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

57%

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

50%

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

The body is cleanly sectioned with useful 'Use/Do not use' triggers and a sequenced instruction list, but it pads tokens by restating the description, gives only abstract guidance without named tooling, and points to a playbook file that is absent from the bundle. Validation exists but lacks a feedback loop.

Suggestions

Remove the verbatim repeat of the description and tighten the 'Context' section to stop restating what debugging/tracing is for.

Add concrete tooling specifics (e.g., OpenTelemetry, Jaeger/Tempo, correlation-ID formats) or a minimal executable example so the instructions are actionable without the missing playbook.

Either provide resources/implementation-playbook.md or remove the dangling reference, since the file is cited in both Instructions and Resources but does not exist.

Dimension	Reasoning	Score
Conciseness	The body is mostly sectioned and lean, but it repeats the frontmatter description verbatim as the opening paragraph and the 'Context' section restates the skill's purpose — padding that could be trimmed.	2 / 3
Actionability	The Instructions give a sequenced task list ('Identify services, trace boundaries, and key spans', 'Standardize log/trace fields and correlation IDs') but name no concrete tools, commands, or configs, so guidance is incomplete rather than executable.	2 / 3
Workflow Clarity	A sequenced workflow is present and includes a 'Validate end-to-end trace coverage and sampling' step, but there is no explicit error-recovery feedback loop or checkpoint condition, leaving validation implicit.	2 / 3
Progressive Disclosure	Sections are well organized and a one-level-deep reference to resources/implementation-playbook.md is signaled, but that referenced file does not exist in the bundle, so the disclosure path is broken.	2 / 3
	Total	8 / 12 Passed

Description

65%

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 names a clear domain and several concrete actions with natural trigger terms, but it is written in second person and omits an explicit 'Use when' trigger clause, capping both specificity and completeness. It is reasonably distinctive but could still overlap with adjacent observability skills.

Suggestions

Rewrite in third person ('Configures debugging workflows...') to avoid the second-person specificity penalty.

Add an explicit 'Use when...' trigger clause (e.g., 'Use when setting up distributed tracing, diagnosing multi-service issues, or standardizing logging across services') to raise completeness to 3.

Sharpen distinctiveness by naming the specific niche, e.g. 'distributed/multi-service tracing', to reduce overlap with generic debugging or logging skills.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete actions ('Configure debugging workflows, implement tracing solutions, and establish troubleshooting practices'), which would rate a 3, but it uses second-person voice ('You are a debugging expert') and the rubric mandates a one-point specificity reduction for second-person voice.	2 / 3
Completeness	It clearly states what the skill does but lacks any 'Use when...' clause or equivalent explicit trigger guidance, which the rubric caps at 2 for completeness.	2 / 3
Trigger Term Quality	It covers natural terms users would say when needing this skill — 'debugging', 'distributed tracing', 'diagnostic tools', and 'troubleshooting' — giving good keyword coverage rather than abstract jargon.	3 / 3
Distinctiveness Conflict Risk	The distributed-tracing niche is somewhat specific, but 'debugging expert' is broad and could overlap with general debugging, logging, or observability skills without distinct triggers.	2 / 3
	Total	9 / 12 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: e63f7dd

Reviewed: about 3 hours 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.