Install the "sentry-node-sdk" agent skill from https://github.com/getsentry/sentry-for-ai/tree/main/skills-legacy/sentry-node-sdk into .claude/skills/sentry-node-sdk/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sentry-node-sdk", then confirm the skill loads.
Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
skills CLI
$ npx skills add getsentry/sentry-for-ai --skill sentry-node-sdk -a codex
Project install goes to .agents/skills/; add -g for ~/.codex/skills/.
Install the "sentry-node-sdk" agent skill from https://github.com/getsentry/sentry-for-ai/tree/main/skills-legacy/sentry-node-sdk into .agents/skills/sentry-node-sdk/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sentry-node-sdk", then confirm the skill loads.
Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
skills CLI
$ npx skills add getsentry/sentry-for-ai --skill sentry-node-sdk -a cursor
Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.
Install the "sentry-node-sdk" agent skill from https://github.com/getsentry/sentry-for-ai/tree/main/skills-legacy/sentry-node-sdk into .cursor/skills/sentry-node-sdk/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sentry-node-sdk", then confirm the skill loads.
Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
skills CLI
$ npx skills add getsentry/sentry-for-ai --skill sentry-node-sdk -a gemini-cli
Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.
Install the "sentry-node-sdk" agent skill from https://github.com/getsentry/sentry-for-ai/tree/main/skills-legacy/sentry-node-sdk into .gemini/skills/sentry-node-sdk/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sentry-node-sdk", then confirm the skill loads.
Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
skills CLI
$ npx skills add getsentry/sentry-for-ai --skill sentry-node-sdk -a github-copilot
Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.
Install the "sentry-node-sdk" agent skill from https://github.com/getsentry/sentry-for-ai/tree/main/skills-legacy/sentry-node-sdk into .github/skills/sentry-node-sdk/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sentry-node-sdk", then confirm the skill loads.
GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
skills CLI
$ npx skills add getsentry/sentry-for-ai --skill sentry-node-sdk -a opencode
OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
Install the "sentry-node-sdk" agent skill from https://github.com/getsentry/sentry-for-ai/tree/main/skills-legacy/sentry-node-sdk into .opencode/skills/sentry-node-sdk/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sentry-node-sdk", then confirm the skill loads.
OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
Skill name
sentry-node-sdk
GitHub stars
268
Token cost
~8.4k tokens
SKILL.md length
2,331 words
Files
8 (incl. references)
Skills in repo
32
Repo updated
First seen
Licence
Apache-2.0
At a glance
Full Sentry SDK setup for Node.js, Bun, and Deno. An agent skill from getsentry/sentry-for-ai.
Works in 4 steps: Detect → Recommend → Guide → …
Asked to add Sentry to Node.js
SKILL.md covers Invoke This Skill When, Phase 1: Detect, Phase 2: Recommend and Phase 3: Guide, plus 4 more sections
Calls bun, node and npm; reaches docs.sentry.io; needs SENTRY_AUTH_TOKEN
What it does
Sentry Node SDK is an agent skill from getsentry/sentry-for-ai, published by the product's own GitHub organization. Full Sentry SDK setup for Node.js, Bun, and Deno. Use when asked to "add Sentry to Node.js", "add Sentry to Bun", "add Sentry to Deno", "install @sentry/node", "@sentry/bun", or "@sentry/deno", or configure error monitoring, tracing, logging, profiling, metrics, crons, or AI monitoring for server-side JavaScript/TypeScript runtimes.
Its SKILL.md is about 8.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 8 other files, including reference files (for example `references/ai-monitoring.md`, `references/crons.md` and `references/error-monitoring.md`).
It sits in Backend & APIs, covering Scheduled and recurring tasks and Backend development. It works with Sentry, Deno, Node.js and JavaScript. The repository describes itself as: Teach your AI coding assistant how to use Sentry - setup, debugging, alerts, and more. The licence is Apache-2.0.
When your agent uses it
Asked to add Sentry to Node.js
Add Sentry to Bun
Add Sentry to Deno
Install @sentry/node
Example prompts
“add Sentry to Node.js”
“add Sentry to Bun”
“add Sentry to Deno”
“/sentry-node-sdk”
Requirements
Node.js
Workflow steps
4 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit d8fd106. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
bun
node
npm
deno
yarn
pnpm
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
docs.sentry.io
Also links to:
sentry.io
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
SENTRY_AUTH_TOKEN
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Sentry Node SDK loads about 8.4k tokens when it runs, and up to ~36k if it reads all its reference files. Until then it costs about 88 tokens; SKILL.md has 2,331 words of instructions outside code blocks.
Always· name and description, kept in context so the agent knows when to use it
~88
When it runs· the whole SKILL.md, loaded when a task matches
~8.4k
With references· SKILL.md plus every file in references/, read only if the agent opens them
~36k
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
Download SKILL.mdSave it as .claude/skills/sentry-node-sdk/SKILL.md (or your agent's skills folder). This skill also uses 7 other files; get the full folder from GitHub.
name
sentry-node-sdk
description
Full Sentry SDK setup for Node.js, Bun, and Deno. Use when asked to "add Sentry to Node.js", "add Sentry to Bun", "add Sentry to Deno", "install @sentry/node", "@sentry/bun", or "@sentry/deno", or configure error monitoring, tracing, logging, profiling, metrics, crons, or AI monitoring for server-side JavaScript/TypeScript runtimes.
Opinionated wizard that scans your project and guides you through complete Sentry setup for server-side JavaScript and TypeScript runtimes: Node.js, Bun, and Deno.
Invoke This Skill When
User asks to "add Sentry to Node.js", "Bun", or "Deno"
User wants to install or configure @sentry/node, @sentry/bun, or @sentry/deno
User wants error monitoring, tracing, logging, profiling, crons, metrics, or AI monitoring for a backend JS/TS app
User asks about instrument.js, --import ./instrument.mjs, bun --preload, or npm:@sentry/deno
User wants to monitor Express, Fastify, Koa, Hapi, Connect, Bun.serve(), or Deno.serve()
NestJS? Use sentry-nestjs-sdk instead — it uses @sentry/nestjs with NestJS-native decorators and filters.
Next.js? Use sentry-nextjs-sdk instead — it handles the three-runtime architecture (browser, server, edge).
Note: SDK versions below reflect current Sentry docs at time of writing (@sentry/node ≥10.42.0, @sentry/bun ≥10.42.0, @sentry/deno ≥10.42.0).
Always verify against docs.sentry.io/platforms/javascript/guides/node/ before implementing.
Phase 1: Detect
Run these commands to identify the runtime, framework, and existing Sentry setup:
Present a concrete recommendation based on what you found. Don't ask open-ended questions — lead with a proposal:
Route from OTel detection:
OTel tracing detected (@opentelemetry/sdk-node or @opentelemetry/sdk-trace-node in package.json, or NodeTracerProvider in source) → use OTLP path: otlpIntegration() via @sentry/node-core/light; do not set tracesSampleRate; Sentry links errors to OTel traces automatically
⚡ Runtime Metrics — automatic collection of memory, CPU, and event loop metrics; nodeRuntimeMetricsIntegration() (Node.js) / bunRuntimeMetricsIntegration() (Bun)
Recommendation logic:
Feature
Recommend when...
Error Monitoring
Always — non-negotiable baseline
OTLP Integration
OTel tracing detected — replaces native Tracing
Tracing
Always for server apps — HTTP spans + DB spans are high-value; skip if OTel tracing detected
Logging
App uses winston, pino, bunyan, or needs log-to-trace correlation
Profiling
Node.js only — performance-critical service; native addon compatible; skip if OTel tracing detected (requires tracesSampleRate, incompatible with OTLP)
AI Monitoring
App calls OpenAI, Anthropic, LangChain, Vercel AI, or Google GenAI
Crons
App uses node-cron, Bull, BullMQ, Agenda, or any scheduled task pattern
Metrics
App needs custom counters, gauges, or histograms
Runtime Metrics
Any Node.js or Bun service wanting automatic memory/CPU/event-loop visibility
OTel tracing detected:"I see OpenTelemetry tracing in the project. I recommend Sentry's OTLP integration for tracing (via your existing OTel setup) + Error Monitoring + Sentry Logging [+ Metrics/Crons/AI Monitoring if applicable]. Shall I proceed?"
No OTel:"I recommend setting up Error Monitoring + Tracing. Want me to also add Logging or Profiling?"
Phase 3: Guide
Runtime: Node.js
Option 1: Wizard (Recommended for Node.js)
You need to run this yourself — the wizard opens a browser for login and requires interactive input that the agent can't handle. Copy-paste into your terminal:
npx @sentry/wizard@latest -i node
It handles login, org/project selection, SDK installation, instrument.js creation, and package.json script updates.
Once it finishes, come back and skip to Verification.
If the user skips the wizard, proceed with Option 2 (Manual Setup) below.
Option 2: Manual Setup — Node.js
Install
bash
npm install @sentry/node --save
# or
yarn add @sentry/node
# or
pnpm add @sentry/node
Create the Instrument File
CommonJS (instrument.js):
javascript
// instrument.js — must be loaded before all other modules
const Sentry = require("@sentry/node");
Sentry.init({
dsn: process.env.SENTRY_DSN ?? "___DSN___",
dataCollection: {
// To disable sending user data and HTTP bodies, uncomment the lines below. For more info visit:
// https://docs.sentry.io/platforms/javascript/guides/node/configuration/options/#dataCollection
// userInfo: false,
// httpBodies: [],
},
// 100% in dev, lower in production
tracesSampleRate: process.env.NODE_ENV === "development" ? 1.0 : 0.1,
// Capture local variable values in stack frames
includeLocalVariables: true,
enableLogs: true,
});
ESM (instrument.mjs):
javascript
// instrument.mjs — loaded via --import flag before any other module
import * as Sentry from "@sentry/node";
Sentry.init({
dsn: process.env.SENTRY_DSN ?? "___DSN___",
dataCollection: {
// To disable sending user data and HTTP bodies, uncomment the lines below. For more info visit:
// https://docs.sentry.io/platforms/javascript/guides/node/configuration/options/#dataCollection
// userInfo: false,
// httpBodies: [],
},
tracesSampleRate: process.env.NODE_ENV === "development" ? 1.0 : 0.1,
includeLocalVariables: true,
enableLogs: true,
});
Start Your App with Sentry Loaded First
CommonJS — add require("./instrument") as the very first line of your entry file:
javascript
// app.js
require("./instrument"); // must be first
const express = require("express");
// ... rest of your app
ESM — use the --import flag so Sentry loads before all other modules (Node.js 18.19.0+ required):
const Koa = require("koa");
const Sentry = require("@sentry/node");
const app = new Koa();
// Add as FIRST middleware (catches errors thrown by later middleware)
Sentry.setupKoaErrorHandler(app);
// ... your other middleware and routes
app.listen(3000);
Hapi (async — must await):
javascript
const Hapi = require("@hapi/hapi");
const Sentry = require("@sentry/node");
const server = Hapi.server({ port: 3000 });
// ... your routes
// Must await — Hapi registration is async
await Sentry.setupHapiErrorHandler(server);
await server.start();
Connect:
javascript
const connect = require("connect");
const Sentry = require("@sentry/node");
const app = connect();
// Add BEFORE routes (like Fastify and Koa)
Sentry.setupConnectErrorHandler(app);
// ... your middleware and routes
require("http").createServer(app).listen(3000);
NestJS — has its own dedicated skill with full coverage:
Use the sentry-nestjs-sdk skill instead.
NestJS uses a separate package (@sentry/nestjs) with NestJS-native constructs:
SentryModule.forRoot(), SentryGlobalFilter, @SentryTraced, @SentryCron decorators,
and GraphQL/Microservices support. Load that skill for complete NestJS setup.
@sentry/bun automatically instruments Bun.serve() via JavaScript Proxy. No extra setup is required — just initialize with --preload and your Bun.serve() calls are traced:
typescript
// server.ts
const server = Bun.serve({
port: 3000,
fetch(req) {
return new Response("Hello from Bun!");
},
});
Framework Error Handlers on Bun
Bun can run Express, Fastify, Hono, and Elysia. Use the same @sentry/bun import and the @sentry/node error handler functions (re-exported by @sentry/bun):
typescript
import * as Sentry from "@sentry/bun";
import express from "express";
const app = express();
// ... routes
Sentry.setupExpressErrorHandler(app);
app.listen(3000);
Bun Feature Support
Feature
Bun Support
Notes
Error Monitoring
✅ Full
Same API as Node
Tracing
✅ Via @sentry/node OTel
Most auto-instrumentations work
Logging
✅ Full
enableLogs: true + Sentry.logger.*
Profiling
❌ Not available
@sentry/profiling-node uses native addons incompatible with Bun
No wizard available for Deno. Manual setup only.
Requires Deno 2.0+. Deno 1.x is not supported.
Use npm: specifier. The deno.land/x/sentry registry is deprecated.
// main.ts — Sentry.init() must be called before any other code
import * as Sentry from "@sentry/deno";
Sentry.init({
dsn: Deno.env.get("SENTRY_DSN") ?? "___DSN___",
dataCollection: {
// To disable sending user data and HTTP bodies, uncomment the lines below. For more info visit:
// https://docs.sentry.io/platforms/javascript/guides/node/configuration/options/#dataCollection
// userInfo: false,
// httpBodies: [],
},
tracesSampleRate: Deno.env.get("DENO_ENV") === "development" ? 1.0 : 0.1,
enableLogs: true,
});
// Your application code follows
Deno.serve({ port: 8000 }, (req) => {
return new Response("Hello from Deno!");
});
Unlike Node.js and Bun, Deno does not have a --preload or --import flag. Sentry must be the first import in your entry file.
Required Deno Permissions
The SDK requires network access to reach your Sentry ingest domain:
bash
deno run \
--allow-net=o<ORG_ID>.ingest.sentry.io \
--allow-read=./src \
--allow-env=SENTRY_DSN,SENTRY_RELEASE \
main.ts
For development, --allow-all works but is not recommended for production.
Deno Cron Integration
Deno provides native cron scheduling. Use denoCronIntegration for automatic monitoring:
typescript
import * as Sentry from "@sentry/deno";
import { denoCronIntegration } from "@sentry/deno";
Sentry.init({
dsn: Deno.env.get("SENTRY_DSN") ?? "___DSN___",
integrations: [denoCronIntegration()],
});
// Cron is automatically monitored
Deno.cron("daily-cleanup", "0 0 * * *", () => {
// cleanup logic
});
Deno Feature Support
Feature
Deno Support
Notes
Error Monitoring
✅ Full
Unhandled exceptions + captureException
Tracing
✅ Custom OTel
Automatic spans for Deno.serve() and fetch
Logging
✅ Full
enableLogs: true + Sentry.logger.*
Profiling
❌ Not available
No profiling addon for Deno
Metrics
✅ Full
Sentry.metrics.*
Runtime Metrics
❌ Not available
No runtime metrics integration for Deno
Crons
✅ Full
denoCronIntegration() + Sentry.withMonitor()
AI Monitoring
✅ Partial
Vercel AI SDK integration works; OpenAI/Anthropic via npm:
Use this path only when OpenTelemetry tracing was detected in Phase 1
(e.g., @opentelemetry/sdk-node or @opentelemetry/sdk-trace-node in package.json).
For projects without an existing OTel setup, use the standard @sentry/node path above.
The OTLP integration uses @sentry/node-core/light — a lightweight Sentry SDK that does not bundle its own OpenTelemetry. Instead, it hooks into the user's existing OTel TracerProvider and exports spans to Sentry via OTLP.
When to Use
Scenario
Recommended path
New project, no existing OTel
Standard @sentry/node (above) — includes built-in OTel
The @opentelemetry/* packages are peer dependencies. If the project already has them installed, skip duplicates.
Initialize
javascript
// instrument.mjs — load via --import flag before any other module
import { NodeTracerProvider } from '@opentelemetry/sdk-trace-node';
import * as Sentry from '@sentry/node-core/light';
import { otlpIntegration } from '@sentry/node-core/light/otlp';
// Register the user's OTel TracerProvider first
const provider = new NodeTracerProvider();
provider.register();
Sentry.init({
dsn: process.env.SENTRY_DSN ?? '___DSN___',
dataCollection: {
// To disable sending user data and HTTP bodies, uncomment the lines below. For more info visit:
// https://docs.sentry.io/platforms/javascript/guides/node/configuration/options/#dataCollection
// userInfo: false,
// httpBodies: [],
},
enableLogs: true,
// Do NOT set tracesSampleRate — OTel controls sampling
integrations: [
otlpIntegration({
// Export OTel spans to Sentry via OTLP (default: true)
setupOtlpTracesExporter: true,
}),
],
});
OpenAI, Anthropic, LangChain, Vercel AI, Google GenAI
For each feature: read the reference file, follow its steps exactly, and verify before moving on.
Show full SKILL.md (884 more words)Show less
Runtime Metrics
Automatically collect Node.js and Bun runtime health metrics (memory, CPU utilization, event loop delay/utilization, uptime) at a configurable interval. Metrics appear in Sentry's Metrics product under the node.runtime.* / bun.runtime.* namespace.
Node.js — add nodeRuntimeMetricsIntegration() to your instrument.js:
Metrics collected: same as Node.js except no event loop delay percentiles (unavailable in Bun). Prefixed with bun.runtime.*.
Configuration Reference
Sentry.init() Core Options
Option
Type
Default
Notes
dsn
string
—
Required. Also from SENTRY_DSN env var
tracesSampleRate
number
—
0–1; required to enable tracing; do not set when using OTLP path
dataCollection
object
conservative unless set
Fine-grained control over auto-collected categories (userInfo, cookies, httpHeaders, httpBodies, queryParams, genAI). When omitted, the SDK falls back to sendDefaultPii (default false). Passing the object — even {} — flips unset categories to their permissive defaults; opt out per category.
includeLocalVariables
boolean
false
Add local variable values to stack frames (Node.js)
enableLogs
boolean
false
Enable Sentry Logs product (v9.41.0+)
environment
string
"production"
Also from SENTRY_ENVIRONMENT env var
release
string
—
Also from SENTRY_RELEASE env var
debug
boolean
false
Log SDK activity to console
enabled
boolean
true
Set false in tests to disable sending
sampleRate
number
1.0
Fraction of error events to send (0–1)
shutdownTimeout
number
2000
Milliseconds to flush events before process exit
nativeNodeFetchIntegration() Options
Configures outgoing fetch/undici span capture. Since @opentelemetry/instrumentation-undici@0.22.0, response headers like content-length are no longer captured automatically — use headersToSpanAttributes to opt in:
For OTel-first projects using @sentry/node-core/light. Import: import { otlpIntegration } from '@sentry/node-core/light/otlp'.
Option
Type
Default
Purpose
setupOtlpTracesExporter
boolean
true
Auto-configure OTLP exporter to send spans to Sentry; set false if you already export to your own Collector
collectorUrl
string
undefined
OTLP HTTP endpoint of an OTel Collector (e.g., http://localhost:4318/v1/traces); when set, spans are sent to the collector instead of the DSN-derived Sentry endpoint
Graceful Shutdown
Flush buffered events before process exit — important for short-lived scripts and serverless:
Readable stack traces in production require uploading source maps with @sentry/cli or the webpack/esbuild/rollup plugins — for example, an inject + upload step in your build:
Upload needs a SENTRY_AUTH_TOKEN (a build-time secret). For creating the token and wiring it into CI, see sentry-source-maps.
Verification
After setup, verify Sentry is receiving events:
javascript
// Add temporarily to your entry file or a test route, then remove
import * as Sentry from "@sentry/node"; // or @sentry/bun / @sentry/deno
Sentry.captureException(new Error("Sentry test error — delete me"));
Or trigger an unhandled exception:
javascript
// In a route handler or startup — will be captured automatically
throw new Error("Sentry test error — delete me");
Connecting frontend and backend with the same DSN or linked projects enables distributed tracing — stack traces that span your browser, API server, and database in a single trace view.
Troubleshooting
Issue
Cause
Solution
Events not appearing
instrument.js loaded too late
Ensure it's the first require() / loaded via --import or --preload
Tracing spans missing
tracesSampleRate not set
Add tracesSampleRate: 1.0 to Sentry.init()
ESM instrumentation not working
Missing --import flag
Run with node --import ./instrument.mjs; import "./instrument.mjs" inside app is not sufficient
@sentry/profiling-node install fails on Bun
Native addon incompatible
Profiling is not supported on Bun — remove @sentry/profiling-node
Deno: events not sent
Missing --allow-net permission
Run with --allow-net=o<ORG_ID>.ingest.sentry.io
Deno: deno.land/x/sentry not working
Deprecated and frozen at v8.55.0
Switch to npm:@sentry/deno specifier
includeLocalVariables not showing values
Integration not activated or minified code
Ensure includeLocalVariables: true in init; check source maps
NestJS: errors not captured
Wrong SDK or missing filter
Use sentry-nestjs-sdk — NestJS needs @sentry/nestjs, not @sentry/node
Hapi: setupHapiErrorHandler timing issue
Not awaited
Must await Sentry.setupHapiErrorHandler(server) before server.start()
Shutdown: events lost
Process exits before flush
Add await Sentry.close(2000) in SIGTERM/SIGINT handler
Stack traces show minified code
Source maps not uploaded
Configure @sentry/cli source map upload in build step
No traces appearing (OTLP)
Missing @opentelemetry/* packages or otlpIntegration not added
Verify @opentelemetry/sdk-trace-node is installed; add otlpIntegration() to integrations; do not set tracesSampleRate
OTLP: errors not linked to traces
otlpIntegration not registered
Ensure otlpIntegration() is in the integrations array — it registers the propagation context that links errors to OTel traces
Profiling not starting (OTLP)
Profiling requires tracesSampleRate
Profiling is not compatible with the OTLP path; use the standard @sentry/node setup instead
Sentry Node SDK next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
Runs pre-trained Hugging Face models in JavaScript or TypeScript with Transformers.js, in browsers or Node.js, Bun and Deno, for text, vision, audio and multimodal tasks.
Full Sentry SDK setup for Node.js, Bun, and Deno. An agent skill from getsentry/sentry-for-ai. Sentry Node SDK is an agent skill from getsentry/sentry-for-ai, published by the product's own GitHub organization.js, Bun, and Deno.
When should I use Sentry Node SDK?
Sentry Node SDK fits situations like: asked to add Sentry to Node.js; add Sentry to Bun; add Sentry to Deno; install @sentry/node.
How do I install Sentry Node SDK in Claude Code?
Run `npx skills add getsentry/sentry-for-ai --skill sentry-node-sdk -a claude-code`. Or copy the skill folder (skills-legacy/sentry-node-sdk in getsentry/sentry-for-ai) into .claude/skills/sentry-node-sdk in your project. Claude Code loads it when a task matches its description.
How do I install Sentry Node SDK in Codex?
Run `npx skills add getsentry/sentry-for-ai --skill sentry-node-sdk -a codex`. Or copy the skill folder (skills-legacy/sentry-node-sdk in getsentry/sentry-for-ai) into .agents/skills/sentry-node-sdk in your project. Codex loads it when a task matches its description.
Can I use Sentry Node SDK in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add getsentry/sentry-for-ai --skill sentry-node-sdk -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/sentry-node-sdk, .gemini/skills/sentry-node-sdk, .github/skills/sentry-node-sdk and .opencode/skills/sentry-node-sdk in your project.
What does Sentry Node SDK need to run?
Going by SKILL.md and its folder, Sentry Node SDK needs the command-line tools its instructions call (bun, node, npm, deno, yarn and pnpm) and credentials named SENTRY_AUTH_TOKEN. Our summary lists: Node.js.
Does Sentry Node SDK access the network?
SKILL.md names 2 domains. In commands or code: docs.sentry.io; the agent is likely to contact it when it follows the instructions. As links in the text: sentry.io. This is read from the text; nothing was executed.
Is Sentry Node SDK safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Sentry Node SDK use?
Sentry Node SDK is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Sentry Node SDK use?
About 8.4k tokens (SKILL.md is roughly 34k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 28k tokens, read only when the agent opens those files.
What are the alternatives to Sentry Node SDK?
Skills that share tags, products or a category with Sentry Node SDK: Javascript SDK (aiskillstore/marketplace, 430 stars), Node Backend Development Guidelines (diet103/claude-code-infrastructure-showcase, 10k stars), PayRam Checkout Integration (PayRam/payram-mcp, 158 stars) and Transformers.js (huggingface/skills, 11k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Sentry Node SDK?
getsentry (a GitHub organization, an official publisher) maintains it in getsentry/sentry-for-ai, which has 268 GitHub stars. The repository holds 32 skills in this directory. The repository was last updated on October 7, 2026.
Source: getsentry/sentry-for-ai on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.