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

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

78%Weight 40%Scale 1-5

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

A well-structured entry-point skill that routes to a self-contained reference and supplies concrete fetch commands for version-sensitive facts. Its main weakness is duplication of the Sources of Truth table between the body and the reference file.

Suggestions

Trim the body's Sources of Truth table to only the most-used fetches (e.g. the three `npm view` version checks) and defer the full pinned-URL table to references/declarative-setup.md, which already contains a superset of it.

Add a one-line routing hint for non-declarative tasks (e.g. programmatic NodeSDK setup or auto-instrumentations register usage) so the entry point signals where those go, since currently only declarative-setup.md is listed.

Note the body/reference fetch-table duplication explicitly so future edits update one canonical copy, preventing the pinned versions (2.11.0 / 0.222.0) from drifting between the two locations.

Dimension	Reasoning	Score
Conciseness	The body is a lean navigation index with no concept over-explanation, but the Sources of Truth fetch table substantially duplicates the expanded table already present in references/declarative-setup.md, so a few tokens could be trimmed.	4 / 5
Actionability	Provides copy-paste-ready executable commands ("npm view @opentelemetry/configuration version" and pinned WebFetch URLs) plus a clear reference link, but the actual setup code lives in the reference rather than the body, leaving minor gaps for in-place execution.	4 / 5
Workflow Clarity	The simple routing workflow — "Load a reference below based on the task; each reference is self-contained" — is unambiguous with a use-when table, satisfying the simple-skill exception, though no explicit validation checkpoints are present.	4 / 5
Progressive Disclosure	Clear overview pointing to one verified one-level-deep reference (references/declarative-setup.md) via a well-signaled use-when table, with content appropriately split and cross-references to sibling skills for easy navigation.	5 / 5
	Total	17 / 20 Passed

Description

83%Weight 40%Scale 1-5

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 clearly states capabilities and explicit trigger conditions with natural keyword coverage. It is comprehensive on completeness and only slightly broad on the distinctiveness margin against sibling OTel skills.

Dimension	Reasoning	Score
Specificity	Names the domain plus several concrete capabilities — "NodeSDK, declarative YAML configuration, auto-instrumentations, ESM vs CJS import patterns" and the actions "adding, reviewing, or configuring" — giving good coverage with minor gaps rather than the exhaustive action list of a 5.	4 / 5
Completeness	Explicitly answers both what ("NodeSDK, declarative YAML configuration, auto-instrumentations, ESM vs CJS import patterns") and when ("Use when adding, reviewing, or configuring OpenTelemetry in a Node.js service" plus concrete trigger phrases), matching the top anchor.	5 / 5
Trigger Term Quality	Lists natural phrases a user would say — "setup otel in node", "js telemetry", "node tracing setup", "auto instrumentation node" — with good synonym coverage (otel/telemetry/tracing), though a few natural variations are absent, keeping it just below comprehensive.	4 / 5
Distinctiveness Conflict Risk	Clearly scoped to OpenTelemetry in Node.js with Node-specific triggers, but "any Node.js-related OTel question" and the shared declarative-YAML theme create minor overlap risk with sibling skills like otel-declarative-config.	4 / 5
	Total	17 / 20 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: 8e6ed41

Reviewed: 15 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.