CtrlK
BlogDocsLog inGet started
Tessl Logo

otel-collector

Expert guidance for configuring and deploying the OpenTelemetry Collector. Use when setting up a Collector pipeline, configuring receivers, exporters, or processors, deploying a Collector to Kubernetes or Docker, or forwarding telemetry to Dash0. Triggers on requests involving collector, pipeline, OTLP receiver, exporter, or Dash0 collector setup.

100

1.36x
Quality

100%

Does it follow best practices?

Impact

100%

1.36x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is an exceptionally well-structured skill. It provides a complete, executable quick start configuration, clear workflow with validation checkpoints, and excellent progressive disclosure through a comprehensive rules table and quick reference lookup. The key principles section efficiently communicates non-obvious, high-impact constraints without over-explaining.

DimensionReasoningScore

Conciseness

The content is lean and efficient. It avoids explaining what OpenTelemetry is or how YAML works. Every section serves a purpose: key principles state non-obvious gotchas, the quick start is a minimal working config, and the quick reference table is a dense lookup. No unnecessary padding.

3 / 3

Actionability

The quick start provides a complete, copy-paste-ready YAML configuration. The configuration workflow includes a specific validation command (`otelcol validate --config=config.yaml`). The key principles give concrete, actionable rules (e.g., 'Place memory_limiter first in every pipeline').

3 / 3

Workflow Clarity

The 4-step configuration workflow is clearly sequenced with an explicit validation step (step 2: validate locally) and a verification step (step 4: debug exporter). The key principles section serves as a checklist of critical constraints. The workflow includes feedback guidance (validate before deploy, verify after deploy, remove debug exporter before production).

3 / 3

Progressive Disclosure

The SKILL.md is an excellent overview that provides a concise quick start inline and delegates all detailed content to clearly labeled, one-level-deep rule files. The quick reference table maps specific user needs to the appropriate rule file. Navigation is intuitive and well-signaled.

3 / 3

Total

12

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a strong skill description that clearly defines its scope around OpenTelemetry Collector configuration and deployment. It excels in all dimensions by listing specific capabilities, providing explicit trigger guidance with natural keywords, and carving out a distinct niche. The inclusion of both 'Use when...' and 'Triggers on...' clauses makes it highly effective for skill selection.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: configuring Collector pipelines, configuring receivers/exporters/processors, deploying to Kubernetes or Docker, and forwarding telemetry to Dash0. These are concrete, actionable capabilities.

3 / 3

Completeness

Clearly answers both 'what' (configuring and deploying the OpenTelemetry Collector with specific sub-tasks) and 'when' (explicit 'Use when...' clause and a 'Triggers on...' clause listing specific trigger terms).

3 / 3

Trigger Term Quality

Includes strong natural keywords users would say: 'collector', 'pipeline', 'OTLP receiver', 'exporter', 'Dash0', 'Kubernetes', 'Docker', 'OpenTelemetry Collector'. Good coverage of terms a user would naturally use when needing this skill.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive with a clear niche around OpenTelemetry Collector configuration and deployment. The specific mentions of Dash0, OTLP receiver, Kubernetes/Docker deployment, and collector pipelines make it very unlikely to conflict with other skills.

3 / 3

Total

12

/

12

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.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
dash0hq/agent-skills
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.