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

52%

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 ./plugins/AI-Agents-Safe-Coding-Skills/skills/distributed-debugging-debug-trace/SKILL.md

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

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 body is well-sectioned and concise, but its instructions are vague and non-executable, the workflow lacks validation checkpoints, and its only progressive-disclosure reference points to a missing file. It reads as an outline rather than actionable guidance.

Suggestions

Replace abstract instruction bullets with concrete, executable steps naming specific tools/commands (e.g., an OpenTelemetry setup snippet, a sampling config, a correlation-ID logging pattern).

Add explicit validation checkpoints to the workflow (e.g., verify trace propagation end-to-end, confirm sampling rate, check that PII redaction is active before production).

Either create 'resources/implementation-playbook.md' or remove the broken reference so the pointed-to detailed material actually exists.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes competence, but the opening paragraph restates the description verbatim and the 'Context' section adds mild padding that could be trimmed.	4 / 5
Actionability	Instructions are high-level hints ('Identify services, trace boundaries, and key spans', 'Configure local debugging and production-safe tracing') with no concrete code, commands, or named tools to execute.	2 / 5
Workflow Clarity	The instruction bullets form only a rough sequence with poorly defined steps and no validation checkpoints; given the production-tracing risk this stays below the destructive-operation cap of 3 at anchor 2.	2 / 5
Progressive Disclosure	Section structure is clear, but the sole referenced file 'resources/implementation-playbook.md' does not exist in the bundle, so the one-level-deep reference is broken and cannot support navigation.	3 / 5
	Total	11 / 20 Passed

Description

61%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 clearly states the skill's domain and several actions but omits any explicit 'when to use' trigger guidance and uses second-person voice, capping completeness and lowering specificity. It is distinguishable and uses reasonably natural trigger terms, landing in the mid-range.

Suggestions

Add an explicit 'Use when...' clause with concrete trigger phrases (e.g., 'Use when setting up distributed tracing, diagnosing multi-service issues, or establishing logging standards').

Rewrite in third person to avoid the second-person voice penalty (e.g., 'Configures debugging workflows and implements tracing solutions...' rather than 'You are a debugging expert...').

Include more natural synonyms and file/tech extensions users say (observability, logs, OpenTelemetry, .trace) to raise trigger term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain and several actions ('Configure debugging workflows, implement tracing solutions, and establish troubleshooting practices') but the verbs are somewhat generic, and the second-person opening ('You are a debugging expert') triggers the voice penalty that lowers the score by one from a base of 4.	3 / 5
Completeness	The description gives a clear 'what' but contains no 'Use when...' clause or equivalent explicit trigger guidance, so completeness is capped at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	Includes natural terms users would say ('debugging', 'distributed tracing', 'diagnostic tools', 'troubleshooting', 'production'), though common synonyms like observability, logs, and monitoring are absent.	4 / 5
Distinctiveness Conflict Risk	Distributed tracing and debugging form a fairly distinct niche with minimal conflict risk, though there is minor overlap with general observability or logging skills.	4 / 5
	Total	14 / 20 Passed

Validation

93%

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

Validation for skill structure

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

	Total	15 / 16 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills/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.