CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

96%

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

93%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.

The content is an exemplary expert skill body: token-efficient, version-pinned facts with zero padding, executable inline examples, and a clear workflow culminating in end-to-end validation, backed by well-organized one-level-deep reference files. The only notable gap is that the recovery loop after a failed validation is implied rather than explicit.

Suggestions

In step 5, close the feedback loop explicitly: state what to do when file-exporter output does not match expectations (e.g., re-check statement guards and function signatures, then re-run telemetrygen).

Name the specific artifact to inspect during verification (e.g., the exported OTLP JSON/traces file and which fields to spot-check) so the validation step is unambiguous even before consulting the telemetrygen recipe.

DimensionReasoningScore

Conciseness

The body never explains concepts Claude already knows (no "what is OpenTelemetry" preamble) and every line carries non-obvious, version-pinned facts such as "the transform default-error gate was removed in v0.162.0" and "`Base64Decode` was removed in v0.161". Not 4: there is no over-explanation to trim; the one orienting sentence ("OTTL transforms or selects telemetry inside Collector components") is necessary framing, and the version/date facts are organized as pinned status rather than time-conditional instructions.

5 / 5

Actionability

Guidance is fully executable: copy-paste-ready statements like `set(span.attributes["env"], "prod") where resource.attributes["env"] == nil`, a complete guard `IsString(log.body) and IsMatch(log.body.string, "(?s)^\\s*\\{.*\\}\\s*$")`, exact path spellings (`otelcol.client.metadata["X-Tenant"][0]`), and concrete workflow actions ("Confirm each function's exact identifier and signature in references/functions.md", "send known telemetry and inspect file-exporter output"). Not 4: the inline examples plus linked catalogs cover the common cases with no gaps.

5 / 5

Workflow Clarity

The five numbered steps are clearly sequenced (component → context → verify functions → error behavior → verify end to end) with an explicit validation step, and the "Safety and correctness gates" section acts as a checklist. Not 5: the error-recovery feedback loop when end-to-end validation fails is only implied, not stated (no "fix the statement and re-validate" guidance); not 3: validation for these mutating/batch processors is present and explicit, so the missing-validation cap does not apply.

4 / 5

Progressive Disclosure

The body is a lean overview with a "Load only what the task needs" section that signals each of the three one-level-deep reference files (contexts, functions, quick-reference) with a one-line description, all of which exist in the bundle with their own Contents sections; it even links to a specific verified anchor ("Feature gates (verified 2026-10-25)") that is present in functions.md, and instructs reading only the relevant section. Not 4: the split is appropriate and navigation is easy with no organization gaps.

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.

The description is a model example: it states what the skill does with concrete verbs, gives an explicit and multi-faceted "Use when" clause covering all of its workflows, and uses the exact component and signal terminology an OTTL user would naturally employ. Conflict risk with other skills is minimal because the niche and triggers are highly specific.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "writing and debugging telemetry transformations", "authoring or reviewing `transform`, `filter`, `tail_sampling` processor configs or `routing` connector configs", "debugging OTTL syntax or semantics", and "converting data-processing requirements into OTTL statements" — comprehensively covering the skill's capabilities. Not 4: coverage is broad and each action is specific rather than having minor gaps.

5 / 5

Completeness

Explicitly answers both questions: the "what" is "OTTL expert for writing and debugging telemetry transformations in the OpenTelemetry Collector", and the "when" is a concrete "Use when..." clause enumerating authoring/reviewing configs, debugging syntax or semantics, transforming signals, and converting requirements into OTTL statements. Not 4: the trigger guidance is explicit and specific, not merely present.

5 / 5

Trigger Term Quality

Natural terms a user would say are comprehensively present: "OTTL" with its full expansion, "OpenTelemetry Collector", the exact component names ("transform", "filter", "tail_sampling", "routing"), and signal types ("traces, metrics, logs, or profiles"). Not 4: no commonly used phrasing for this domain is missing; these component names are precisely what affected users type.

5 / 5

Distinctiveness Conflict Risk

The OTTL niche with named Collector processors and connectors is distinct from general telemetry or unrelated data-processing skills, so wrong-skill triggering is unlikely. Not 4: the triggers (OTTL, specific processor/connector names) are unambiguous and do not meaningfully overlap with sibling skills' territory.

5 / 5

Total

20

/

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 suspicious

Warning

Total

15

/

16

Passed

Repository

ollygarden/opentelemetry-agent-skills

Path

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