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

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

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.

The body delivers exceptional actionability — exact commands, URLs, package names, and entry points — and a well-gated workflow with explicit three-level validation and reporting requirements. Its weaknesses are conciseness (the security section and the Ruby table cell are overlong and repetitive) and progressive disclosure (the two referenced files are missing from the bundle, and per-language caveats that belong in those files are inlined instead).

Suggestions

Create (or fix the paths to) `references/declarative-setup.md` and `references/setup.md` — the Cross-References section currently points to files that do not exist in the bundle, so a loading session dead-ends.

Tighten the "Trust and evidence boundaries" section by consolidating its repeated untrusted-data and fail-closed statements into a single compact rule list; it currently restates the same posture several times.

Move the per-language bootstrap caveats (especially the ~90-word Ruby cell and the .NET note) into the referenced language files, keeping only the entry point and one-line summary in the main table.

Dimension	Reasoning	Score
Conciseness	The body is operationally dense with genuinely non-obvious runtime specifics, but the "Trust and evidence boundaries" section restates untrusted-data/fail-closed framing multiple times and the Ruby bootstrap cell is a ~90-word wall of caveats inline. Mostly efficient, but several passages could be tightened — not the padded verbosity of anchor 2, so 3.	3 / 5
Actionability	Fully executable guidance throughout: copy-paste `gh` commands with flags, exact WebFetch URLs, a bash export snippet, and exact package names and entry points (`NewSDK`, `DeclarativeConfiguration.parseAndCreate`, `startNodeSDK()`, `load_config_file()`) with the specific `OTEL_CONFIG_FILE` behavior per runtime. Matches the "copy-paste ready; covers common cases" anchor.	5 / 5
Workflow Clarity	A clear sequenced workflow (selection gate → fetch sources → generate → overlay values → validate) with three explicitly enumerated validation levels, explicit feedback loops ("refetch after a schema-related error", stop-and-diagnose on unclassified tags), and a response-completion checklist. This matches the top anchor: explicit validation steps, error-recovery loops, and a checklist.	5 / 5
Progressive Disclosure	Sections are well organized and references are clearly signaled one level deep, but both files cited in Cross-References (`references/declarative-setup.md`, `references/setup.md`) do not exist in the bundle, so navigation dead-ends. Additionally, per-language detail that belongs in the language references (the Ruby cell's long caveat list, the .NET note) is inlined in SKILL.md. This sits between the "could be better organized" anchor and the "most content appropriately placed" anchor; the broken references keep it at 3.	3 / 5
	Total	16 / 20 Passed

Description

87%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 that clearly and explicitly states both what the skill does and when to use it, with concrete trigger phrases and good synonym coverage. The only weaknesses are minor: "file_format" as a trigger is schema jargon rather than natural user phrasing, and coverage of the activation/precedence side of the task is lighter than the configuration-generation side.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete actions ("configuring OpenTelemetry SDK providers (tracer, meter, logger), setting up OTLP exporters, defining sampling strategies, or writing otel config files"), matching the "several specific actions; minor gaps" anchor. Coverage of activation/precedence and validation workflows is thinner than the comprehensive anchor, so it falls just below 5.	4 / 5
Completeness	Explicitly answers both what ("OpenTelemetry declarative YAML configuration for SDK setup" plus the enumerated provider/exporter/sampling actions) and when ("Use when configuring... Triggers on ... or when the user is setting up telemetry pipelines via config files rather than code") with concrete trigger phrases, matching the top anchor exactly.	5 / 5
Trigger Term Quality	Good keyword coverage with synonyms ("otel config", "otelconf", "OpenTelemetry YAML", "OTEL_CONFIG_FILE", "declarative configuration"), but "file_format" is a schema field name rather than a phrase users naturally say, and no file-extension terms (e.g. ".yaml") appear. Not clearly a match for the comprehensive anchor, so 4.	4 / 5
Distinctiveness Conflict Risk	Clear niche (OpenTelemetry declarative YAML configuration) with distinct triggers like "OTEL_CONFIG_FILE", "otelconf", and "declarative configuration" that users of this specific task would say. Minimal overlap risk with generic telemetry or general-YAML skills.	5 / 5
	Total	18 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
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
Commit: ea1a940

Reviewed: 18 hours ago

Table of Contents

Discovery Implementation Validation

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.