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 design multi-cloud OpenTelemetry Collector deployments. This is complex because each cloud provider has different authentication, networking, and compliance requirements.",
"type": "weighted_checklist",
"checklist": [
{
"name": "Uses cloud-agnostic OpenTelemetry components",
"description": "The response recommends standard OpenTelemetry receivers and processors that work across clouds (OTLP, prometheus, etc.) rather than cloud-specific collectors. Score zero if solution is cloud-vendor-specific.",
"max_score": 20
},
{
"name": "Addresses cloud-specific authentication (IAM, Service Accounts)",
"description": "The response configures authentication for each cloud: AWS IAM roles, GCP Service Accounts, Azure Managed Identities. Must address how credentials are passed to collectors without hardcoding secrets.",
"max_score": 25
},
{
"name": "Implements per-region or per-cloud aggregation",
"description": "The architecture includes aggregation strategy: either per-region gateways or centralized collector tiers that aggregate from all clouds. Must explain trade-offs of each approach.",
"max_score": 20
},
{
"name": "Handles networking constraints (VPCs, Security Groups)",
"description": "The response addresses cloud-specific networking: AWS security groups, GCP firewall rules, Azure NSGs. Must explain how collectors in different clouds can reach central backend.",
"max_score": 15
},
{
"name": "Considers compliance and data residency",
"description": "The response mentions data residency requirements (e.g., EU data must stay in EU) and how collector placement addresses compliance. Partial credit if mentioned, full credit if configured.",
"max_score": 15
},
{
"name": "Provides cost and operational considerations",
"description": "The response acknowledges different costs and operational complexity across clouds. Optional but recommended.",
"max_score": 5
}
]
}.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