CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

69

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

85%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: it routes cleanly to a single self-contained reference and defines a concrete verification protocol for version-sensitive facts via executable commands. The main improvement opportunity is removing the duplication between the body's Sources of Truth table and the equivalent table inside the reference file.

Suggestions

De-duplicate the Sources of Truth table: several rows (npm view commands, pinned WebFetch URLs) appear in both SKILL.md and references/declarative-setup.md — keep only the cross-skill pointers and the reference link in the body and let the reference carry the fetch commands.

Move the version-pinned status row ("3.0.0 / 0.300.0, verified 2026-10-21") into a dedicated version-status or migration section so the entry-point table stays time-stable.

Add one minimal inline activation snippet (e.g., the OTEL_CONFIG_FILE + node --import line) so the body is self-sufficient for the most common case without opening the reference.

DimensionReasoningScore

Conciseness

The body is a lean router with no concept padding, but the Sources of Truth table duplicates several rows (npm view commands, pinned WebFetch URLs) already present in references/declarative-setup.md, and version pins with dates ("3.0.0 / 0.300.0, verified 2026-10-21") sit in the main table rather than a version-status or deprecated section. Minor trimming would reach anchor 5.

4 / 5

Actionability

Routing is explicit ("Load a reference below based on the task; each reference is self-contained") and the fetch commands are copy-paste ready ("npm view @opentelemetry/sdk-node version", exact WebFetch URLs). Not anchor 5 because the entry body itself contains no setup code or worked example — it delegates everything to the single reference.

4 / 5

Workflow Clarity

This is a single-purpose router under 50 lines whose single action — match the task to references/declarative-setup.md, then verify version-sensitive facts via the listed Sources of Truth commands — is unambiguous, so the simple-skill exception applies. The Sources of Truth table additionally functions as an explicit verify-before-claiming checkpoint for version-sensitive facts, and no destructive or batch operations are involved.

5 / 5

Progressive Disclosure

The body is a clear overview with a well-signaled, one-level-deep reference table ("File | Use when") pointing to the verified references/declarative-setup.md, which exists and is self-contained. Cross-references to sibling skills are by skill name, not nested file chains, so navigation matches the anchor-5 example.

5 / 5

Total

18

/

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 description: it names the domain and concrete capability areas, answers both what and when explicitly, and lists natural trigger phrases. The only weaknesses are a topic-list style rather than action verbs and a broad catch-all trigger that slightly raises conflict risk with sibling OTel skills.

DimensionReasoningScore

Specificity

"NodeSDK, declarative YAML configuration, auto-instrumentations, ESM vs CJS import patterns" plus "adding, reviewing, or configuring" names several concrete capabilities with only minor coverage gaps. It sits above anchor 3 (1-2 concrete actions) because it enumerates four distinct capability areas, but below anchor 5 because it lists topics/components more than executable actions.

4 / 5

Completeness

"OpenTelemetry in Node.js / JavaScript / TypeScript — NodeSDK, declarative YAML configuration, auto-instrumentations, ESM vs CJS import patterns" answers what, and "Use when adding, reviewing, or configuring OpenTelemetry in a Node.js service. Triggers on ..." answers when with concrete trigger phrases. This matches the anchor-5 example structure exactly; anchor 4 would require a weaker or less explicit 'when'.

5 / 5

Trigger Term Quality

"setup otel in node", "js telemetry", "node tracing setup", "NodeSDK", "auto instrumentation node", "TracerProvider node" are phrases a user would naturally say. Not anchor 5: common variations like "opentelemetry javascript", "instrument node app", or "typescript tracing" are missing.

4 / 5

Distinctiveness Conflict Risk

The Node.js-specific niche and triggers (NodeSDK, node tracing setup) are clearly distinct from other skills. Not anchor 5: the catch-all "or any Node.js-related OTel question" could capture Node-flavored YAML-schema or cross-language version questions that belong to sibling otel-* skills, creating minor overlap risk with closely related skills.

4 / 5

Total

17

/

20

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

ollygarden/opentelemetry-agent-skills

Path

skills/otel-js/SKILL.md

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.