CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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, wiring `weaver registry check`/`generate`/`diff` into CI, or choosing a Weaver version for a semantic-conventions release.

Quality

94%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

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.

A high-quality, highly actionable skill body: executable commands with argument-ordering traps, a five-step workflow, and an unusually strong verification contract with a checklist. The main costs are token-level — repeated restatements of the same rules and inline version/date stamps — plus one undiscovered bundle script.

Suggestions

Consolidate repeated guidance: state the formatter-on-output rule and the boundary-domain rule once each (e.g., in Non-Negotiable Rules) and let the Workflow and Verification Contract reference them by name, cutting roughly 10-15 lines of duplicated tokens.

Move time-sensitive version/date facts ('since v0.22.0', 'semconv v1.44.0', dated-record callouts) into a short 'Versioned/deprecated notes' section or into the already-dated references/ci-integration.md record, so the main body stays version-stable.

Add a one-line pointer to scripts/inspect-resolved.sh in the body (e.g., under References To Load On Demand) so the bundle's only script is discoverable from the main file.

DimensionReasoningScore

Conciseness

The body is dense and assumes Claude's competence — no generic OTel or YAML explanations — but several rules are repeated three to four times (formatter-on-output in Non-Negotiable Rules, Workflow step 4, Gotcha 2, and the Verification Contract; boundary-domain advice and the {"v2": true} jq flag each appear three times), and inline time-sensitive version/date stamps ('since v0.22.0', 'v1.44.0', 'still so in the dated record') sit outside any deprecated/old-patterns section. This is tightening work rather than padding, so 4 rather than 3.

4 / 5

Actionability

Fully executable, copy-paste-ready commands with concrete paths: 'weaver registry check --v2 -r ./telemetry/registry/', the full 'weaver registry generate --v2 --registry ... --templates ... <lang> <output-dir>' invocation with the argument-ordering gotcha, 'gofmt -w', 'prettier', 'ruff format', 'git diff --exit-code', plus exact syntax like 'semconv_grouped_spans({"v2": true})' and "attr.brief | comment(format="go")". Specific examples cover the common cases.

5 / 5

Workflow Clarity

The five-step Workflow (install, author registry, author templates, validate+generate, wire CI) gives each step its exact command, and the Verification Contract adds explicit validate-then-fix-then-recheck loops ('run weaver registry check --v2 ... and capture the result', 'run weaver registry generate --v2 and the language formatter, then verify git diff --exit-code is clean') plus a [x]/[~]/[ ] checklist. This matches the anchor with explicit validation steps, feedback loops, and checklists.

5 / 5

Progressive Disclosure

The body is a genuine overview with a dedicated 'References To Load On Demand' section giving one-line descriptions per file, and all four referenced files (registry-authoring.md, template-authoring.md, ci-integration.md, migration-playbook.md) exist and are one level deep. The gap keeping it below 5: scripts/inspect-resolved.sh is a real bundle file but is never surfaced from SKILL.md (only from a reference's comments), and the 12-item Gotchas list is borderline content that could partly live in references.

4 / 5

Total

18

/

20

Passed

Description

96%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: it states concrete capabilities in third person, includes an explicit and richly enumerated 'Use when...' clause, and is scoped tightly to the Weaver tool so it triggers precisely. The only weak point is slight trigger overlap with the closely related otel-semantic-conventions domain.

DimensionReasoningScore

Specificity

Lists multiple concrete actions spanning the skill's full surface: 'authoring or reviewing a registry (manifest, attributes, metrics, spans, events)', 'writing Jinja2 templates against the resolved schema', 'migrating hand-maintained telemetry constants', 'wiring `weaver registry check`/`generate`/`diff` into CI', and 'choosing a Weaver version'. Coverage is comprehensive across authoring, templating, migration, CI, and versioning, exceeding the 'minor gaps' bar of a 4.

5 / 5

Completeness

Explicitly answers both parts: the 'what' ('OpenTelemetry Weaver registry authoring, codegen, and CI enforcement') and a full 'Use when...' clause enumerating six concrete trigger scenarios (adopting Weaver, authoring/reviewing a registry, writing templates, migrating constants, wiring CI, choosing a version).

5 / 5

Trigger Term Quality

Includes the natural terms a user needing this skill would say — 'Weaver', 'registry', 'manifest', 'attributes, metrics, spans, events', 'Jinja2 templates', 'migrating hand-maintained telemetry constants', 'CI' — plus exact subcommand names (`weaver registry check`/`generate`/`diff`). No commonly used phrasing for this domain is missing, so it sits above the 'a few natural terms missing' anchor of 4.

5 / 5

Distinctiveness Conflict Risk

The tool name 'Weaver' anchors nearly every trigger, giving a clear niche with minimal wrong-skill triggering. However, 'authoring or reviewing a registry (manifest, attributes, metrics, spans, events)' and 'choosing a Weaver version for a semantic-conventions release' sit adjacent to a companion semantic-conventions skill's territory, so minor overlap risk with a closely related skill remains — matching anchor 4 rather than the minimal-conflict anchor 5.

4 / 5

Total

19

/

20

Passed

Validation

100%

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

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.