CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

97%

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

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 strong, well-engineered skill body: an executable workflow with an explicit verify step, complete commands and manifest examples, and exemplary one-level-deep reference structure. The only weakness is conciseness at the margin — the dated version-pairing table mixes time-sensitive release data into the overview where a tighter rule statement would do.

Suggestions

Move the dated release/version-pairing table (the 'Verified 2026-10-25' rows) into a reference file or a clearly-labeled dated appendix, keeping only the pairing rules and one pinned example row in the body.

Tighten the 'Verified 2026-10-25' prose into a short rule statement (e.g. 'These pairings were verified 2026-10-25 against the linked tags; re-verify before deploying') instead of the multi-clause 'Offline, cite this date, never call a value currently latest...' sentence.

DimensionReasoningScore

Conciseness

The body is dense and lean — flag tables, complete manifests, and rule lists with almost no explanation of concepts Claude already knows ('The commands below use `ocb`, the release-archive binary name.'). It falls short of 5 because the dated 'Verified 2026-10-25' section carries time-sensitive version numbers/dates ('v0.163.0 ... tagged 2026-10-14', 'published as 0.163.0–0.163.2') plus awkward prose ('Offline, cite this date, never call a value currently latest, and confirm it against the evidence before deploying') that could be trimmed, which the rubric's time-sensitivity guideline penalizes. It is above 3 because nearly every section is actionable and there is no padded introductory material.

4 / 5

Actionability

Fully executable, copy-paste-ready guidance throughout: 'go install go.opentelemetry.io/collector/cmd/builder@v0.163.0', a complete minimal builder.yaml with pinned component versions, 'ocb --config=builder.yaml' variants, a full flag table with defaults, and the verify command './dist/<name> validate --config=<collector-config>.yaml'. Not 4: the concrete commands and complete manifest cover the common cases end to end, with only genuinely advanced detail delegated to references.

5 / 5

Workflow Clarity

A five-step workflow (Install → Write the manifest → Align versions → Build → Verify) with an explicit validation step ('run ./dist/<name> validate --config=<collector-config>.yaml, then start it and send test data') and error-recovery routing ('If the build fails, see references/troubleshooting.md'). The #1 failure mode (version alignment) is sequenced before the build step. Not 4: validation and failure feedback are explicit in the sequence, not implied, and builds are not destructive/batch operations so no cap applies.

5 / 5

Progressive Disclosure

The body is a concise overview (~120 lines) pointing to three one-level-deep reference files — references/manifest.md ('every manifest key'), references/workflows.md ('CI two-stage builds, Docker and multi-arch builds'), references/troubleshooting.md ('version mismatches, module conflicts...') — each verified to exist, match its described scope, and contain no nested references. References are linked inline at point of use and consolidated in a 'Reference files' section. Not 4: the split is clean, well-signaled, and trivially navigable.

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: concrete third-person capability statement, an explicit multi-condition 'Use when' clause, an enumerated trigger list with synonyms, and a distinct niche that won't collide with adjacent otel skills. No changes needed.

DimensionReasoningScore

Specificity

Multiple concrete actions with comprehensive coverage: 'Build custom OpenTelemetry Collector distributions with OCB', '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', and 'troubleshooting OCB build failures'. Not 4: the action list spans the full task lifecycle with no notable coverage gap.

5 / 5

Completeness

Clearly answers both questions: the 'what' is 'Build custom OpenTelemetry Collector distributions with OCB (OpenTelemetry Collector Builder)' and an explicit 'Use when' clause enumerates concrete conditions ('authoring or debugging a builder manifest ... setting up CI or Docker builds ... or troubleshooting OCB build failures'). Not 4: the 'when' is explicit and multi-conditioned rather than a single broad trigger.

5 / 5

Trigger Term Quality

Comprehensive natural-term coverage including synonyms and the config filename: 'Triggers on "ocb", "collector builder", "custom collector distribution", "builder manifest", "builder-config", and version-mismatch errors from OCB builds', plus 'builder.yaml' in the body of the description. Not 4: both the tool name and its manifest/config variants users would actually say are enumerated.

5 / 5

Distinctiveness Conflict Risk

Clear niche — building custom collector distributions — with distinct, qualified triggers ('ocb', 'builder manifest', 'version-mismatch errors from OCB builds') that are unlikely to fire for adjacent skills like collector configuration or component authoring. Not 4: the trigger list is anchored specifically to OCB builds rather than to the broader collector domain.

5 / 5

Total

20

/

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-collector-builder/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.