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 correctly configure resource limits and memory management for a high-throughput collector. Processing 100k traces/sec requires proper memory_limiter configuration, queue strategies, and Kubernetes resource allocation.",
"type": "weighted_checklist",
"checklist": [
{
"name": "Configures memory_limiter processor",
"description": "The configuration includes memory_limiter processor with: limit_mib (80% of pod memory limit), spike_limit_mib (20% of limit), and check_interval. Score zero if memory_limiter is missing.",
"max_score": 25
},
{
"name": "Sets appropriate queue settings for backpressure",
"description": "The configuration includes queue settings: persistent queue (file_storage) for production, queue size appropriate for trace volume. Must address what happens when queue is full (drop vs backpressure).",
"max_score": 20
},
{
"name": "Specifies Kubernetes resource requests and limits",
"description": "The pod/container configuration includes requests and limits for CPU and memory. For 100k traces/sec, should estimate appropriate values (typically 2+ CPU, 4GB+ memory). Partial credit for only requests or only limits.",
"max_score": 20
},
{
"name": "Explains memory monitoring and alerting",
"description": "The response includes how to monitor memory usage (e.g., Prometheus metrics, kubectl top) and set alerts when memory usage approaches limits. Score zero if monitoring is not addressed.",
"max_score": 15
},
{
"name": "Provides scaling guidance",
"description": "The response explains when to scale horizontally (add more replicas) vs vertically (increase per-pod resources). Should mention that 100k traces/sec may require multiple replicas and a load balancer.",
"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