otel-collector

OpenTelemetry Collector component configuration. Use when authoring, reviewing, or debugging Collector YAML for a specific receiver, processor, exporter, connector, or extension — config keys, defaults, validation rules, signal support, stability levels, and component-level gotchas. Triggers on Collector component questions including receivers, processors, exporters, connectors, extensions, component renames, signal support, and pipeline wiring.

Quality

92%

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

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, actionable overview with a clear sequenced workflow (including an explicit verification checkpoint) and an exemplary progressive-disclosure design that pushes detail into one-level-deep, clearly-signaled files. The main weakness is verbosity in the component-index summaries, which carry reference-grade config detail that belongs in the deferred detail files.

Suggestions

Tighten the Component index summaries to kind/signals/stability plus a one-line use-case; move config-reference detail (e.g. the prometheus_remote_write row's full key list, TLS/compression defaults, RW1 drop rules) into each component's configuration.md, consistent with the skill's own lean-README philosophy.

Relocate the "Adding a new component to this skill" authoring meta-section into a separate maintainer reference file so it does not consume the always-loaded SKILL.md overview budget.

Compress the per-signal stability annotations in the index table (e.g. "Beta (traces), Alpha (logs/metrics)") to a single concise form, deferring the per-signal breakdown to each component's README metadata table.

Dimension	Reasoning	Score
Conciseness	The body is dense and assumes Claude's competence (no basic-concept padding), but several index summaries carry config-reference detail (e.g. the prometheus_remote_write row: "TLS on by default... snappy-only compression, remote_write_queue... Drops non-cumulative monotonic sums...") that the skill's own philosophy defers to configuration.md, and the meta "Adding a new component" section adds length — mostly efficient but could be tightened. Not 3 because not every token earns its place in an always-loaded overview; not 1 because there is no unnecessary concept explanation or fluff.	2 / 3
Actionability	Provides a complete, copy-paste-ready named-instances YAML block plus concrete commands ("otelcol-contrib --config <file>.yaml", the OCB builder, telemetrygen) and specific config defaults throughout, matching the score-3 anchor of fully executable code and commands.	3 / 3
Workflow Clarity	A clear 5-step Workflow with an explicit validation checkpoint ("5. Verify. Run the component page's Verification recipe") and a concrete verification-harness checklist (save YAML, start collector, send telemetry, watch debug/file output); not 2 because checkpoints are explicit rather than implicit.	3 / 3
Progressive Disclosure	Exemplary one-level-deep design: a lean overview + component index pointing at components/<type>/README.md, a clearly signaled Details index pattern ("- [Configuration](configuration.md) — config keys, defaults, validation"), and explicit guidance splitting content into on-demand detail files. No bundle files were present to verify, so this is scored on the described structure, which matches the score-3 anchor.	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 and aspects, uses natural domain trigger terms, and explicitly states both what it does and when to use it in third-person voice. It is clearly distinguishable from sibling skills and unlikely to conflict.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ("authoring, reviewing, or debugging Collector YAML") and concrete aspects ("config keys, defaults, validation rules, signal support, stability levels, and component-level gotchas"), matching the score-3 anchor of multiple specific concrete actions.	3 / 3
Completeness	Clearly answers what ("OpenTelemetry Collector component configuration") and when ("Use when authoring, reviewing, or debugging Collector YAML..."; "Triggers on Collector component questions including..."), satisfying the score-3 anchor of explicit what-and-when with triggers.	3 / 3
Trigger Term Quality	Covers the natural domain terms a user would actually say ("receiver, processor, exporter, connector, or extension"; "component renames, signal support, and pipeline wiring"), giving good coverage rather than jargon-only or generic phrasing.	3 / 3
Distinctiveness Conflict Risk	Clearly niched to OpenTelemetry Collector component configuration with distinct component-level triggers, making it unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 1 missing	Warning

	Total	15 / 16 Passed

Repository: ollygarden/opentelemetry-agent-skills
Path: skills/otel-collector/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.