distributed-debugging-debug-trace — Claude Code skill: what it does
distributed-debugging-debug-trace sets up debugging and distributed tracing: trace boundaries, key spans, correlation IDs, and a check that traces actually cover the request path.
MIT ★ 50,109 updated 2026-10-29
npx skills add sickn33/agentic-awesome-skills --skill distributed-debugging-debug-trace -a claude-codeWhat distributed-debugging-debug-trace does
The skill walks the agent through a trace setup: find the services and where a trace begins and ends, pick the spans that matter, wire up local debugging plus tracing that won't hurt production, settle on one set of log fields and correlation IDs. Then it asks for proof that traces reach across the whole request path and that sampling is tuned. You describe the job in $ARGUMENTS; deeper tooling patterns sit in resources/implementation-playbook.md.
Treat that playbook as sketches. Its classes are partial, some helpers and imports are missing, and the OpenTelemetry and Sentry snippets are tied to particular versions. Check them against what you have pinned and look at the instrumentation already in place, or you end up with duplicate server spans. The author tags the skill risk: critical, which fits: a debugger runs code, and heap or core dumps hand over every secret held in memory.
Keep inspectors and dashboards on loopback behind an authenticated tunnel, cap how long and how large a snapshot can get, strip secrets and PII before anything leaves the box, close the temporary access afterwards. Pausing, profiling or changing telemetry on production needs scoped authorization and a rollback plan. A config that parses proves nothing about end-to-end coverage.
What it helps with
- Trace a request across several services
- Standardize log fields and correlation IDs
- Check whether traces cover the full request path
- Debug a production incident without leaving verbose logging on
- Strip secrets and PII before exporting traces
Example prompts for the agent
- Map the trace boundaries and key spans for our checkout service
- Check whether our traces cover the whole request path and that sampling keeps the slow calls
- Set up a production-safe debugging session and tell me how to keep secrets out of the snapshots
How to install distributed-debugging-debug-trace
1Skills CLI (Vercel)
npx skills add sickn33/agentic-awesome-skills --skill distributed-debugging-debug-trace -a claude-code2Manually: put the files in place
~/.claude/skills/distributed-debugging-debug-trace/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/distributed-debugging-debug-trace/
1Skills CLI (Vercel)
npx skills add sickn33/agentic-awesome-skills --skill distributed-debugging-debug-trace -a codex2Manually: put the files in place
.agents/skills/distributed-debugging-debug-trace/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add sickn33/agentic-awesome-skills --skill distributed-debugging-debug-trace -a cursor2Manually: put the files in place
.cursor/skills/distributed-debugging-debug-trace/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install sickn33/agentic-awesome-skills skills/distributed-debugging-debug-trace2Manually: put the files in place
.github/skills/distributed-debugging-debug-trace/SKILL.md1Skills CLI (Vercel)
npx skills add sickn33/agentic-awesome-skills --skill distributed-debugging-debug-trace -a gemini-cli2Platform CLI
gemini skills install https://github.com/sickn33/agentic-awesome-skills --path skills/distributed-debugging-debug-traceManually: put the files in place
.devin/skills/distributed-debugging-debug-trace/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add sickn33/agentic-awesome-skills --skill distributed-debugging-debug-trace -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about distributed-debugging-debug-trace
How to install distributed-debugging-debug-trace in Claude Code?
Run npx skills add sickn33/agentic-awesome-skills --skill distributed-debugging-debug-trace -a claude-code. The skill file lands at ~/.claude/skills/distributed-debugging-debug-trace/SKILL.md.
What does distributed-debugging-debug-trace do?
It works through debug and trace setup: trace boundaries, key spans, one set of log fields and correlation IDs, coverage and sampling checks. It also spells out how to keep production safe and secrets out of the output.
Can I use it on production?
For production-safe tracing, yes, with limits. Verbose tracing needs safeguards, while pause, profile or telemetry changes require scoped authorization and a rollback plan.
Source text
SKILL.md · MIT
--- name: distributed-debugging-debug-trace description: "You are a debugging expert specializing in setting up comprehensive debugging environments, distributed tracing, and diagnostic tools. Configure debugging workflows, implement tracing solutions, and establish troubleshooting practices for development and production environments." risk: critical source: community date_added: "2026-02-27" --- # Debug and Trace Configuration You are a debugging expert specializing in setting up comprehensive debugging environments, distributed tracing, and diagnostic tools. Configure debugging workflows, implement tracing solutions, and establish troubleshooting practices for development and production environments. ## Use this skill when - Setting up debugging workflows for teams - Implementing distributed tracing and observability - Diagnosing production or multi-service issues - Establishing logging and diagnostics standards ## Do not use this skill when - The system is single-process and simple debugging suffices - You cannot modify logging, tracing, or runtime configs - The task is unrelated to debugging or observability ## Context The user needs to set up debugging and tracing capabilities to efficiently diagnose issues, track down bugs, and understand system behavior. Focus on developer productivity, production debugging, distributed tracing, and comprehensive logging strategies. ## Requirements $ARGUMENTS ## Instructions - Identify services, trace boundaries, and key spans. - Configure local debugging and production-safe tracing. - Standardize log/trace fields and correlation IDs. - Validate end-to-end trace coverage and sampling. - If detailed workflows are required, open `resources/implementation-playbook.md`. ## Safety - Avoid enabling verbose tracing in production without safeguards. - Redact secrets and PII from logs and traces. ## Deployment and evidence boundary The playbook contains incomplete illustrative classes, undefined helper methods/imports and version-specific OpenTelemetry/Sentry configuration, not a ready-to-run debug stack. Inspect pinned APIs and existing instrumentation before adapting it; avoid duplicate server spans and extract/propagate trace context through supported instrumentation. Debuggers can execute code and heap/core snapshots can expose every in-memory secret. Keep inspectors and dashboards loopback-only behind approved authenticated tunnels, cap snapshot duration/disk/overhead, redact before export and remove temporary access after use. Production pause/profile/telemetry changes require scoped authorization and rollback. Do not replace process-global console methods per request or return sensitive diagnostics in response headers. A successful config parse does not establish end-to-end trace coverage or application correctness. ## Resources - `resources/implementation-playbook.md` for detailed tooling and configuration patterns. ## Limitations - Use this skill only when the task clearly matches the scope described above. - Do not treat the output as a substitute for environment-specific validation, testing, or expert review. - Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
© sickn33 · MIT · sickn33/agentic-awesome-skills