otel-weaver

OpenTelemetry Weaver registry authoring, codegen, and CI enforcement. Use when adopting Weaver, authoring or reviewing a registry (manifest, attributes, metrics, spans, events), writing Jinja2 templates against the resolved schema, migrating hand-maintained telemetry constants, or wiring `weaver registry check`/`generate`/`diff` into CI.

Quality

92%

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

85%Weight 40%Scale 1-3

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

A dense, highly actionable skill body with concrete commands, a real CI example, an executable helper script, and a strong verification checklist. Its only weakness is conciseness: load-bearing but time-sensitive version numbers are scattered inline and one rule is restated in three places.

Suggestions

Consolidate version-pinned facts (v0.25.1, semconv v1.43.0, v0.22.0 auto-escaping) into a single 'Version notes' or 'Deprecated/old patterns' section so the main flow stays evergreen and conciseness is not penalized for time-sensitive detail.

State the boundary-domain rule (http/db/messaging/rpc/network/gen-ai belong upstream, not locally) once in Non-Negotiable Rules and reference it from Gotcha #10 and the Verification Contract instead of repeating the full list three times.

Move the deeper per-field registry and template-shape detail — already in the reference files — out of inline Gotchas where it duplicates the references, keeping Gotchas to one-line pitfalls.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and free of basic-concept padding, but pervasive time-sensitive version pins (v0.25.1, v1.43.0, v0.22.0) appear inline rather than in a deprecated/old-patterns section, and the boundary-domain rule is repeated across Non-Negotiable Rules, Gotcha #10, and the Verification Contract — so not every token earns its place.	2 / 3
Actionability	Provides exact, copy-paste-ready commands (`weaver registry check --v2 -r ...`, `weaver registry generate --v2 ...`), a complete GitHub Actions YAML in the CI reference, an executable `scripts/inspect-resolved.sh`, and named jq helpers — fully executable guidance.	3 / 3
Workflow Clarity	A clear 5-step Workflow is paired with a dedicated Verification Contract checklist and explicit validation checkpoints (`check`, `git diff --exit-code`, `diff` against base branch) plus error-recovery guidance, matching the 'clear sequence with explicit validation steps' anchor.	3 / 3
Progressive Disclosure	The body is an overview with a 'References To Load On Demand' section pointing to four real reference files (registry-authoring, template-authoring, ci-integration, migration-playbook) and one real script, all verified present, inline-signaled and only one level deep — well-structured navigation.	3 / 3
	Total	11 / 12 Passed

Description

100%Weight 40%Scale 1-3

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 precise, trigger-rich description that names concrete capabilities and an explicit 'Use when ...' clause covering several distinct adoption scenarios. It is distinguishable from adjacent telemetry skills and avoids fluff or voice problems.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'registry authoring, codegen, and CI enforcement', 'writing Jinja2 templates against the resolved schema', 'migrating hand-maintained telemetry constants', and 'wiring `weaver registry check`/`generate`/`diff` into CI' — matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	Explicitly states what ('OpenTelemetry Weaver registry authoring, codegen, and CI enforcement') and when ('Use when adopting Weaver, authoring or reviewing a registry ...'), satisfying the 'clearly answers both what AND when with explicit triggers' anchor.	3 / 3
Trigger Term Quality	Covers natural terms a user adopting the tool would say ('adopting Weaver', 'authoring or reviewing a registry', 'writing Jinja2 templates', 'migrating hand-maintained telemetry constants', 'wiring ... into CI'); uses the recommended imperative 'Use when...' trigger form rather than second person, so no voice penalty applies.	3 / 3
Distinctiveness Conflict Risk	Targets a narrow, clearly named tool (OpenTelemetry Weaver) with distinct triggers unlikely to fire for unrelated skills, matching the 'clear niche with distinct triggers' anchor.	3 / 3
	Total	12 / 12 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: ollygarden/opentelemetry-agent-skills
Path: skills/otel-weaver/SKILL.md
Commit: c5d2edc

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