liteverge-opentelemetry-lambda
Add OpenTelemetry observability (traces, metrics) to an AWS Lambda function with Liteverge. Use when the user asks to add tracing, observability, or metrics to a Lambda function — or to add custom spans and metrics to an already-instrumented Lambda. Logs are not included; use CloudWatch for logging.
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 clearly defines its scope (OpenTelemetry observability for Lambda via Liteverge), provides explicit trigger conditions, and helpfully clarifies what it doesn't cover (logs). The description uses proper third-person voice and includes natural keywords users would actually use when requesting this functionality.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Add OpenTelemetry observability (traces, metrics)', 'add custom spans and metrics', and clarifies scope with 'Logs are not included; use CloudWatch for logging'. | 3 / 3 |
Completeness | Clearly answers both what ('Add OpenTelemetry observability to AWS Lambda with Liteverge') and when ('Use when the user asks to add tracing, observability, or metrics to a Lambda function') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'tracing', 'observability', 'metrics', 'Lambda function', 'custom spans', plus the specific tool name 'Liteverge' and 'OpenTelemetry'. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with specific technology stack (OpenTelemetry + AWS Lambda + Liteverge) and clear scope boundaries (excludes logs). Unlikely to conflict with generic observability or Lambda 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 documentation. It excels at progressive disclosure and conciseness, serving as a clean entry point. The only limitation is that actionability depends entirely on the referenced files—this file itself contains no executable guidance.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, providing only decision logic and navigation without explaining what OpenTelemetry is or how Lambda works. Every line serves a purpose. | 3 / 3 |
Actionability | The skill provides clear decision criteria and file references, but no executable code or concrete commands are present in this file itself—all actionable content is delegated to referenced files. | 2 / 3 |
Workflow Clarity | For a routing/decision skill, the workflow is crystal clear: two distinct paths with explicit decision criteria and a fallback check (package.json inspection) when uncertain. | 3 / 3 |
Progressive Disclosure | Excellent structure with a concise overview and one-level-deep references to init.md and instrument.md. Clear signaling of when to use each file with well-organized navigation. | 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.