Automated summary
This skill guides the setup of debugging environments, distributed tracing, and diagnostic tooling for both development and production teams.
Strengths
- Covers both local debugging and production-safe tracing
- Emphasizes standardizing log/trace fields and correlation IDs
- Includes explicit safeguards around production verbosity and redacting secrets and PII
- Points to a detailed implementation playbook for tooling and configuration patterns
Limitations
- Stays procedural: no specific tooling (OpenTelemetry, Jaeger, etc.) is named in the SKILL.md
- Assumes you can modify logging, tracing, or runtime configuration
- Does not replace environment-specific validation or expert review
Use it when you need to establish team debugging workflows, distributed tracing, and logging/diagnostics standards across services.
Avoid it for a simple single-process system, or when you cannot change logging, tracing, or runtime configuration.
Security analysis
SafeThe skill contains only high-level instructions for debugging and tracing configuration. It declares no tools, runs no commands, and includes no destructive, exfiltration, obfuscation, or safety-disabling behavior. It explicitly advises redacting secrets/PII and avoiding unsafe production tracing.
No concerns found
How this analysis is madeExamples
Help me add distributed tracing across our three Node.js microservices: define trace boundaries and key spans, standardize correlation IDs in logs, and configure sampling that is safe for production.Our team has no shared debugging conventions. Propose a logging and diagnostics standard with required fields and correlation IDs, plus safeguards to avoid verbose tracing in prod and to redact PII.We have intermittent 500s in a multi-service checkout flow. Set up a debugging and tracing plan to isolate which service and span is failing, and tell me what to validate end to end.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: unknown 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.
Resources
resources/implementation-playbook.mdfor 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.
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/distributed-debugging-and-tracing-ms47vpwc/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/distributed-debugging-and-tracing-ms47vpwc' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/distributed-debugging-and-tracing-ms47vpwc/download' --output '.skill-downloads/distributed-debugging-and-tracing-ms47vpwc/SKILL.md.part' && mv '.skill-downloads/distributed-debugging-and-tracing-ms47vpwc/SKILL.md.part' '.skill-downloads/distributed-debugging-and-tracing-ms47vpwc/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
Original excerpt: Requirements
$ARGUMENTS
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/distributed-debugging-and-tracing-ms47vpwc/SKILL.md' && test -s '.skill-downloads/distributed-debugging-and-tracing-ms47vpwc/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/distributed-debugging-debug-trace' && cp -R '.skill-downloads/distributed-debugging-and-tracing-ms47vpwc' '.claude/skills/distributed-debugging-debug-trace'Cursor
test -f '.skill-downloads/distributed-debugging-and-tracing-ms47vpwc/SKILL.md' && test -s '.skill-downloads/distributed-debugging-and-tracing-ms47vpwc/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/distributed-debugging-debug-trace' && cp -R '.skill-downloads/distributed-debugging-and-tracing-ms47vpwc' '.cursor/skills/distributed-debugging-debug-trace'Codex
test -f '.skill-downloads/distributed-debugging-and-tracing-ms47vpwc/SKILL.md' && test -s '.skill-downloads/distributed-debugging-and-tracing-ms47vpwc/SKILL.md' && mkdir -p '.agents/skills' && test ! -e '.agents/skills/distributed-debugging-debug-trace' && cp -R '.skill-downloads/distributed-debugging-and-tracing-ms47vpwc' '.agents/skills/distributed-debugging-debug-trace'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/distributed-debugging-and-tracing-ms47vpwc'openskills read 'distributed-debugging-and-tracing-ms47vpwc'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/distributed-debugging-and-tracing-ms47vpwc/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
Configure a Chat Channel with SecretRefs
DevOps
Set up chat channels using non-interactive commands, with secrets only as SecretRefs. Covers gather, mutate, repair, and prove steps for reliable delivery.
Investigate ClickHouse CI Failures
DevOps
Investigate a ClickHouse CI failure end-to-end from a PR or S3 report URL. Fetches failed tests, classifies flaky vs real regression, and checks for existing issues/fixes.
Ansible PR Review
DevOps
Reviews an Ansible PR following the project's standardized process, including changelog checks, test coverage validation, and feedback tracking.