setting-up-distributed-tracing

Execute this skill automates the setup of distributed tracing for microservices. it helps developers implement end-to-end request visibility by configuring context propagation, span creation, trace collection, and analysis. use this skill when the user re... Use when appropriate context detected. Trigger with relevant phrases based on skill purpose.

Quality

51%

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/performance/distributed-tracing-setup/skills/setting-up-distributed-tracing/SKILL.md

Quality

Content

35%

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

The body is a generic, descriptive overview with no executable examples, no validation checkpoints, and no navigation to the bundled script/reference files, leaving Claude without concrete guidance to act on.

Suggestions

Add concrete, executable snippets (e.g. a minimal OpenTelemetry SDK init block and a Jaeger/Zipkin exporter config) instead of only describing that code will be generated.

Replace the generic "Instructions/Output/Error Handling" sections with a real sequenced workflow that includes a validation/verification checkpoint (e.g. confirm a trace appears in the backend after instrumentation).

Link to the bundled materials, e.g. "For a working Jaeger setup, run scripts/setup_jaeger.py" and reference the relevant files in references/, instead of leaving them unmentioned.

Dimension	Reasoning	Score
Conciseness	Mostly readable but padded with generic restatement (the Overview repeats the description) and low-value filler like "Invoke this skill when the trigger conditions are met / Provide necessary context and parameters" and "Resources: Project documentation / Related skills and commands" that Claude already knows.	2 / 3
Actionability	No executable code or commands appear anywhere; actions are described ("generates the necessary configuration files and code snippets", "structured output relevant to the task") rather than shown, matching the vague/abstract anchor.	1 / 3
Workflow Clarity	"How It Works" lists sequenced phases, but there are no validation or verification checkpoints and no feedback loops for a setup task that modifies running services, capping workflow clarity at 2 per the guidelines.	2 / 3
Progressive Disclosure	The body is a monolithic single-file treatment that never links to or signals the existing bundle (scripts/setup_jaeger.py, references/, assets/), so navigation to the detailed materials is absent despite them being present on disk.	2 / 3
	Total	7 / 12 Passed

Description

67%

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 in a clear niche, but its trigger clause is truncated and filled with generic boilerplate, weakening both trigger quality and completeness.

Suggestions

Rewrite the "Use when..." clause with concrete natural triggers, e.g. "Use when the user asks to set up distributed tracing, instrument microservices with OpenTelemetry/Jaeger/Zipkin, or debug cross-service request flows."

Remove the templated placeholders ("Use when appropriate context detected. Trigger with relevant phrases based on skill purpose.") and the truncated "use this skill when the user re..." fragment.

Rewrite the opening in clean third person (e.g. "Sets up distributed tracing for microservices...") to fix the awkward "Execute this skill automates..." phrasing.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions — "configuring context propagation, span creation, trace collection, and analysis" — matching the multiple-specific-actions anchor.	3 / 3
Completeness	Clearly states what the skill does, but the "when" guidance is cut off and replaced with templated placeholders, so an explicit usable trigger is effectively missing — capping completeness at 2 per the guidelines.	2 / 3
Trigger Term Quality	Contains some relevant terms ("distributed tracing", "setup tracing", "microservices") but the trigger clause is truncated ("use this skill when the user re...") and padded with generic boilerplate ("Use when appropriate context detected. Trigger with relevant phrases based on skill purpose") rather than natural user phrasings.	2 / 3
Distinctiveness Conflict Risk	Targets a distinct niche (distributed tracing setup for microservices) with domain-specific vocabulary, making it unlikely to trigger for unrelated skills.	3 / 3
	Total	10 / 12 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Path: plugins/performance/distributed-tracing-setup/skills/setting-up-distributed-tracing/SKILL.md
Commit: 15940c5

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