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

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

85%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 well-structured, actionable skill body with explicit validation checkpoints and clean one-level-deep reference navigation. It would tighten further by de-duplicating the Gotchas against the Non-Negotiable Rules and inlining one small template example.

Suggestions

De-duplicate Gotchas 3, 5, and 10 against the Non-Negotiable Rules (jq {"v2": true}, boundary domains, formatter) so each point lives in one place.

Inline one minimal .j2 template snippet (e.g. rendering span.name.note) so template authoring is actionable without opening references/template-authoring.md.

Collapse the Verification Contract's re-listed rules into a pointer to the Non-Negotiable Rules to recover token budget.

Dimension	Reasoning	Score
Conciseness	Dense and specialist, assuming Claude's knowledge of OTel/Rego/Jinja2, with every section earning its place; however the Gotchas repeat several points already in Non-Negotiable Rules (jq {"v2": true}, boundary domains, formatter), and the Verification Contract re-lists rules, so a little trimming is possible.	4 / 5
Actionability	Provides concrete, copy-paste-ready commands throughout (weaver registry check/generate with exact flags, formatter invocations, the comment(format="go") filter, jq helper calls with {"v2": true}) and a specific CLI arg-ordering gotcha; the main gap is that a template .j2 example is referenced out rather than shown inline.	4 / 5
Workflow Clarity	A numbered 5-step Workflow with a concrete command per step is paired with a dedicated Verification Contract that provides an explicit validate->fix->retry feedback loop (run check, capture, run generate+formatter, verify git diff --exit-code clean, re-read files) and a [x]/[~]/[ ] checklist.	5 / 5
Progressive Disclosure	SKILL.md is a clear overview that points to four real, one-level-deep references (registry-authoring, template-authoring, ci-integration, migration-playbook) plus two companion skills, all gathered in a clearly signaled "References To Load On Demand" section; bundle files and the inspect-resolved.sh script are present and correctly referenced.	5 / 5
	Total	18 / 20 Passed

Description

92%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 high-quality description: it states concrete capabilities, gives an explicit "Use when..." trigger with several specific scenarios, and occupies a clear niche. The only mild gap is breadth of everyday synonyms, which is inherently limited for a specialist tool.

Dimension	Reasoning	Score
Specificity	Names the domain and lists multiple specific concrete actions — "registry authoring, codegen, and CI enforcement" — then enumerates concrete sub-tasks (manifest/attributes/metrics/spans/events authoring, Jinja2 templates, migrating constants, wiring check/generate/diff into CI), giving comprehensive coverage.	5 / 5
Completeness	Explicitly answers both what ("registry authoring, codegen, and CI enforcement") and when ("Use when adopting Weaver, authoring or reviewing a registry..., writing Jinja2 templates..., migrating..., or wiring ... into CI") with concrete trigger phrases.	5 / 5
Trigger Term Quality	Strong natural trigger phrases ("adopting Weaver", "authoring or reviewing a registry", "writing Jinja2 templates", "migrating hand-maintained telemetry constants", "wiring ... into CI") cover the domain well, but synonym/file-extension breadth is limited for a specialist tool, so it sits above the midpoint rather than at full coverage.	4 / 5
Distinctiveness Conflict Risk	Scoped tightly to OpenTelemetry Weaver with distinct, domain-specific triggers, so it is unlikely to fire for an unrelated skill.	5 / 5
	Total	19 / 20 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: 8e6ed41

Reviewed: 16 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.