CtrlK
BlogDocsLog inGet started
Tessl Logo

o11y-dev/opentelemetry-skill

Expert OpenTelemetry guidance for collector configuration, pipeline design, and production telemetry instrumentation across Kubernetes, ECS, serverless, and standalone deployments. 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

1.34x
Quality

98%

Does it follow best practices?

Impact

94%

1.34x

Average score across 18 eval scenarios

SecuritybySnyk

Passed

No known issues

Overview
Quality
Evals
Security
Files

Quality

Content

100%

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

The skill body is a strong, production-oriented overview: it pairs concrete copy-paste config with sequenced review workflows and a keyword→reference trigger table that points to a verified bundle. It is lean, actionable, and well-structured for progressive disclosure.

DimensionReasoningScore

Conciseness

The body is dense and assumes Claude's competence throughout — Core Principles, Pre-Flight Checklist, and Anti-Patterns are terse imperatives with every token earning its place; there is only minor overlap between the Pre-Flight and Review-Mode sections, not enough to drop it to the score-2 'could be tightened' anchor.

3 / 3

Actionability

Provides a fully copy-paste-ready production baseline YAML with concrete port numbers (4317/4318), a specific validation command ('otelcol validate --config <path>'), and explicit defaults (memory_limiter first, limit_percentage: 80), matching the score-3 'executable and copy-paste ready' anchor.

3 / 3

Workflow Clarity

Multi-step processes are clearly sequenced with explicit checkpoints: the Pre-Flight Checklist ('If unknown, ask first'), the eight-step Existing Config Review Mode, and the 'Validation & Error Recovery' section with symptom→cause→fix feedback loop, satisfying the score-3 anchor.

3 / 3

Progressive Disclosure

A clear trigger-keyword table maps each request pattern to a one-level-deep reference file (all of which exist in ./references/), keeping SKILL.md as an overview with well-signaled navigation; the only blemish is that setup-index.md acts as a second-level hub but is not surfaced from the body, though this is minor and does not push it to score-2.

3 / 3

Total

12

/

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.

The description is concise yet comprehensive: it states concrete capabilities and provides an explicit 'Use when' trigger clause with natural terms and named tools. It cleanly satisfies all four dimensions at the top anchor.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('configuring collectors, designing pipelines, instrumenting applications, implementing sampling, managing cardinality, securing telemetry, writing OTTL transformations, or setting up AI coding agent observability'), matching the score-3 anchor of enumerating specific concrete actions.

3 / 3

Completeness

Explicitly answers both 'what' (expert OpenTelemetry guidance for collector config, pipeline design, instrumentation) and 'when' via the 'Use when configuring collectors, designing pipelines, ...' clause, satisfying the score-3 anchor.

3 / 3

Trigger Term Quality

Covers natural terms a user would say — 'configuring collectors', 'designing pipelines', 'instrumenting applications', 'sampling', 'cardinality', 'securing telemetry', 'OTTL transformations', and named tools 'Claude Code, Codex, Gemini CLI, GitHub Copilot' — giving good coverage of likely phrasings.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear OpenTelemetry niche with distinct, domain-specific triggers and named AI coding agents, making it unlikely to fire for an unrelated skill.

3 / 3

Total

12

/

12

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Reviewed

Table of Contents