CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

81%

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

67%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-engineered routing skill with a clear workflow, explicit verification, and an excellent one-level-deep disclosure design. Its main cost is token weight: dense version-stamped index cells, duplicated notes, and dated verification paragraphs that could be trimmed or pushed into the per-component files.

Suggestions

Slim the Component index summary cells to one-line routing cues and move version history (e.g. drain's masking_rules rename, interval's aggregation semantics, k8s_attributes gate changes) into the corresponding components/<type>/quirks.md, keeping the index a pure router as the workflow claims it is.

Consolidate the sending_queue.batch guidance — currently repeated in both the otlp_grpc index row and the Pipeline placement section — into a single location.

Move the dated verification provenance (the two "Verified 2026-10-xx" paragraphs) into a small maintenance/versioning note or the component pages, and add a one-line instruction for what to do when a Verification recipe's observed output disagrees with the documented behavior.

DimensionReasoningScore

Conciseness

The body avoids re-explaining OTel basics, but index-table cells carry version-history detail that belongs in per-component pages (e.g. the drain masking_rules rename and interval aggregation semantics), the sending_queue.batch note is stated twice (otlp_grpc row and Pipeline placement), and pervasive version numbers plus two "Verified 2026-10-xx" paragraphs are not quarantined in a deprecation/old-patterns section. Mostly efficient but with unnecessary detail and tightening opportunities fits the 3 anchor rather than the 4 anchor's minor over-explanation.

3 / 5

Actionability

Concrete, executable guidance throughout: a named-instance YAML example, verification commands (otelcol-contrib --config, OCB build step, telemetrygen + debug exporter), an explicit upstream-README fallback, and a concrete component-authoring template. It falls short of the 5 anchor because the copy-paste common-case configs are deferred to component pages rather than shown inline.

4 / 5

Workflow Clarity

The five-step workflow is clearly sequenced with an explicit verification step, an unindexed-fallback recovery path, and anti-hallucination checkpoints ("Do not infer exact configuration or status from the summary row or memory"). It misses the 5 anchor because there is no guidance for what to do when the verification output does not match the documented behavior — a minor validation gap.

4 / 5

Progressive Disclosure

The structure is a well-signaled, one-level-deep hierarchy (lean component README with a Details index pointing to configuration.md, verification.md, advanced.md, quirks.md) with a disciplined split policy and reference implementations. Minor gaps: the components/ files referenced are not present in the bundle to verify, and index summary cells partially inline detail that belongs in the component detail files, keeping it below the 5 anchor's fully appropriate split.

4 / 5

Total

15

/

20

Passed

Description

88%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 description: concrete, third-person, with an explicit "Use when" clause and a second trigger sentence covering natural Collector vocabulary. The only weaknesses are a few missing synonyms and slight overlap risk with closely related OTel skills via the "pipeline wiring" trigger.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions ("authoring, reviewing, or debugging Collector YAML") across all five component kinds, plus the knowledge areas covered ("config keys, defaults, validation rules, signal support, stability levels, and component-level gotchas"), which is comprehensive for the domain. It exceeds the 4 anchor because no meaningful capability gaps are visible.

5 / 5

Completeness

Both questions are answered explicitly and concretely: "what" via "OpenTelemetry Collector component configuration … config keys, defaults, validation rules …" and "when" via an explicit "Use when authoring, reviewing, or debugging Collector YAML" clause plus a second "Triggers on Collector component questions" sentence. This matches the 5 anchor's clear and explicit what-and-when with concrete trigger phrases.

5 / 5

Trigger Term Quality

"receivers, processors, exporters, connectors, extensions, component renames, signal support, and pipeline wiring" are natural terms users say when asking Collector questions, but a few common synonyms are absent ("otel", "otelcol", "collector-contrib", and specific component names like "filelog"). Good coverage with a few natural terms missing fits the 4 anchor rather than the 5 anchor's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

The component-configuration niche is clear and the triggers (component renames, receivers, processors) are distinctive, but "pipeline wiring" and "signal support" have minor overlap with closely related sibling skills (pipeline design, OTTL) that the body excludes yet the description does not disambiguate. Mostly distinct with minor overlap risk fits 4 rather than the 5 anchor's minimal conflict risk.

4 / 5

Total

18

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

relative_links

Relative link issues: 1 missing

Warning

Total

15

/

16

Passed

Repository

ollygarden/opentelemetry-agent-skills

Path

skills/otel-collector/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.