otel-js

OpenTelemetry in Node.js / JavaScript / TypeScript — NodeSDK, declarative YAML configuration, auto-instrumentations, ESM vs CJS import patterns. Use when adding, reviewing, or configuring OpenTelemetry in a Node.js service. Triggers on "setup otel in node", "js telemetry", "node tracing setup", "NodeSDK", "auto instrumentation node", "TracerProvider node", or any Node.js-related OTel question.

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

85%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured pointer skill: lean, actionable via concrete fetch commands, single unambiguous action, and one-level-deep references that resolve to real files. The only weakness is inline hardcoded version pins that will go stale.

Suggestions

Move the hardcoded version pins (2.10.0, 0.221.0, 0.79.0) out of the body — either into references/declarative-setup.md or replace them with a 'resolve latest via npm view' note — so the overview does not silently go stale.

Add a one-line canonical snippet (e.g. the register() entry point) so the body is actionable for the most common task without always requiring the reference file to be loaded.

Dimension	Reasoning	Score
Conciseness	The body is a lean pointer skill with no concept over-explanation, but it embeds time-sensitive hardcoded version pins ('2.10.0', '0.221.0', '0.79.0') inline in the Sources of Truth table, which the rubric flags as a conciseness/staleness penalty; it is mostly efficient but could be tightened by deferring those pins.	2 / 3
Actionability	Provides concrete, copy-paste-ready commands — 'npm view @opentelemetry/configuration version' and specific WebFetch URLs to pinned raw GitHub paths — rather than vague direction, matching the 'fully executable code/commands' anchor.	3 / 3
Workflow Clarity	A simple single-purpose entry skill whose single action — 'Load a reference below based on the task; each reference is self-contained' — is unambiguous, so workflow clarity earns 3 under the simple-skills note; no destructive/batch steps require validation checkpoints.	3 / 3
Progressive Disclosure	Clear overview with a well-signaled references table linking one level deep to references/declarative-setup.md (verified to exist), with content appropriately split and easy navigation via the cross-references section.	3 / 3
	Total	11 / 12 Passed

Description

100%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, third-person description that names concrete capabilities, supplies natural trigger terms, and gives an explicit 'Use when' clause with a distinct Node.js-scoped niche. No fluff or over-claims.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capabilities — 'NodeSDK, declarative YAML configuration, auto-instrumentations, ESM vs CJS import patterns' — rather than vague language, matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	Explicitly answers both what (the listed capabilities) and when via 'Use when adding, reviewing, or configuring OpenTelemetry in a Node.js service', matching the 'clearly answers both what AND when' anchor; not capped at 2 because the 'Use when' clause is present.	3 / 3
Trigger Term Quality	Good coverage of natural phrases a user would say — 'setup otel in node', 'js telemetry', 'node tracing setup', 'auto instrumentation node' — plus technical terms, fitting the 'good coverage of natural terms' anchor.	3 / 3
Distinctiveness Conflict Risk	Scoped to Node.js/JS/TS OTel with Node-specific triggers (NodeSDK, TracerProvider node), giving it a clear niche unlikely to conflict with the language-agnostic sibling otel skills it cross-references.	3 / 3
	Total	12 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: ollygarden/opentelemetry-agent-skills
Path: skills/otel-js/SKILL.md
Commit: c5d2edc

Reviewed: about 3 hours ago

Table of Contents

Discovery Implementation Validation

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.