o11y-dev/opentelemetry-skill
Expert OpenTelemetry guidance for collector configuration, pipeline design, and production telemetry instrumentation. Use when configuring collectors, designing pipelines, instrumenting applications, implementing sampling, managing cardinality, securing telemetry, writing OTTL transformations, or setting up AI coding agent observability (Claude Code, Codex, Gemini CLI, GitHub Copilot).
93
97%
Does it follow best practices?
Impact
85%
7.08xAverage score across 4 eval scenarios
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that clearly defines its domain (OpenTelemetry), lists specific concrete capabilities, and includes an explicit 'Use when...' clause with comprehensive trigger terms. The description is concise yet thorough, covering both general OTel tasks and a distinctive niche (AI coding agent observability). It uses proper third-person voice throughout.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: collector configuration, pipeline design, instrumentation, sampling, cardinality management, securing telemetry, OTTL transformations, and AI coding agent observability. These are all distinct, concrete capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (expert OpenTelemetry guidance for collector configuration, pipeline design, production telemetry instrumentation) and 'when' with an explicit 'Use when...' clause listing eight specific trigger scenarios. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'OpenTelemetry', 'collector', 'pipeline', 'instrumentation', 'sampling', 'cardinality', 'OTTL', and specific AI agent names (Claude Code, Codex, Gemini CLI, GitHub Copilot). These are terms practitioners naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — OpenTelemetry is a specific domain, and the description narrows further with terms like 'OTTL transformations', 'collector configuration', and 'AI coding agent observability'. Very unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
92%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality skill that demonstrates expert-level OpenTelemetry knowledge packaged efficiently for Claude. Its strengths are the production-ready baseline config, explicit validation workflow with error recovery, and the well-designed progressive disclosure trigger table. The main weakness is that bundle files are not provided, making it impossible to verify the 13+ referenced markdown files actually exist and contain the promised content.
Suggestions
Provide the referenced bundle files (references/sampling.md, references/collector.md, etc.) so the progressive disclosure system is actually functional rather than aspirational.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It avoids explaining what OpenTelemetry is or how collectors work conceptually. Every section delivers actionable information—principles are terse guardrails, the config is copy-paste ready, and the anti-patterns list is a compact checklist. No unnecessary padding. | 3 / 3 |
Actionability | The skill provides a fully executable baseline YAML configuration, concrete bash validation commands, and a detailed error recovery table with specific fixes. The pre-flight checklist asks targeted questions. Everything is copy-paste ready and specific. | 3 / 3 |
Workflow Clarity | The workflow is clearly sequenced: pre-flight checklist → generate config → validate before deploying (with exact commands) → verify live pipeline → error recovery with feedback loops. Validation checkpoints are explicit, and the error recovery table provides a fix-and-retry pattern for each failure mode. | 3 / 3 |
Progressive Disclosure | The trigger table with 12 reference files is an excellent progressive disclosure design, and references are clearly one-level deep. However, no bundle files were provided, so we cannot confirm the referenced files exist. The SKILL.md itself is well-structured but includes a substantial inline config block that could arguably be a referenced file, and the compatibility.md reference at the end feels tacked on. | 2 / 3 |
Total | 11 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
Reviewed
Table of Contents