skill CX Codex

otel-js — Claude Code skill: OpenTelemetry for Node.js

Q: How do I install otel-js in Claude Code?

Run `npx skills add ollygarden/opentelemetry-agent-skills --skill otel-js -a claude-code`. The skill file then sits at `~/.claude/skills/otel-js/SKILL.md`.

Q: Do I need other skills next to otel-js?

It cross-references `otel-declarative-config` for the YAML schema, `otel-sdk-versions` for SDK version selection and `otel-semantic-conventions` for semantic conventions. Without the first one, config details are left to the agent's guesswork.

Walks your agent through OpenTelemetry setup in a Node.js, JavaScript or TypeScript service. Handy when you are adding tracing or wiring up NodeSDK.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓

npx skills add ollygarden/opentelemetry-agent-skills --skill otel-js -a claude-code

Open on GitHub

What otel-js does

The skill gives an agent a starting point for OpenTelemetry work in Node.js services. It ships one reference file, references/declarative-setup.md, covering SDK setup through declarative YAML: the OTEL_CONFIG_FILE variable, the @opentelemetry/configuration and @opentelemetry/sdk-node packages, import order under ESM and CJS, and the move to 2.0. Each reference stands on its own, so the agent pulls in only what the task needs.

A second section lists where the agent should look things up. Package versions come from npm view for @opentelemetry/configuration, @opentelemetry/sdk-node and @opentelemetry/auto-instrumentations-node. Release status, breaking changes, ESM and CJS preload behaviour, the auto-instrumentation entry point and the 2.x to 3.x migration guide are fetched from files in the opentelemetry-js repository by direct URL.

The skill points at three neighbours: otel-declarative-config for the YAML schema, otel-sdk-versions for picking an SDK version, otel-semantic-conventions for semantic conventions. Install it alongside them, or the agent will guess at part of the answer. Schema details live in the first of those, so without it you are back to reading the upstream docs yourself.

What it helps with

wire NodeSDK into a Node.js service
move OTel config to declarative YAML
sort out import order for ESM and CJS
pick versions of @opentelemetry/sdk-node and auto-instrumentations
migrate from 2.x to 3.x

Example prompts for the agent

Set up OpenTelemetry in this Node.js service with NodeSDK
Convert the OTel config to declarative YAML using OTEL_CONFIG_FILE
Check the OTel import order for ESM in this project

How to install otel-js

1Skills CLI (Vercel)

npx skills add ollygarden/opentelemetry-agent-skills --skill otel-js -a claude-code

2Manually: put the files in place

~/.claude/skills/otel-js/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/otel-js/

1Skills CLI (Vercel)

npx skills add ollygarden/opentelemetry-agent-skills --skill otel-js -a codex

2Manually: put the files in place

.agents/skills/otel-js/SKILL.md

For all projects use ~/.agents/skills/

1Skills CLI (Vercel)

npx skills add ollygarden/opentelemetry-agent-skills --skill otel-js -a cursor

2Manually: put the files in place

.cursor/skills/otel-js/SKILL.md

Cursor also reads .agents/skills/ and .claude/skills/

1GitHub CLI

gh skill install ollygarden/opentelemetry-agent-skills otel-js

2Manually: put the files in place

.github/skills/otel-js/SKILL.md

1Skills CLI (Vercel)

npx skills add ollygarden/opentelemetry-agent-skills --skill otel-js -a gemini-cli

2Platform CLI

gemini skills install https://github.com/ollygarden/opentelemetry-agent-skills --path skills/otel-js

Manually: put the files in place

.devin/skills/otel-js/SKILL.md

The legacy .windsurf/skills/ path still works

Skills CLI (Vercel)

npx skills add ollygarden/opentelemetry-agent-skills --skill otel-js -a opencode

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about otel-js

How do I install otel-js in Claude Code?

Run npx skills add ollygarden/opentelemetry-agent-skills --skill otel-js -a claude-code. The skill file then sits at ~/.claude/skills/otel-js/SKILL.md.

What does otel-js do?

It hands the agent a reference on OpenTelemetry in Node.js: SDK setup via declarative YAML, auto-instrumentations, and the ESM versus CJS import differences. The agent loads it when you add or review tracing in a service.

Do I need other skills next to otel-js?

It cross-references otel-declarative-config for the YAML schema, otel-sdk-versions for SDK version selection and otel-semantic-conventions for semantic conventions. Without the first one, config details are left to the agent's guesswork.

Source text

SKILL.md · Apache-2.0

---
name: otel-js
description: 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.
---

# OpenTelemetry in Node.js

Entry point for OpenTelemetry mechanics in Node.js / JavaScript / TypeScript services.
Load a reference below based on the task; each reference is self-contained.

