setting-up-distributed-tracing
tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill setting-up-distributed-tracingExecute 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.
Validation
81%| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 13 / 16 Passed | |
Implementation
7%This skill content is almost entirely meta-description and placeholder text with no actionable guidance. It explains what distributed tracing is and when to use it (which Claude already knows) but provides zero concrete code examples, configuration snippets, or specific commands. The 'Instructions' and 'Output' sections are generic boilerplate that could apply to any skill.
Suggestions
Replace the abstract 'How It Works' section with actual executable code showing OpenTelemetry instrumentation (e.g., Python/Node.js tracer initialization, span creation, context propagation)
Add concrete configuration examples for at least one backend (Jaeger/Zipkin) including docker-compose setup, environment variables, and exporter configuration
Provide a specific step-by-step workflow with validation checkpoints (e.g., 'verify traces appear in backend UI before proceeding to instrument next service')
Remove the generic 'Instructions', 'Output', and 'Error Handling' sections and replace with actual implementation details and troubleshooting commands
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with extensive padding explaining concepts Claude already knows (what distributed tracing is, when to use it). The 'Overview', 'When to Use', and 'How It Works' sections are redundant meta-descriptions rather than actionable content. | 1 / 3 |
Actionability | No concrete code, commands, or executable examples provided. The 'Examples' section describes what the skill 'will do' abstractly rather than showing actual configuration snippets, OpenTelemetry code, or specific commands. Everything is vague description. | 1 / 3 |
Workflow Clarity | The 'Instructions' section is completely generic ('Invoke this skill when trigger conditions are met') with no actual workflow steps. No validation checkpoints, no specific sequence for implementing tracing, no feedback loops for verifying trace propagation works. | 1 / 3 |
Progressive Disclosure | Content is organized into sections with headers, but it's a monolithic document with no references to detailed materials. The structure exists but contains mostly filler content rather than appropriately split actionable guidance. | 2 / 3 |
Total | 5 / 12 Passed |
Activation
17%This description has a truncated capability section and completely generic placeholder trigger guidance that provides no value for skill selection. While it identifies a specific technical domain (distributed tracing), the boilerplate 'Use when appropriate context detected' text defeats the purpose of having trigger terms. The description needs to be completed and given real trigger examples.
Suggestions
Replace the placeholder trigger text with specific natural phrases like 'Use when the user mentions tracing, distributed tracing, OpenTelemetry, Jaeger, request tracking across services, or debugging microservice latency'
Complete the truncated description to fully explain what the skill does
Add user-friendly trigger terms alongside technical ones (e.g., 'track requests across services', 'debug slow API calls', 'see request flow')
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (distributed tracing for microservices) and lists some actions (configuring context propagation, span creation, trace collection, and analysis), but the description is truncated and uses somewhat technical jargon rather than concrete user-facing actions. | 2 / 3 |
Completeness | While the 'what' is partially addressed, the 'when' clause is entirely placeholder text ('Use when appropriate context detected') that provides zero actionable guidance. The description also appears truncated ('when the user re...'). | 1 / 3 |
Trigger Term Quality | The trigger guidance is completely generic boilerplate ('Use when appropriate context detected. Trigger with relevant phrases based on skill purpose') with no actual natural keywords users would say. Technical terms like 'context propagation' and 'span creation' are jargon, not user language. | 1 / 3 |
Distinctiveness Conflict Risk | The domain of 'distributed tracing for microservices' is reasonably specific, but the generic trigger guidance and truncated description reduce distinctiveness. Could overlap with general observability or monitoring skills. | 2 / 3 |
Total | 6 / 12 Passed |
Reviewed
Table of Contents
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.