CtrlK
BlogDocsLog inGet started
Tessl Logo

otel-ottl

OpenTelemetry Transformation Language (OTTL) expert for writing and debugging telemetry transformations in the OpenTelemetry Collector. Use when authoring or reviewing `transform`, `filter`, `tail_sampling` processor configs or `routing` connector configs, debugging OTTL syntax or semantics, transforming traces, metrics, logs, or profiles, or converting data-processing requirements into OTTL statements.

79

Quality

100%

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

100%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 tight, high-signal body: actionable OTTL examples, a sequenced workflow with an explicit end-to-end validation step, well-signaled one-level references to real bundle files, and no concept-explaining padding. It reaches the top anchor on all four dimensions.

DimensionReasoningScore

Conciseness

The body is lean and assumes competence — no explaining what OTel or the Collector is — and every section (workflow, gates, traps, sources) earns its tokens; the version pins are load-bearing correctness anchors rather than decorative time-sensitive noise, so it sits at the 'lean and efficient' anchor rather than the 'could be tightened' one.

3 / 3

Actionability

Provides fully executable, copy-paste-ready guidance — the OTTL block 'set(span.attributes["env"], "prod") where resource.attributes["env"] == nil', concrete guards 'where x != nil', 'IsString(x)', YAML escaping '$${1}', and 'Decode(value, "base64")' — far above the pseudocode/vague anchors.

3 / 3

Workflow Clarity

A clear five-step sequence culminating in an explicit validation checkpoint ('Validate the exact Collector version, then send known telemetry and inspect file-exporter output') plus a Safety-gates checklist, matching the anchor for clear sequencing with explicit validation and feedback loops.

3 / 3

Progressive Disclosure

SKILL.md is an overview that signals one-level-deep references — 'Contexts', 'Functions', 'Quick reference' — each with a one-line description and confirmed real files in ./references/, plus a 'read only the relevant section' instruction, fitting the 'clear overview with well-signaled one-level-deep references' anchor.

3 / 3

Total

12

/

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.

An exemplary description: concrete actions, natural trigger terms, explicit 'Use when' guidance, and a distinct OTel-Collector/OTTL niche, all in concise third person. It satisfies the highest anchor on every dimension.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'writing and debugging telemetry transformations', 'authoring or reviewing transform, filter, tail_sampling processor configs or routing connector configs', 'converting data-processing requirements into OTTL statements' — matching the 'multiple specific concrete actions' anchor.

3 / 3

Completeness

Explicitly answers both what ('writing and debugging telemetry transformations in the OpenTelemetry Collector') and when ('Use when authoring or reviewing ... debugging OTTL syntax or semantics ...'), with an explicit 'Use when' trigger clause, so it does not cap at 2.

3 / 3

Trigger Term Quality

Covers natural terms an OTel Collector user would actually say — 'OTTL syntax or semantics', 'transform, filter, tail_sampling processor configs', 'routing connector configs', 'transforming traces, metrics, logs, or profiles' — with good variation rather than jargon-only phrasing.

3 / 3

Distinctiveness Conflict Risk

The OTTL/Collector niche with component-specific triggers (transform, filter, tail_sampling, routing) is a clear, distinct domain unlikely to fire for unrelated skills; it is below the level-2 'could still overlap' anchor.

3 / 3

Total

12

/

12

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 suspicious

Warning

Total

15

/

16

Passed

Repository
ollygarden/opentelemetry-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.