liteverge-opentelemetry-browser
Add OpenTelemetry tracing to a browser/frontend app with Liteverge. Use when the user asks to add observability, tracing, or OpenTelemetry to a React, Next.js, Vue, Angular, or similar frontend app — or to add custom spans and instrumentation to an already-instrumented app.
94
92%
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 follows best practices. It clearly states what the skill does (add OpenTelemetry tracing with Liteverge), provides explicit 'Use when' guidance with multiple natural trigger terms, and is distinctive enough to avoid conflicts with related skills. The description uses proper third-person voice and covers both new instrumentation and extending existing instrumentation.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists specific concrete actions: 'Add OpenTelemetry tracing', 'add custom spans and instrumentation'. Also specifies the context (browser/frontend app with Liteverge) and mentions specific frameworks. | 3 / 3 |
Completeness | Clearly answers both what ('Add OpenTelemetry tracing to a browser/frontend app with Liteverge') and when ('Use when the user asks to add observability, tracing, or OpenTelemetry to a React, Next.js, Vue, Angular, or similar frontend app'). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'observability', 'tracing', 'OpenTelemetry', 'React', 'Next.js', 'Vue', 'Angular', 'frontend app', 'custom spans', 'instrumentation'. These are terms developers naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear niche: specifically targets frontend/browser OpenTelemetry with Liteverge. The combination of 'Liteverge', 'frontend', and 'OpenTelemetry' creates a unique trigger profile unlikely to conflict with backend tracing or other observability skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%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-structured routing skill that efficiently directs Claude to the appropriate detailed instructions based on user intent. The decision logic is clear and the progressive disclosure is excellent. The main limitation is that actionability depends on the referenced files rather than being self-contained, though this is appropriate for a routing/overview skill.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, providing only decision logic and navigation without explaining what OpenTelemetry is or how tracing works. Every section serves a clear purpose. | 3 / 3 |
Actionability | The skill provides clear decision criteria and references to detailed files, but contains no executable code itself. The actionability depends entirely on the referenced files (init.md, instrument.md). | 2 / 3 |
Workflow Clarity | The decision workflow is crystal clear with explicit criteria for choosing between two paths, including a concrete check (look for @opentelemetry/api in package.json) when uncertain. | 3 / 3 |
Progressive Disclosure | Excellent structure with a clear overview, well-signaled one-level-deep references to init.md and instrument.md, and appropriate separation of concerns. Navigation is intuitive. | 3 / 3 |
Total | 11 / 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
- liteverge/liteverge-opentelemetry
- Commit
3e0a0be
- 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.