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-claude/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 concise and well-sectioned but offers only abstract directives with no concrete, executable guidance, and its single external reference points to a file that is not present in the bundle.

Suggestions

Add concrete, executable guidance: specific tracing tools (e.g., OpenTelemetry, Jaeger), example config snippets, or commands for instrumenting services and verifying trace coverage.

Convert the instructions into a numbered workflow with explicit validation checkpoints (e.g., 'verify trace propagation across services' / 'confirm sampling rate') and a fix-and-retry loop before enabling production tracing.

Fix the broken reference by creating 'resources/implementation-playbook.md' (or correcting the path so it matches the 'Resources' section), so progressive disclosure points to a real file.

Dimension	Reasoning	Score
Conciseness	Lean and mostly efficient with no concept over-explanation; only minor redundancy from re-stating the description verbatim in the opening paragraph.	4 / 5
Actionability	Provides only high-level hints ('Identify services, trace boundaries, and key spans,' 'Standardize log/trace fields and correlation IDs') with no concrete commands, code, tools, or examples, matching the 'high-level hints missing specific steps' anchor.	2 / 5
Workflow Clarity	Instructions are a rough, loosely ordered bullet list with no explicit sequence, validation checkpoints, or feedback loops for production-affecting operations; the safety section notes risks but defines no validation workflow.	2 / 5
Progressive Disclosure	Has clear section structure and a one-level reference, but the referenced file 'resources/implementation-playbook.md' does not exist in the bundle, and the path naming is inconsistent ('resources/' vs the 'Resources' section), leaving navigation only partially reliable.	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 what the skill does but lacks any explicit trigger ('Use when...') guidance, capping completeness. Trigger terms and distinctiveness are reasonably strong, while specificity is held back by generic, abstract actions.

Suggestions

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

Replace abstract actions with more concrete operations (name specific tools, libraries, or concrete tasks) to lift specificity above 3.

Dimension	Reasoning	Score
Specificity	Lists several actions ('Configure debugging workflows, implement tracing solutions, and establish troubleshooting practices') but they are generic and abstract rather than concrete, matching the '1-2 concrete actions, not comprehensive' anchor.	3 / 5
Completeness	Has a clear 'what' but no 'Use when...' clause or equivalent explicit trigger guidance, which per the rubric caps completeness at 3.	3 / 5
Trigger Term Quality	Good coverage of natural domain terms users would say ('debugging,' 'distributed tracing,' 'diagnostic tools,' 'troubleshooting,' 'logging') with only a few natural synonyms or specific tool names missing.	4 / 5
Distinctiveness Conflict Risk	The debugging/distributed-tracing/diagnostics niche is mostly distinct with minor overlap risk against closely related observability 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-claude/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.