CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

81%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.

The body is exceptionally actionable and operationally safe — concrete commands, verified compatibility pins, explicit validation levels, and strong untrusted-input handling — with a clear sequenced workflow and feedback loops. Its weaknesses are token efficiency (version-dense dated tables and long inline runtime detail that belongs in reference files) and a couple of reference paths that are not resolvable within this bundle.

Suggestions

Move the per-runtime activation detail (especially the long Ruby row) and the detailed parser-evidence rows into references/runtime-compatibility.md or a dedicated activation reference, keeping only the runtime name and entry-point summary in SKILL.md.

Consolidate the dated version pins into a single clearly-marked compatibility section that explicitly routes to the reference file for evidence, or add an 'old patterns' style subsection so stale pins don't penalize the evergreen guidance.

Tighten the 'Trust and evidence boundaries' prose into a short bulleted checklist of caps and rejection rules; the ~20-line paragraph is hard to scan and could be trimmed without losing any rule.

DimensionReasoningScore

Conciseness

No padding or explanation of known concepts, but the body is dense with time-sensitive version pins ("Parsers verified 2026-10-25", Java 1.67.0, JS 0.301.0, Ruby 0.2.0) that are not in an 'old patterns'/'deprecated' section, and long prose blocks like the ~20-line "Trust and evidence boundaries" paragraph and the Ruby activation row could be tightened or moved to references. Fits the 3 anchor ("mostly efficient but... could be tightened") better than 4, whose "minor instances" understates the version-heavy table and dense inline detail.

3 / 5

Actionability

Fully executable, copy-paste-ready commands: `gh release list --repo open-telemetry/opentelemetry-configuration --exclude-drafts --json tagName,publishedAt --limit 100`, concrete WebFetch URL templates, `export OTEL_CONFIG_FILE=/app/configs/otel.yaml`, exact package coordinates (io.opentelemetry:opentelemetry-sdk-extension-declarative-config) and API entry points (NewSDK, DeclarativeConfiguration.parseAndCreate, startNodeSDK, load_config_file). The absence of an inline YAML example is explicitly justified — the file_format literal must be verified per runtime, and the tagged canonical example is prescribed as the template.

5 / 5

Workflow Clarity

Clear sequencing with explicit validation checkpoints and feedback loops: the 5-step "Generate YAML" numbered workflow, ordered evidence precedence with stop conditions, three separately-reported validation levels with "never claim one that was not run", refetch-after-schema-error and stop-and-diagnose-on-bad-tag loops, and the "Response completion" checklist. Matches the 5 anchor; no destructive/batch cap applies since validation is pervasive.

5 / 5

Progressive Disclosure

Good structure with a clearly-signaled one-level-deep reference ("read [`references/runtime-compatibility.md`](references/runtime-compatibility.md)" with a stated purpose, and that file links no further files), but not a 5: heavy per-runtime detail (the very long Ruby activation paragraph, the dense trust/evidence section) stays inline in SKILL.md, and two of the named reference paths (references/declarative-setup.md, references/setup.md) do not exist in this bundle, leaving minor navigation gaps.

4 / 5

Total

17

/

20

Passed

Description

95%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 description in third-person voice: it names the domain and several concrete capabilities, gives an explicit 'Use when' clause, and enumerates eight natural trigger phrases including the package name and environment variable. Only minor capability coverage is missing relative to the skill body.

DimensionReasoningScore

Specificity

Lists several concrete actions — "configuring OpenTelemetry SDK providers (tracer, meter, logger)", "setting up OTLP exporters", "defining sampling strategies", "writing otel config files" — which is well above the 1-2 actions of a 3, but not a 5 because body-level capabilities like activation/OTEL_CONFIG_FILE precedence and env-var substitution are absent, leaving minor gaps in coverage.

4 / 5

Completeness

Explicitly answers both questions: what ("OpenTelemetry declarative YAML configuration for SDK setup") and when ("Use when configuring OpenTelemetry SDK providers... Triggers on \"otel config\"...") with concrete trigger phrases. Matches the 5 anchor exactly; the 'when' clause cannot be more explicit than the enumerated trigger list.

5 / 5

Trigger Term Quality

Comprehensive natural-term coverage including synonyms and identifiers users would actually say: "otel config", "OpenTelemetry YAML", "declarative configuration", "otelconf", "OTEL_CONFIG_FILE", "file_format", plus the disambiguating phrase "setting up telemetry pipelines via config files rather than code". Anchor 4 ("a few natural terms missing") fits less well since both casual phrasings and the package/env-var names are covered.

5 / 5

Distinctiveness Conflict Risk

Clear niche with distinct triggers — OTEL_CONFIG_FILE, otelconf, file_format, and "via config files rather than code" explicitly separates it from programmatic-SDK and generic OpenTelemetry skills, satisfying the 5 anchor ("clear niche with distinct triggers; minimal conflict risk"). Not a 4 because no meaningful overlap risk remains with closely related skills.

5 / 5

Total

19

/

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.

Validation — 15 / 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

Path

skills/otel-declarative-config/SKILL.md

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.