REPO PACKAGE
getsentry sentry-for-ai
OFFICIAL32skills
3groups
3ready to use
LABSCO SUMMARY
The skills do three different jobs. Most are full SDK setup wizards — one per platform, each scanning the project and walking through error monitoring, tracing, profiling, session replay, and logging for that stack; the README's own table names fifteen platforms, but the live skill list also includes wizards for the browser, Cloudflare Workers, Elixir, and Flutter that the table leaves out. A smaller group covers specific features: AI/LLM call monitoring, an OpenTelemetry Collector exporter, and a guide for choosing between an error, a span, a log, or a metric. The rest is workflow — finding and fixing issues through the Sentry MCP server, creating alerts, and generating new SDK-wizard skills from a template.
This is for a team already sending errors to Sentry, or about to, that wants its coding agent to install the SDK correctly the first time and later triage what Sentry catches without leaving the editor — not for evaluating whether to adopt Sentry itself. The distribution model matters too: this repository is the source of truth but is not itself installable; four separate downstream repositories, one each for Claude Code, Cursor, Codex, and Grok, are built from it by CI and are what actually gets added to an agent.
READ THE FULL ANALYSIS
What it costs to start. Twenty-four of the 33 skills need a live Sentry project — and the plugin's auto-configured MCP connection — before they do more than write install code. A few workflow skills also expect the GitHub CLI (gh) authenticated, which the README calls out but does not set up for you.
Who this isn't for. If you don't run Sentry, none of this applies: every skill here assumes an existing or soon-to-exist Sentry project, and there's no offline or eval mode the way a purely local tool would have one.
The README undercounts its own wizards. Its "SDK Setup Wizards" table lists fifteen platforms, which is the number worth quoting if you're citing this package, but four more wizard skills exist in the live set than that table shows — a small but real gap between the docs and what actually ships.
ALSO IN THIS PACKAGE
2 items
skill-creator
skill-updater
MCP SERVERS
1 itemMCP SERVER
sentry
Official Sentry MCP server for investigating issues, error reports, traces, and performance monitoring data from AI coding agents.
http · https://mcp.sentry.dev/mcp?utm_source=pluginWHAT'S INSIDE
32 showing · 32 totalReady to use
Nothing else to set up — install it and go.
32 of 32
SETUP
Showing all 32 skills
sentry-android-sdk
Gets an Android app reporting its crashes to Sentry — including the freezes where the app stops responding, and the failures down in the native code underneath it.
sentry-browser-sdk
Error reporting for a website built without a framework — a hand-written page, a WordPress or Shopify shop — including a replay of what the visitor did before it broke.
sentry-cloudflare-sdk
Puts Sentry into code running on Cloudflare's network, so a request that fails out there comes back with everything it touched on the way — databases, queues, background jobs.
sentry-cocoa-sdk
Reports what goes wrong inside an iPhone, iPad, Mac, Apple TV, Watch or Vision app — the crashes, the freezes, and the times the system killed the app for not responding.
sentry-dotnet-sdk
Wires a .NET program up to Sentry — a web service, a desktop application or a phone app — so a crash and the log lines leading up to it arrive in one place.
sentry-elixir-sdk
An Elixir or Phoenix app can lose a background process quietly; this sets Sentry up to report those crashes, and to time requests and database calls where the usual libraries are in place.
sentry-fix-issues
Starts from an error report sitting in Sentry, works out from the code why it happened, and changes the code so it stops happening.
sentry-flutter-sdk
Flutter builds one codebase into phone, desktop and web apps; this puts Sentry into whichever of those the app actually ships, so crashes come back from all of them.
sentry-go-sdk
Sets a Go service up to report its own crashes, its request timings and its log output to Sentry, whichever web framework or logging library it happens to be built on.
sentry-instrumentation-guide
Software records what it is doing in four different ways, and picking the wrong one leaves you with data that answers a question you weren't asking — this is how to choose between them.
sentry-nestjs-sdk
Puts Sentry into a NestJS backend, so a failure is reported no matter how the request arrived — an ordinary web call, a GraphQL query, an open socket, or a message from another service.
sentry-nextjs-sdk
Sets Sentry up in a Next.js site — in the visitor's browser and on every server it runs on — so an error or a slow page is reported wherever it came from.
sentry-node-sdk
Gets a JavaScript backend — Node.js, Bun or Deno — reporting its crashes and its slow requests, without tearing out the timing setup the project may already have.
sentry-php-sdk
Adds crash and error reporting to a PHP site, whether it is plain PHP or built on Laravel or Symfony, and pulls its log messages in alongside.
sentry-python-sdk
A crash in a Python service should arrive with the request that caused it — this is the setup that makes that happen, under Django, Flask, FastAPI or a Celery worker.
sentry-react-native-sdk
Sets Sentry up in a React Native or Expo app, so a crash is reported together with the screen the user was on and what they tapped just before it.
sentry-react-router-framework-sdk
A React Router version 7 site runs half in the browser and half on the server; this catches the errors on both sides and times the requests that pass between them.
sentry-react-sdk
Adds error reporting to a React app — including the errors an error boundary would otherwise swallow — with a replay of the clicks that led up to one.
sentry-ruby-sdk
Gets a Ruby or Rails app reporting its exceptions and its logs to Sentry, including the ones thrown deep inside a background job where nobody was watching.
sentry-sdk-setup
Works out what a project is written in and hands over to the Sentry setup guide for that particular language or framework.
sentry-sdk-upgrade
Moves a JavaScript project onto a newer major version of Sentry, walking through each breaking change in the official upgrade notes and applying it to the code that is actually there.
sentry-setup-ai-monitoring
Shows in Sentry what an app's AI is doing: which model was asked, how long the answer took, how many tokens it burned, and the turns of one chat grouped together.
sentry-svelte-sdk
When a Svelte app breaks for a user you never hear from, this is what tells you — the error, the trace around it, and a replay of what they were doing.
sentry-tanstack-start-sdk
A TanStack Start app runs in two places at once, so Sentry has to go into both — this wires up the browser side and the server side, then proves each one reports.
Choosing what else to send4 skills
sentry-fix-stack-traces
When Sentry's error reports point at scrambled code instead of your own file names and line numbers, this gets the missing lookup files uploaded from your build so the next error reads properly.
sentry-otel-exporter-setup
Several services already send their telemetry into one shared OpenTelemetry pipeline — this branches that stream off to Sentry, each service landing in its own project.
sentry-setup-releases
Makes every error in Sentry say which version of your app it came from, which code changes went into that version, and which change most likely caused it.
sentry-snapshots-cocoa
Takes pictures of an Apple app's screens on every pull request and sends them to Sentry, so a change that alters how something looks is spotted before it ships.
Installing the SDK2 skills
sentry-get-started
The front door to Sentry, a service that catches the errors your software runs into and shows where they came from. On a new project it sets Sentry up and proves a real error arrives; on one that already has it, it points you to the right next step.
sentry-instrument
Gets Sentry recording one more kind of information about your app — or its very first error on a new install — and does not call it finished until a real example has turned up in Sentry.
Once it is in production2 skills
sentry-create-alert
Sentry spots a problem at two in the morning; this is where you decide who hears about it and how — by email, Slack, PagerDuty or Discord.
sentry-debug-issue
One error report in Sentry, carried all the way from “something is broken” to a shipped fix: the cause found in your own code, a test that reproduces it, and the report closed by the change itself.
No skill in this package matches that.
HOW TO GET IT
WHOLE PACKAGEInstall the whole package (32 skills)
npx skills add getsentry/sentry-for-aiSINGLE SKILLOr install a single skill
npx skills add getsentry/sentry-for-ai --skill <name> --full-depthPick the skill name from the Skills tab — each entry there installs independently.