otel-collector-builder

Build custom OpenTelemetry Collector distributions with OCB (OpenTelemetry Collector Builder). Use when authoring or debugging a builder manifest (builder.yaml), choosing component and provider versions, building a collector that bundles a custom or out-of-distribution component, setting up CI or Docker builds of a distribution, or troubleshooting OCB build failures. Triggers on "ocb", "collector builder", "custom collector distribution", "builder manifest", "builder-config", and version-mismatch errors from OCB builds.

Quality

92%

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-3

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

A well-structured, highly actionable skill body with a clear validated workflow and clean progressive disclosure to verified reference files. The only weakness is conciseness: pervasive time-sensitive version numbers used as examples will date the content and could be isolated.

Suggestions

Isolate concrete version numbers (v0.157.0, v1.63.0) into a single clearly-dated 'worked example' or 'current versions' callout, and rely on the already-cited authoritative default.yaml URL for the canonical pairing, so the body stays valid as versions advance.

Consider replacing a few of the repeated inline v0.157.0 examples with a placeholder like v0.x.0 once the pattern is established, to reduce staleness-sensitive tokens.

Dimension	Reasoning	Score
Conciseness	Lean and assumes Claude's competence (no basic OpenTelemetry explanations), but time-sensitive version numbers (v0.157.0 appears throughout, v1.63.0) are used as running examples rather than isolated in a deprecated/old-patterns section, which the guideline penalizes.	2 / 3
Actionability	Fully executable, copy-paste-ready guidance: `go install ...@v0.157.0`, a complete minimal manifest, concrete `ocb --config=builder.yaml` build commands with flag combinations, and a verify command.	3 / 3
Workflow Clarity	A clear 5-step numbered sequence with an explicit validation checkpoint in step 5 ("run ./dist/<name> validate --config=..." then "If the build fails, see references/troubleshooting.md"), giving a build→verify→recover feedback loop.	3 / 3
Progressive Disclosure	SKILL.md is an overview that points to three real, well-signaled one-level-deep references (manifest.md, workflows.md, troubleshooting.md — all verified to exist and self-contained), with content appropriately split and a navigation section listing each file's contents.	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 strong, specific description that names concrete actions, provides explicit natural-language triggers, answers both what and when, and occupies a clearly distinct niche. No fluff or over-claims; voice follows the endorsed 'Use when...' imperative pattern.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "authoring or debugging a builder manifest", "choosing component and provider versions", "building a collector that bundles a custom or out-of-distribution component", "setting up CI or Docker builds", "troubleshooting OCB build failures" — matching the multiple-specific-actions anchor.	3 / 3
Completeness	Answers both what ("Build custom OpenTelemetry Collector distributions with OCB") and when ("Use when authoring or debugging..." plus the explicit Triggers clause), matching the what-AND-when anchor.	3 / 3
Trigger Term Quality	The explicit "Triggers on 'ocb', 'collector builder', 'custom collector distribution', 'builder manifest', 'builder-config', and version-mismatch errors" clause gives good coverage of natural terms a user would actually say.	3 / 3
Distinctiveness Conflict Risk	A clear niche (OCB / custom collector distributions) with distinct triggers, and the body explicitly defers adjacent tasks to `otel-collector` and `otel-telemetrygen`, making conflict unlikely.	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-collector-builder/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.