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

94%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Critical

Do not install without reviewing

Quality

Content

88%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 a dense, security-conscious procedural skill with executable commands, a well-sequenced workflow, explicit validation checkpoints, and clear cross-references. It is slightly verbose in recurring caveats and somewhat monolithic, which keeps conciseness and progressive disclosure at 4 while actionability and workflow clarity reach 5.

Suggestions

Consolidate the compatibility/precedence caveats that recur across "Sources of Truth", "Generate YAML", and "Response completion" into a single stated-once rule to reduce redundancy.

Move the full environment-variable substitution table and the extended trust/evidence-boundary prose into a referenced file, keeping SKILL.md as a lean overview with one-level-deep links.

Tighten the "Trust and evidence boundaries" section to bullet-form guardrails so the safety rules stay explicit but consume fewer tokens.

Dimension	Reasoning	Score
Conciseness	The body is information-dense and assumes Claude's competence (no basic OTel primers), but compatibility/precedence caveats recur across "Sources of Truth", "Generate YAML", and "Response completion", and some safety prose could be trimmed — efficient overall with minor removable redundancy, so it sits at 4 rather than the every-token-earns-its-place anchor of 5.	4 / 5
Actionability	Provides copy-paste-ready commands (the `gh release list/view ... --json` invocations), concrete `WebFetch` URLs with an explicitly explained `<schema-release-tag>` placeholder, a literal env-var export, and a substitution-syntax table — fully executable guidance covering the common cases.	5 / 5
Workflow Clarity	The 5-step "Generate YAML" procedure is clearly sequenced with a selection-gate checkpoint, three explicitly separated validation levels, fail-closed feedback ("fail closed when any other cap is reached"), and a "Response completion" checklist — matching the explicit-validation-and-feedback-loops anchor.	5 / 5
Progressive Disclosure	Well-organized into clearly headed sections with one-level-deep cross-references to sibling skills (otel-go/java/js/python load `references/declarative-setup.md`, otel-dotnet loads `references/setup.md`), but the SKILL.md itself is fairly monolithic and some inline detail (full substitution table, trust-boundary prose) could be split out, leaving it just below the cleanly-split anchor of 5.	4 / 5
	Total	18 / 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.

The description is specific, trigger-rich, and complete, clearly stating both the capability and the invocation conditions with natural user-facing terms. It is a strong, low-conflict description that earns top marks across all dimensions.

Dimension	Reasoning	Score
Specificity	Names the domain and multiple 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 minimal or generic list.	5 / 5
Completeness	Explicitly answers both what (declarative YAML SDK configuration with concrete provider/exporter/sampling tasks) and when ("Use when configuring... Triggers on...") with concrete trigger phrases, so it sits firmly at the top anchor rather than the partial-when anchor of 4.	5 / 5
Trigger Term Quality	Includes comprehensive natural triggers and synonyms — "otel config", "OpenTelemetry YAML", "declarative configuration", "otelconf", "OTEL_CONFIG_FILE", "configure tracing/metrics/logs export" — the phrases a user would actually say when needing this skill.	5 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (OpenTelemetry declarative YAML config) with distinct, domain-specific triggers, making overlap with unrelated skills minimal; it would not fire for general coding or non-OTel config tasks.	5 / 5
	Total	20 / 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: c5d2edc

Reviewed: about 3 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.