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.

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

92%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.

An exemplary entry-point skill: a lean index that routes to a single self-contained reference and pins authoritative upstream sources with executable fetch commands. The only flaw is embedded time-sensitive version/date pins in the Sources of Truth table, which will age and slightly bloat the body.

DimensionReasoningScore

Conciseness

The body is a lean routing index with no concept explanations, but the Sources of Truth table embeds time-sensitive version and date pins ("3.0.0 / 0.300.0, verified 2026-10-25", "0.82.0") outside any deprecated/old-patterns section, which the guidelines penalize — anchor 4, not 5.

4 / 5

Actionability

Fully executable, copy-paste-ready commands cover the fact-checking cases ("npm view @opentelemetry/configuration version", exact WebFetch URLs pinned to tagged releases) alongside an unambiguous use-when table for the setup task — anchor 5 for an instruction/navigation skill.

5 / 5

Workflow Clarity

A simple single-purpose skill under 50 lines whose one action is unambiguous ("Load a reference below based on the task; each reference is self-contained") with an explicit fact-to-fetch mapping; the simple-skill exception applies, and there are no destructive or batch operations requiring validation.

5 / 5

Progressive Disclosure

Clear overview with one verified, well-signaled one-level-deep reference (references/declarative-setup.md, confirmed to exist and to contain no nested bundle references), an appropriate index-vs-detail split, and explicit cross-references — anchor 5.

5 / 5

Total

19

/

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 that clearly states a specific niche, explicit capabilities, and a well-formed 'Use when' clause with natural trigger phrases. It is fully complete and highly actionable as a trigger description, with only minor gaps in action-verb framing and synonym coverage.

Suggestions

Lead with concrete verbs for each capability (e.g., "Set up NodeSDK via declarative YAML", "Instrument HTTP/Express/gRPC automatically", "Resolve ESM vs CJS preload order") rather than a comma-separated topic inventory.

Add natural trigger variants users would say, such as "opentelemetry javascript", "instrument node app", or "typescript tracing", to round out keyword coverage.

DimensionReasoningScore

Specificity

Enumerates concrete sub-capabilities ("NodeSDK, declarative YAML configuration, auto-instrumentations, ESM vs CJS import patterns") with action verbs ("adding, reviewing, or configuring"), but reads more as a topic inventory than a list of concrete actions, matching anchor 4 rather than the comprehensive action coverage of anchor 5.

4 / 5

Completeness

Explicitly answers both what (the enumerated NodeSDK/YAML/auto-instrumentation/ESM-CJS capabilities) and when ("Use when adding, reviewing, or configuring OpenTelemetry in a Node.js service") with concrete trigger phrases, exactly matching anchor 5.

5 / 5

Trigger Term Quality

Includes natural phrases users would say ("setup otel in node", "node tracing setup", "auto instrumentation node") plus the broad catch-all "any Node.js-related OTel question", but misses common variations like "opentelemetry javascript" or "instrument node app", placing it at anchor 4.

4 / 5

Distinctiveness Conflict Risk

Clearly niched to Node.js with Node-specific triggers and explicit scoping ("in a Node.js service"), but the "declarative YAML configuration" capability overlaps a language-agnostic YAML-schema skill, giving minor overlap risk consistent with anchor 4 rather than the minimal-conflict anchor 5.

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.