Expert OpenTelemetry guidance for collector configuration, pipeline design, and production telemetry instrumentation across Kubernetes, ECS, serverless, and standalone deployments. 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).
94
98%
Does it follow best practices?
Impact
94%
1.34xAverage score across 18 eval scenarios
Passed
No known issues
{
"context": "Tests whether the skill causes the agent to make appropriate deployment pattern recommendations for different scenarios. This requires understanding trade-offs between DaemonSet, Gateway, and Sidecar patterns, including resource usage, operational complexity, and scalability.",
"type": "weighted_checklist",
"checklist": [
{
"name": "Recommends Gateway pattern for high-volume centralized collection",
"description": "For 500k traces/min, the response should recommend Gateway pattern over DaemonSet because: (1) concentrates processing, (2) enables tail sampling, (3) reduces per-node overhead. Score zero if DaemonSet is recommended as primary pattern.",
"max_score": 25
},
{
"name": "Explains trade-offs between patterns",
"description": "The response discusses trade-offs: DaemonSet (low latency, high per-node cost) vs Gateway (centralized, requires load balancing) vs Sidecar (isolation, highest overhead). Must mention at least 2 trade-offs.",
"max_score": 20
},
{
"name": "Addresses multi-region deployment considerations",
"description": "The response acknowledges multi-region constraints and recommends per-region deployment patterns or cross-region forwarding with appropriate latency/cost considerations. Score zero if multi-region is not addressed.",
"max_score": 20
},
{
"name": "Provides resource estimates for 500k traces/min",
"description": "The response includes rough CPU/memory estimates for the proposed pattern at 500k traces/min scale. Partial credit for back-of-envelope calculations.",
"max_score": 15
},
{
"name": "Considers scaling and cost implications",
"description": "The response discusses how to handle dynamic scaling (HPA/scaling groups) and includes rough cost comparison between patterns. Must acknowledge that costs vary by cloud provider and usage.",
"max_score": 20
}
]
}.claude-plugin
.codex-plugin
.cursor-plugin
.github
scripts
docs
evals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
scenario-6
scenario-7
scenario-8
scenario-9
scenario-10
scenario-11
scenario-12
scenario-13
scenario-14
scenario-15
scenario-16
scenario-17
scenario-18
references