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 hits all the marks. It clearly specifies the tools involved (OpenTelemetry SDK, Kopai), lists concrete use cases, provides explicit trigger guidance with both technical terms and natural user phrases, and maintains a distinct niche that won't conflict with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple concrete actions: 'Instrument applications with OpenTelemetry SDK', 'validate telemetry using Kopai', covering setup, tracing, logging, metrics, testing, and debugging. Uses third person voice correctly. | 3 / 3 |
Completeness | Clearly answers both what (instrument with OpenTelemetry, validate with Kopai) and when (explicit 'Use when...' clause covering setup, debugging, and specific user phrases like 'my traces aren't showing up'). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'observability', 'tracing/logging/metrics', 'traces aren't showing up', 'I don't see any data', 'add observability to my app'. Includes both technical terms and natural language phrases. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with specific tool names (OpenTelemetry SDK, Kopai) and domain-specific triggers (telemetry, traces, observability). Unlikely to conflict with generic coding or logging skills. | 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 an exemplary skill file that demonstrates excellent token efficiency while maintaining high actionability. The workflow is clearly sequenced with validation checkpoints, and content is well-organized with appropriate progressive disclosure to detailed rules and references. The skill respects Claude's intelligence by jumping straight to executable commands and code.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. No unnecessary explanations of what OpenTelemetry is or how observability works. Every section delivers actionable content without padding. | 3 / 3 |
Actionability | Provides fully executable commands and code. The Quick Reference has copy-paste ready bash commands, and the Node.js example includes complete, runnable code with exact package names and file structure. | 3 / 3 |
Workflow Clarity | Clear 5-step workflow with explicit validation checkpoint (step 4) and troubleshooting guidance. Includes feedback loop: 'If empty: check endpoint/port, verify app is running, wait 10-30s and retry' followed by escalation to troubleshooting rules. | 3 / 3 |
Progressive Disclosure | Excellent structure with quick reference upfront, then workflow, then a concrete example, then organized rules by priority (CRITICAL/HIGH/MEDIUM). References are one level deep with clear navigation to rules/*.md and references/*.md files. | 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.
- Repository
- kopai-app/kopai-mono
- Commit
d5894e9
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.