Expert OpenTelemetry guidance for collector configuration, pipeline design, and production telemetry instrumentation. Use when configuring collectors, designing pipelines, instrumenting applications, implementing sampling, managing cardinality, securing telemetry, writing OTTL transformations, or setting up AI coding agent observability (Claude Code, Codex, Gemini CLI, GitHub Copilot).
93
97%
Does it follow best practices?
Impact
85%
7.08xAverage score across 4 eval scenarios
Passed
No known issues
{
"context": "Tests whether the skill causes the agent to provide Claude Code-specific telemetry configuration rather than generic OpenTelemetry setup. Without the skill, agents provide generic OTEL configuration that omits the required enablement flag, correct metric temporality, and privacy controls. The skill should enforce Claude Code-specific knowledge including environment variables, settings file location, and cardinality warnings.",
"type": "weighted_checklist",
"checklist": [
{
"name": "Specifies CLAUDE_CODE_ENABLE_TELEMETRY=1 environment variable",
"description": "The response includes the CLAUDE_CODE_ENABLE_TELEMETRY=1 environment variable as a required step to enable telemetry. Without this flag, no telemetry is emitted regardless of OTEL configuration. Responses that provide OTEL configuration without this flag score zero on this criterion.",
"max_score": 30
},
{
"name": "Mentions OTEL_EXPORTER_OTLP_METRICS_TEMPORALITY_PREFERENCE=cumulative",
"description": "The response specifies the correct metric temporality preference for Claude Code metrics. Using delta temporality or omitting this setting results in incorrect metric aggregation for the cumulative counters Claude Code emits.",
"max_score": 20
},
{
"name": "References ~/.claude/settings.json for persistent configuration",
"description": "The response mentions that environment variables can be persisted in ~/.claude/settings.json under an env block for consistent telemetry across sessions. Responses that only show environment variable exports without mentioning persistent config score zero on this criterion.",
"max_score": 15
},
{
"name": "Includes privacy controls for prompt and tool logging",
"description": "The response mentions OTEL_LOG_USER_PROMPTS and/or OTEL_LOG_TOOL_DETAILS privacy controls, explaining that prompt content is not logged by default and these flags must be explicitly enabled. Omitting privacy configuration entirely scores zero — this is a key safety concern for the skill.",
"max_score": 20
},
{
"name": "Warns about session.id cardinality in metrics",
"description": "The response warns that session.id should not be used as a metric dimension/label due to high cardinality, and recommends using it only in logs/events or for correlation via prompt.id. Missing this warning entirely scores zero — it is a specific Claude Code observability pitfall the skill addresses.",
"max_score": 15
}
]
}docs
evals
cardinality-protection
claude-code-telemetry
collector-memory-limiter
scenario-1
scenario-2
scenario-3
scenario-4
tail-sampling-setup
references