CtrlK
BlogDocsLog inGet started
Tessl Logo

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).

94

6.92x
Quality

94%

Does it follow best practices?

Impact

97%

6.92x

Average score across 4 eval scenarios

SecuritybySnyk

Passed

No known issues

Overview
Quality
Evals
Security
Files

Quality

Content

85%

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

This is a strong, well-architected skill that provides actionable production defaults, clear workflow sequences, and excellent progressive disclosure through a trigger-based reference system. The baseline configuration is copy-paste ready with meaningful inline commentary, and the eval-critical response minimums ensure consistent quality on high-stakes topics. Minor verbosity in some sections (review mode, context triggers table) prevents a perfect conciseness score, but overall token efficiency is good for the breadth of coverage.

DimensionReasoningScore

Conciseness

The skill is generally efficient and avoids explaining basic concepts Claude already knows, but some sections are somewhat verbose — the 'Existing Configuration Review Mode' and 'Progressive Disclosure: Context Triggers' table could be tighter. The core principles section has minor redundancy with later sections (e.g., anti-patterns repeated). Overall mostly lean but not maximally token-efficient.

2 / 3

Actionability

The skill provides a complete, copy-paste-ready production baseline YAML configuration, specific validation commands (`otelcol validate --config <path>`), concrete environment variable names for Claude Code telemetry, specific port numbers, and precise processor ordering rules. The eval-critical response minimums give exact, actionable requirements for common scenarios.

3 / 3

Workflow Clarity

The pre-flight checklist establishes a clear sequence (confirm before generating), the eval-critical response minimums define explicit checkpoints for specific scenarios, and the validation section mandates at least one validation checkpoint. The existing configuration review mode provides a systematic 8-point audit checklist with clear interaction checks. The anti-patterns section serves as a verification checklist.

3 / 3

Progressive Disclosure

Excellent progressive disclosure design with a clear trigger-based reference loading table mapping keywords to specific reference files. The SKILL.md serves as a well-organized overview with concise inline content (baseline config, principles, anti-patterns summary) while pointing to 13+ reference files for detailed topics. References are one level deep and clearly signaled throughout. However, no bundle files were provided to verify the referenced paths actually exist.

3 / 3

Total

11

/

12

Passed

Description

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 provides an explicit 'Use when...' clause with comprehensive trigger terms. It uses proper third-person voice and covers both broad practitioner needs and niche sub-topics like OTTL and AI agent observability, making it highly distinguishable from other skills.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: collector configuration, pipeline design, sampling, cardinality management, OTTL transformations, and AI coding agent observability. These are distinct, actionable capabilities rather than vague abstractions.

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 when seeking help.

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

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.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Reviewed

Table of Contents