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

96%

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

92%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 build skill with a clear validated workflow and clean one-level-deep reference split. The only weakness is repeated hard-coded version numbers that age the content and slightly inflate the token budget.

Suggestions

Replace repeated concrete version numbers (v0.160.0, v1.66.0) with a single placeholder or a 'current as of' note plus the authoritative default-manifest URL, so the skill does not silently go stale.

Consider moving the version-alignment example versions into a small version-mapping table in references/manifest.md and keeping the body version-agnostic.

Dimension	Reasoning	Score
Conciseness	Dense and largely free of padding — no preamble explaining what OpenTelemetry is, mostly tables and executable blocks. Hard-coded version numbers (v0.160.0, v1.66.0) repeated throughout are time-sensitive and not isolated in a deprecated/old-patterns section, which trims it off the top anchor.	4 / 5
Actionability	Copy-paste ready throughout: a complete minimal manifest, concrete install commands, and an explicit flag table with defaults and purposes covering the common build cases.	5 / 5
Workflow Clarity	A five-step workflow with an explicit validation checkpoint ('Verify: run ./dist/<name> validate --config=...') and an error-recovery pointer to troubleshooting when the build fails.	5 / 5
Progressive Disclosure	Body is a concise overview with three clearly signaled, one-level-deep reference files (manifest.md, workflows.md, troubleshooting.md), all of which exist in references/; content is appropriately split with easy navigation.	5 / 5
	Total	19 / 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.

A strong, third-person description that concretely states capabilities, provides explicit 'Use when' and 'Triggers on' guidance, and is clearly distinguishable from related OpenTelemetry skills. It hits the top anchor on every dimension.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Build custom OpenTelemetry Collector distributions', 'authoring or debugging a builder manifest', 'choosing component and provider versions', 'setting up CI or Docker builds', 'troubleshooting OCB build failures' — with comprehensive coverage of the skill's scope.	5 / 5
Completeness	Clearly answers both 'what' ('Build custom OpenTelemetry Collector distributions with OCB') and 'when' via an explicit 'Use when' clause plus a dedicated 'Triggers on' list with concrete trigger phrases.	5 / 5
Trigger Term Quality	Explicit 'Triggers on' set includes natural phrases and synonyms users would say — 'ocb', 'collector builder', 'custom collector distribution', 'builder manifest', 'builder-config', plus the file artifact 'builder.yaml'.	5 / 5
Distinctiveness Conflict Risk	Occupies a narrow, well-defined niche (the OCB builder tool) with distinct trigger vocabulary unlikely to fire for adjacent collector-config or telemetrygen skills.	5 / 5
	Total	20 / 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-collector-builder/SKILL.md
Commit: 8e6ed41

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