CtrlK
BlogDocsLog inGet started
Tessl Logo

otel-declarative-config

OpenTelemetry declarative YAML configuration for SDK setup. Use when configuring OpenTelemetry SDK providers (tracer, meter, logger), setting up OTLP exporters, defining sampling strategies, or writing otel config files. Triggers on "otel config", "OpenTelemetry YAML", "declarative configuration", "otelconf", "OTEL_CONFIG_FILE", "file_format", "configure tracing/metrics/logs export", or when the user is setting up telemetry pipelines via config files rather than code.

72

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

77%Weight 40%Scale 1-5

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

A dense, well-sequenced body with strong validation checkpoints and feedback loops, but its progressive disclosure is undermined by cross-referenced files that do not exist in the bundle. Actionability and conciseness are strong with minor trimmable gaps.

Suggestions

Add the missing bundle files references/declarative-setup.md and references/setup.md (or remove the Cross-References section) so the deferred language-specific details actually resolve.

Include one complete, tag-matched inline YAML example for the most common case so users have a copy-paste starting point without first fetching a remote template.

Tighten the "Trust and evidence boundaries" section by consolidating the YAML tag-handling rules into a compact checklist to reduce token load.

DimensionReasoningScore

Conciseness

Assumes Claude's competence (no explanations of what OpenTelemetry or YAML are) and stays information-dense, but the "Trust and evidence boundaries" section's tag-handling prose is lengthy and could be tightened into a compact list.

4 / 5

Actionability

Provides concrete executable commands (gh release list, WebFetch URLs, bash export) and runtime-specific package/function names, but offers no complete inline YAML example — the core artifact must be fetched and adapted, a minor gap.

4 / 5

Workflow Clarity

Clear numbered generate process, three validation levels reported separately, explicit fail-closed feedback loops ("stop and diagnose", refetch after schema error), and a response-completion checklist — matching the explicit-checkpoints-and-feedback anchor.

5 / 5

Progressive Disclosure

Good section structure and clearly signaled one-level-deep references ("load references/declarative-setup.md", "load references/setup.md"), but those referenced files are absent from the bundle, so the deferred navigation resolves to nothing.

3 / 5

Total

16

/

20

Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, specific description that names concrete actions, supplies comprehensive trigger terms, and explicitly states both capability and activation conditions. It is well distinguished from adjacent OpenTelemetry skills by anchoring on config files rather than code.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions — "configuring OpenTelemetry SDK providers (tracer, meter, logger), setting up OTLP exporters, defining sampling strategies, or writing otel config files" — giving comprehensive coverage rather than a single vague verb.

5 / 5

Completeness

Explicitly answers both what ("OpenTelemetry declarative YAML configuration for SDK setup") and when ("Use when configuring...Triggers on...") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Comprehensive coverage of natural terms and synonyms a user would say, including "otel config", "OpenTelemetry YAML", "otelconf", "OTEL_CONFIG_FILE", and "configure tracing/metrics/logs export".

5 / 5

Distinctiveness Conflict Risk

Clear niche — declarative config-file setup rather than code — with distinct triggers ("OTEL_CONFIG_FILE", "otelconf") that minimize overlap with general instrumentation skills.

5 / 5

Total

20

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 2 missing

Warning

Total

15

/

16

Passed

Repository
ollygarden/opentelemetry-agent-skills
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.