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".
100
100%
Does it follow best practices?
Impact
Pending
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 and Kopai validation), provides comprehensive trigger terms covering both technical keywords and natural user phrases, and explicitly states when to use the skill. The inclusion of example user utterances like 'my traces aren't showing up' is particularly effective for skill selection.
| 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 with Kopai) and 'when' with an explicit 'Use when...' clause covering multiple trigger scenarios including debugging scenarios and example user phrases. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'observability', 'tracing', 'logging', 'metrics', 'traces', 'logs', 'instrumentation', 'OpenTelemetry', plus natural-language phrases like 'my traces aren't showing up', 'I don't see any data', 'how do I add observability to my app'. | 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 exemplifies good practices: it's concise, immediately actionable with executable code, has a clear workflow with validation and troubleshooting feedback loops, and uses progressive disclosure effectively by keeping the overview lean while pointing to detailed rule files. The categorization of rules by priority and the inclusion of a complete Node.js example provide excellent balance between brevity and usefulness.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. No unnecessary explanations of what OpenTelemetry is or how tracing works. Every section serves a purpose and assumes Claude's competence with the underlying concepts. | 3 / 3 |
Actionability | Provides fully executable commands (npx, npm install, node --import), a complete copy-paste ready Node.js instrumentation example, and specific environment variable configurations. The quick reference section alone is immediately actionable. | 3 / 3 |
Workflow Clarity | The 5-step workflow is clearly sequenced with an explicit validation step (step 4) that includes a feedback loop: 'If empty: check endpoint/port, verify app is running and generating traffic, wait 10-30s and retry.' Step 5 escalates to troubleshooting rules, providing clear error recovery paths. | 3 / 3 |
Progressive Disclosure | Excellent structure with a concise overview, quick reference, and one complete example inline, then clearly organized one-level-deep references to rules/<rule-name>.md files and references/ directory. The categorization by priority (CRITICAL/HIGH/MEDIUM) aids navigation. | 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