OpenTelemetry Transformation Language (OTTL) expert. Use when writing or debugging OTTL expressions for any OpenTelemetry Collector component that supports OTTL (processors, connectors, receivers, exporters). Triggers on tasks involving telemetry transformation, filtering, attribute manipulation, data redaction, sampling policies, routing, or Collector configuration. Covers syntax, contexts, functions, error handling, and performance.
98
100%
Does it follow best practices?
Impact
92%
1.10xAverage score across 3 eval scenarios
Passed
No known issues
PII redaction pipeline ordering and nil guards
nil guard on redacted attrs
100%
100%
nil keyword not null
100%
100%
error_mode set explicitly
100%
100%
error_mode ignore in production
100%
100%
SHA256 hash for emails/IDs
0%
100%
replace_pattern for partial masking
100%
100%
filter processor for full drops
100%
100%
redaction after enrichment
100%
100%
delete_key for never-export attrs
50%
0%
set REDACTED for auth headers
0%
100%
debug exporter for validation
100%
100%
High-cardinality URL normalization and attribute limits
UUID pattern normalization
100%
100%
Numeric ID normalization
100%
100%
nil guard on url.path
0%
100%
nil guard on http.route
0%
100%
limit() for attribute count
100%
100%
truncate_all() for value length
100%
100%
resource processor for static attrs
100%
100%
transform to copy resource to span
100%
100%
error_mode set explicitly
100%
100%
error_mode ignore production
100%
100%
nil keyword not null
100%
100%
Stale data filtering, timestamp backfill, and enum constants
UnixNano(Now()) for stale drop
83%
100%
Stale drop uses filter processor
100%
100%
Timestamp backfill observed_time
90%
100%
Timestamp backfill log.time
90%
100%
Enum constant STATUS_CODE_ERROR
100%
100%
IsMatch() for pattern filtering
100%
100%
filter processor for metric drops
100%
100%
nil for absence checks
75%
0%
error_mode set explicitly
100%
100%
error_mode ignore in production
100%
100%
where clause nil guards on attrs
16%
0%
e73252a
Table of Contents
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.