## References

| File | Use when |
|---|---|
| [`references/declarative-setup.md`](references/declarative-setup.md) | Configuring the SDK via declarative YAML: `OTEL_CONFIG_FILE`, `@opentelemetry/configuration`, `@opentelemetry/sdk-node`, ESM/CJS import order, v2.0 migration. |

## Sources of Truth

For YAML schema details, fetch the upstream sources listed in the `otel-declarative-config` skill.
For Node.js-specific facts:

| Fact | Fetch |
|---|---|
| Latest `@opentelemetry/configuration` | `npm view @opentelemetry/configuration version` |
| Latest `@opentelemetry/sdk-node` | `npm view @opentelemetry/sdk-node version` |
| Latest `@opentelemetry/auto-instrumentations-node` | `npm view @opentelemetry/auto-instrumentations-node version` |
| Released package status / breaking changes (`3.0.0` / `0.300.0`, verified 2026-10-21) | `WebFetch https://raw.githubusercontent.com/open-telemetry/opentelemetry-js/v3.0.0/experimental/packages/configuration/README.md` and `WebFetch https://raw.githubusercontent.com/open-telemetry/opentelemetry-js/v3.0.0/experimental/packages/opentelemetry-sdk-node/README.md` |
| Experimental CHANGELOG through `0.300.0` | `WebFetch https://raw.githubusercontent.com/open-telemetry/opentelemetry-js/v3.0.0/experimental/CHANGELOG.md` |
| ESM / CJS preload mechanics at `3.0.0` | `WebFetch https://raw.githubusercontent.com/open-telemetry/opentelemetry-js/v3.0.0/doc/esm-support.md` |
| Auto-instrumentations register entry point at `0.80.0` | `WebFetch https://raw.githubusercontent.com/open-telemetry/opentelemetry-js-contrib/auto-instrumentations-node-v0.80.0/packages/auto-instrumentations-node/README.md` |
| 2.x → 3.x migration (removed packages, Node.js floor) | `WebFetch https://raw.githubusercontent.com/open-telemetry/opentelemetry-js/v3.0.0/doc/3.x/migration-guide.md` |
| Node.js getting-started docs | `WebFetch https://opentelemetry.io/docs/languages/js/getting-started/nodejs/` |

## Cross-References

- Schema-level facts: `otel-declarative-config` skill (language-agnostic YAML schema sources).
- SDK version selection across languages: `otel-sdk-versions` skill.
- Semantic conventions lookup: `otel-semantic-conventions` skill.

Similar skills

All skills for Backend and APIs →

mcp-builder official anthropics This skill walks through building an MCP server in TypeScript or Python, from reading the protocol spec to writing tests and evaluation questions. 130,949installs claude-api official anthropics Reference skill for the Claude API and Anthropic SDK that enforces valid model IDs, adaptive thinking, and streaming. 74,198installs lark-im larksuite This skill lets an agent work with Lark IM messages, chats, files, and interactive cards. Use it when coding tasks need access to team conversations. CX Codex +1 472,900installs lark-event larksuite Listens to Lark/Feishu events and streams them as NDJSON. Use it for bots, message processing, and long-running subscribers. CX Codex +1 466,800installs caveman-discover JuliusBrussee Finds and labels every LLM workflow in your repository so Caveman Cloud breaks down spend by actual job rather than grouping everything into one bucket. CX Codex +1 104,400installs migration JuliusBrussee Enforces reversible, compatibility-safe transitions for schema, data, and API updates. Useful whenever data loss or rollout downtime is unacceptable. CX Codex +1 103,900installs

From the same set7

otel-component-telemetry Scans one OpenTelemetry component at pinned versions and records the spans, metrics and logs it emits as change-point files. CX Codex +1 ★ 116repo stars otel-telemetrygen Builds version-pinned telemetrygen commands for synthetic OTLP traces, metrics and logs aimed at a collector. CX Codex +1 ★ 116repo stars otel-semantic-conventions A skill that looks up released OpenTelemetry semantic conventions: group names, attributes and span naming rules. Useful when the agent would otherwise invent keys. CX Codex +1 ★ 116repo stars otel-python A skill that helps your agent set up and debug OpenTelemetry in Python services: SDK config, declarative YAML, zero-code instrumentation. CX Codex +1 ★ 116repo stars otel-dotnet A skill for OpenTelemetry in .NET and ASP.NET Core: SDK setup through DI, instrumentation, the zero-code agent, and breaking-change audits. CX Codex +1 ★ 116repo stars otel-collector-builder A skill for building custom OpenTelemetry Collector distributions with OCB. Use it when the stock otelcol and otelcol-contrib binaries do not fit. CX Codex +1 ★ 116repo stars