o11y-dev/opentelemetry-skill
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
task.mdevals/scenario-18/
You are evaluating a microservices platform with the following constraints:
- 150 services deployed across 3 cloud regions
- High volume of trace data (500k traces/min)
- Needs per-service telemetry collection
- Must support dynamic service scaling
Recommend the appropriate deployment pattern (DaemonSet vs Gateway vs Sidecar) and explain the trade-offs. The recommendation should include:
- Which pattern is optimal and why
- Resource requirements for each region
- Scalability considerations
- Cost implications
.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