kopai/otel-instrumentation
Instrument applications with OpenTelemetry SDK and validate telemetry using Kopai. Use when setting up observability, adding tracing/logging/metrics, testing instrumentation, debugging missing telemetry data, or when traces/logs/metrics aren't appearing after setup. Also use when users say things like "my traces aren't showing up", "I don't see any data", or "how do I add observability to my app".
80
100%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that clearly communicates specific capabilities (OpenTelemetry instrumentation, Kopai validation), provides explicit trigger guidance with a 'Use when...' clause, and includes natural language examples of user requests. It uses proper third-person voice and covers both the technical domain and common user pain points like missing telemetry data.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple concrete actions: 'Instrument applications with OpenTelemetry SDK', 'validate telemetry using Kopai', 'adding tracing/logging/metrics', 'testing instrumentation', 'debugging missing telemetry data'. These are specific, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (instrument with OpenTelemetry SDK, validate telemetry with Kopai) and 'when' with an explicit 'Use when...' clause covering multiple trigger scenarios, plus natural language examples of user requests. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'observability', 'tracing', 'logging', 'metrics', 'traces', 'logs', 'my traces aren't showing up', 'I don't see any data', 'add observability to my app', 'OpenTelemetry', 'instrumentation'. Includes both technical terms and natural language phrases. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with specific tool names (OpenTelemetry SDK, Kopai) and a clear niche in observability/telemetry instrumentation. Unlikely to conflict with general coding or monitoring skills due to the specific tooling and domain focus. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted skill that efficiently covers the full instrumentation workflow from setup through validation and troubleshooting. It provides immediate actionable content (quick reference, complete Node.js example) while organizing detailed language-specific and troubleshooting guidance into clearly referenced rule files. The progressive disclosure is particularly strong, with priority-labeled categories guiding Claude to the right depth of information.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. No unnecessary explanations of what OpenTelemetry is or how observability works. Every section serves a clear purpose, and the quick reference block is immediately useful. | 3 / 3 |
Actionability | Provides fully executable commands (npx, npm install, node --import), a complete Node.js instrumentation example with copy-paste ready code, and specific CLI commands for validation. The env vars and file contents are concrete and specific. | 3 / 3 |
Workflow Clarity | The 5-step workflow is clearly sequenced with explicit validation at step 4, includes a feedback loop (if empty: check endpoint/port, wait and retry), and escalation to troubleshooting rules in step 5. This covers the validate -> fix -> retry pattern well. | 3 / 3 |
Progressive Disclosure | Excellent structure: quick reference at top, concise workflow overview, one concrete example, then organized rule references by priority (CRITICAL/HIGH/MEDIUM) pointing to one-level-deep rule files. References section cleanly links to CLI reference, docs, and examples. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
Reviewed
Table of Contents