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

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-architected skill body with a concrete, validated workflow, executable examples, and clean progressive disclosure through a lean index plus on-demand detail files. Only minor conciseness trim potential in the summary table.

Dimension	Reasoning	Score
Conciseness	Efficient and assumes Claude's competence (no 'what is OpenTelemetry' preamble), but several component-index summary cells are dense and could be trimmed without losing routing value.	4 / 5
Actionability	Provides concrete executable guidance: exact file paths (components/<type>/README.md), a named-instance YAML example, and specific commands (otelcol-contrib --config <file>.yaml).	5 / 5
Workflow Clarity	A clearly sequenced 5-step workflow with an explicit Verify step as a validation checkpoint and concrete fallback instructions for unindexed components.	5 / 5
Progressive Disclosure	Clear overview routing to one-level-deep on-demand detail files (configuration.md, quirks.md, verification.md, advanced.md) with a well-signaled Details index pattern.	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 highly specific, well-structured description that explicitly covers what the skill does and when to use it, with comprehensive natural trigger terms and clear distinctiveness from sibling skills.

Dimension	Reasoning	Score
Specificity	Names the domain and multiple concrete actions ('authoring, reviewing, or debugging Collector YAML') plus a comprehensive facet list (config keys, defaults, validation rules, signal support, stability levels, gotchas) — clear anchor 5.	5 / 5
Completeness	Explicitly answers both what ('OpenTelemetry Collector component configuration') and when ('Use when authoring, reviewing, or debugging... Triggers on Collector component questions...').	5 / 5
Trigger Term Quality	Comprehensive natural terms covering every component kind ('receivers, processors, exporters, connectors, extensions'), plus 'component renames', 'signal support', and 'pipeline wiring' that users actually say.	5 / 5
Distinctiveness Conflict Risk	Narrow, distinct niche (individual Collector components) with concrete triggers; body further excludes OTTL, declarative config, and pipeline design, minimizing overlap with sibling skills.	5 / 5
	Total	20 / 20 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: 8e6ed41

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