Serverless debugging
Skill charlieviettq/awesome-agent-skill/.claude/skills/serverless-debugging
Curated skill pack for LLM agents in engineer and science workflow (Cursor & Claude ready).
npx -y skills add charlieviettq/awesome-agent-skill --skill serverless-debuggingAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 22 stars22 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Debug serverless and edge functions—limited logs, cold starts, timeouts, env/config mismatches. Use for Lambda, Cloud Functions, Workers, Vercel/Netlify functions.
SKILL.md
1.8 KB, 368 tokens by cl100k_base, as published. Nobody here has run it
Serverless Debugging
Systematic debugging when traditional server logs and SSH are unavailable. Complements test-failure-triage with environment-specific constraints.
When to use
- Intermittent 5xx from functions
- Timeout or memory limit errors
- Works locally but fails when deployed
When not to use
- Long-running container services with full shell access
- Client-only bugs (use browser DevTools skills)
Workflow
- Reproduce — identify trigger (HTTP event, queue, schedule)
- Logs — cloud provider log group/stream; filter by request ID
- Config — compare env vars/secrets: local vs deployed (names only, never log values)
- Limits — timeout, memory, payload size, concurrency
- Cold start — init duration, heavy imports, VPC ENI delay
- Dependencies — outbound network, IAM permissions, region mismatch
- Minimal fix — smallest change; redeploy; verify with structured log line
Common failure modes
| Symptom | Likely cause |
|---|---|
| Task timed out | Slow downstream, missing async, too much work in handler |
| Cannot find module | Bundle/packaging; wrong runtime |
| Access denied | IAM role, resource policy |
| Connection timeout | VPC/subnet/NAT; wrong security group |
| Works once then fails | State in /tmp; connection pool reuse |
Practices
- Structured JSON logs with
requestId,stage,durationMs - Fail fast on missing required env with clear error message (no secret values)
- Use X-Ray or vendor tracing for cross-service calls
- Keep handlers thin; push heavy work to async queues when needed