distributed-tracing

Implement distributed tracing with Jaeger and Tempo to track requests across microservices and identify performance bottlenecks. Use when debugging microservices, analyzing request flows, or implementing observability for distributed systems.

Quality

60%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/distributed-tracing/SKILL.md

Quality

Content

46%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 content is highly actionable with copy-paste-ready code and deploy commands, but it is verbose and monolithic: substantial setup manifests and multi-language instrumentation are inlined rather than split into reference files, and workflows lack explicit validation checkpoints.

Suggestions

Move the large Kubernetes/Docker deployment manifests and per-language instrumentation into separate reference files (e.g., references/jaeger-setup.md, references/instrumentation.md) and link them from a concise overview.

Add explicit validation/verification checkpoints to the deployment and instrumentation workflows (e.g., verify Jaeger UI is reachable, confirm traces appear before proceeding).

Trim introductory concept explanations Claude already knows (Trace/Span/Context definitions) to improve token efficiency.

Dimension	Reasoning	Score
Conciseness	The body is noticeably verbose, packing large inline deployment manifests, full instrumentation snippets in three languages, and lengthy config blocks; much of this detail belongs in separate reference files rather than the overview.	2 / 5
Actionability	Provides concrete, mostly executable code and kubectl/yaml commands across Python, Node.js, and Go with only minor gaps (e.g., the Node.js snippet omits the trace import).	4 / 5
Workflow Clarity	Sections give rough sequences (setup, instrument, propagate, analyze) but there are no explicit validation checkpoints or verify-fix-retry loops, and deployment operations lack verification steps.	3 / 5
Progressive Disclosure	No bundle reference files exist; large deployment and instrumentation content is inlined monolithically with no references offloaded to separate files, and navigation is limited to flat section headers.	2 / 5
	Total	11 / 20 Passed

Description

75%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 communicates capability and trigger conditions in third person, naming specific tools (Jaeger, Tempo) and concrete actions. It is slightly under-comprehensive on action coverage and natural-term synonyms.

Suggestions

Add natural trigger synonyms users say, such as 'traces', 'spans', or 'trace context'.

Expand the action list slightly (e.g., 'propagate trace context', 'sample traces') for more comprehensive coverage.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('Implement distributed tracing', 'track requests across microservices', 'identify performance bottlenecks') naming both Jaeger and Tempo, with minor gaps in coverage of the full action set.	4 / 5
Completeness	Clearly states both what it does and when to use it ('Use when debugging microservices, analyzing request flows...'); the 'when' could be slightly more explicit with additional trigger phrases.	4 / 5
Trigger Term Quality	Includes natural user-facing phrases ('debugging microservices', 'analyzing request flows', 'implementing observability') but misses common synonyms like 'traces' and 'spans' that users would say.	4 / 5
Distinctiveness Conflict Risk	The Jaeger/Tempo + distributed tracing niche is mostly distinct from other observability skills, with minor overlap risk against related metrics/dashboard skills.	4 / 5
	Total	16 / 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-tracing/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.