distributed-debugging-debug-trace

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.

Quality

36%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/distributed-debugging-debug-trace/SKILL.md

The canonical home for this skill is distributed-debugging-debug-trace in rmyndharis/antigravity-skills

Quality

Content

32%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill reads as a high-level outline or template rather than actionable guidance. It lacks any concrete code examples, specific tool configurations, or executable commands for debugging and tracing setup. The referenced implementation playbook is not provided in the bundle, leaving the skill with almost no substantive content to act on.

Suggestions

Add concrete, executable examples for at least one tracing setup (e.g., OpenTelemetry configuration snippet, a sample docker-compose with Jaeger, or a logging configuration with correlation IDs).

Define explicit validation steps: e.g., 'Send a test request and verify the trace appears in the collector UI' or 'Run `curl localhost:16686/api/traces?service=myapp` to confirm trace ingestion'.

Provide the referenced `resources/implementation-playbook.md` bundle file, or inline the most critical patterns directly in the SKILL.md so the skill is usable standalone.

Remove the duplicated description paragraph and the 'Context' section, which restate what's already in the opening line and 'Use this skill when' sections.

Dimension	Reasoning	Score
Conciseness	The skill repeats the description verbatim in the opening paragraph and includes some unnecessary context sections ('Use this skill when', 'Do not use this skill when', 'Context') that explain things Claude can infer. The instructions themselves are reasonably terse but the surrounding scaffolding adds bloat.	3 / 5
Actionability	The instructions are entirely high-level directives ('Identify services, trace boundaries, and key spans', 'Configure local debugging and production-safe tracing') with no concrete code, commands, configuration examples, or specific tool references. There is nothing executable or copy-paste ready.	2 / 5
Workflow Clarity	There is a rough sequence implied by the bullet points (identify → configure → standardize → validate), but steps are vaguely defined with no validation checkpoints, no feedback loops, and no concrete commands. For a skill involving production tracing and distributed systems, the absence of explicit validation steps is a significant gap.	2 / 5
Progressive Disclosure	The skill references `resources/implementation-playbook.md` for detailed patterns, which is good in principle, but no bundle files are provided so the reference is unverifiable and potentially broken. The SKILL.md itself contains very little substantive content, making it feel like a hollow shell pointing to a non-existent resource.	2 / 5
	Total	9 / 20 Passed

Description

41%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description identifies a clear domain (debugging and tracing) but remains at a high level of abstraction without listing concrete, specific actions or tools. It critically lacks a 'Use when...' clause, making it difficult for Claude to know when to select this skill over others. The use of second person ('You are') violates the third-person voice guideline, and the language reads more like a system prompt persona assignment than a skill description.

Suggestions

Add an explicit 'Use when...' clause with trigger terms like 'debug', 'set up tracing', 'distributed tracing', 'error tracking', 'breakpoints', 'logging setup', 'observability'.

Replace high-level phrases like 'establish troubleshooting practices' with concrete actions such as 'configure log aggregation pipelines', 'set up OpenTelemetry instrumentation', 'create debug launch configurations'.

Rewrite in third person voice (e.g., 'Configures debugging environments and implements distributed tracing solutions') instead of the current second person 'You are' framing.

Dimension	Reasoning	Score
Specificity	Names the domain (debugging) and mentions a few actions like 'configure debugging workflows', 'implement tracing solutions', and 'establish troubleshooting practices', but these are still fairly high-level and not concrete specific actions like 'set breakpoints', 'configure log aggregation', or 'instrument code with OpenTelemetry'.	3 / 5
Completeness	Has a somewhat clear 'what' (configure debugging workflows, implement tracing, establish troubleshooting practices) but completely lacks a 'when' clause. There is no 'Use when...' guidance or explicit trigger phrases to help Claude know when to select this skill.	2 / 5
Trigger Term Quality	Includes some relevant keywords like 'debugging', 'distributed tracing', 'diagnostic tools', and 'troubleshooting', but misses common natural terms users would say such as 'logs', 'breakpoints', 'error tracking', 'stack trace', 'profiling', 'observability', or specific tool names like 'OpenTelemetry', 'Jaeger', etc.	3 / 5
Distinctiveness Conflict Risk	The focus on debugging environments and distributed tracing provides some specificity, but terms like 'troubleshooting practices' and 'diagnostic tools' are broad enough to overlap with general development skills, logging skills, or monitoring/observability skills.	3 / 5
	Total	11 / 20 Passed

Validation

90%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: skills/distributed-debugging-debug-trace/SKILL.md
Commit: 57c135b

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.