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

51%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

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

Quality

Content

43%Weight 40%Scale 1-5

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

The skill body is brief and well-sectioned but mostly abstract, offering directives rather than executable guidance and missing validation checkpoints for risky tracing operations. Its progressive disclosure relies on a referenced file that is not present in the bundle.

Suggestions

Replace abstract instructions with concrete, executable guidance, e.g. specific commands or tooling examples (OpenTelemetry setup, log field schemas, sampling config snippets).

Add explicit validation checkpoints and a feedback loop, such as verifying end-to-end trace coverage and re-checking after fixes, to lift workflow clarity above the cap.

Either add the missing 'resources/implementation-playbook.md' bundle file or remove the reference so progressive disclosure is not pointing at nonexistent content.

Dimension	Reasoning	Score
Conciseness	The body is short and avoids explaining concepts Claude already knows, but the opening line verbatim repeats the frontmatter description and the 'Context' section restates obvious purpose, which is mild padding that could be trimmed.	3 / 5
Actionability	Instructions are high-level directives ('Identify services, trace boundaries', 'Standardize log/trace fields') with no concrete commands, tool names, code, or examples, leaving Claude without specific executable steps.	2 / 5
Workflow Clarity	A rough five-step sequence is listed, but there are no validation checkpoints or feedback loops even though production tracing and sampling validation are batch/risky operations, which per the guidelines caps workflow clarity at 3.	3 / 5
Progressive Disclosure	Structure is present with clear sections and a one-level reference to 'resources/implementation-playbook.md', but that referenced file does not exist in any bundle directory, and the body inlines the 'Safety' guidance rather than separating it, so navigation and structure are only partially realized.	3 / 5
	Total	11 / 20 Passed

Description

58%Weight 40%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 states concrete capabilities clearly but omits any explicit 'Use when...' trigger guidance, capping completeness and limiting trigger-term quality. It is reasonably distinct from other skills but would benefit from natural user-facing trigger phrases.

Suggestions

Add an explicit 'Use when...' clause naming natural user phrases (e.g. 'Use when the user asks to trace a request across services, set up distributed tracing, or debug a production issue').

Include concrete trigger keywords and synonyms users would actually say, such as 'debug', 'trace', 'correlation IDs', and 'OpenTelemetry', to improve trigger-term quality.

Tighten 'debugging environments' and 'diagnostic tools' into more specific actions to lift specificity toward comprehensive coverage.

Dimension	Reasoning	Score
Specificity	The description lists several concrete actions ('Configure debugging workflows, implement tracing solutions, and establish troubleshooting practices'), though 'debugging environments' and 'diagnostic tools' are somewhat broad domain language rather than fully concrete actions, leaving minor gaps relative to the comprehensive anchor.	4 / 5
Completeness	The 'what' is clearly stated via concrete actions, but there is no 'Use when...' clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 3.	3 / 5
Trigger Term Quality	It includes relevant terms like 'debugging environments', 'distributed tracing', and 'diagnostic tools', but misses natural phrases users actually say (e.g. 'debug', 'trace a request', 'find a bug') and lacks synonyms or specific tool/file keywords, so coverage is partial rather than comprehensive.	3 / 5
Distinctiveness Conflict Risk	The debugging/distributed-tracing niche is fairly distinct and unlikely to trigger for unrelated skills, with only minor overlap risk against general observability or logging skills.	4 / 5
	Total	14 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: rmyndharis/antigravity-skills
Path: skills/distributed-debugging-debug-trace/SKILL.md
Commit: 3eff4af

Reviewed: 1 day 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.