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 high-quality body: every section adds non-obvious domain knowledge (version pairing, providers replacement semantics, flag defaults), commands are copy-paste ready, and details are properly pushed to three well-signaled reference files. The only weakness is scattered time-sensitive version pins that will go stale and slightly pad the token budget.

Suggestions

Centralize the concrete version examples (v0.162.0, v1.68.0, v1.1.0, 'since v0.154.0') into one 'worked example' or version-matrix block, keeping the general pairing rules and the authoritative-source pointers (release default.yaml, contrib versions.yaml) in the body so the content ages gracefully.

Trim per-release minutiae such as the exact stable-base membership for v0.162.0 into references/manifest.md or a version table, retaining only the rule for finding the pairing.

Dimension	Reasoning	Score
Conciseness	The body is lean and information-dense with no explanation of concepts Claude already knows, but time-sensitive pins ("v0.162.0", "v1.68.0", "v1.1.0", "Since v0.154.0") are scattered throughout rather than centralized or placed in an old-patterns/deprecated section, which is exactly the kind of content that could be trimmed per the time-sensitive guideline.	4 / 5
Actionability	Fully executable, copy-paste-ready guidance: a pinned install command ("go install go.opentelemetry.io/collector/cmd/builder@v0.162.0"), a complete minimal builder.yaml, exact build commands with flags, and a concrete verify command ("./dist/<name> validate --config=<collector-config>.yaml").	5 / 5
Workflow Clarity	The 5-step Workflow is clearly sequenced with an explicit Verify step (validate config, then start and send test data) and an error-recovery path ("If the build fails, see references/troubleshooting.md"); the top failure mode (version alignment) is flagged up front with rules to prevent it.	5 / 5
Progressive Disclosure	SKILL.md stays an overview (minimal manifest, key rules, flags) and pushes full key reference, CI/Docker/local-component workflows, and troubleshooting into three real, one-level-deep reference files, each clearly summarized and linked inline — easy navigation with no nesting.	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.

An exemplary description: third-person/declarative voice, concrete capability list, explicit 'Use when...' clause, and a rich set of natural trigger terms including the tool acronym, synonyms, and the manifest filename. No fluff, over-claims, or overlap risk identified.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete actions — "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", "troubleshooting OCB build failures" — with comprehensive coverage and no vague filler.	5 / 5
Completeness	It explicitly answers both what ("Build custom OpenTelemetry Collector distributions with OCB") and when ("Use when authoring or debugging a builder manifest... or troubleshooting OCB build failures"), plus an explicit trigger list with concrete phrases.	5 / 5
Trigger Term Quality	Natural trigger terms include the acronym ("ocb"), synonyms ("collector builder", "builder manifest", "builder-config", "custom collector distribution"), the filename "builder.yaml", and "version-mismatch errors" — coverage comparable to the anchor-5 example including synonyms and file extensions.	5 / 5
Distinctiveness Conflict Risk	A clear niche (OCB distribution builds) with tool-specific triggers ("ocb", "builder manifest", "custom collector distribution") that are unlikely to fire adjacent skills such as general collector configuration; no generic language that would conflict.	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: ea1a940

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