Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →gotempsh/add-error-tracking
Add Temps error tracking to applications using the Sentry-compatible SDK. Temps exposes a Sentry-compatible DSN that works with the official Sentry SDK for each language/framework — no code changes beyond initialization are required.
Passed 22 of 23 test cases with the skill, and 11 of 23 without it.
and 21 more in the full report
12 fixed10 passed either way0 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 12 test cases the skill fixed. Same model, same prompt, with and without the skill.
A developer cannot find where to retrieve the project connection DSN string inside the Temps user interface. Where exactly in the dashboard is this located?
| Checked | Without skill | With skill |
|---|---|---|
| Directs user to Error Tracking DSN & Setup in Temps dashboard | Missed | Passed |
The instructions your model reads when the skill loads.
Integrate Temps error tracking (Sentry-compatible) into an application. The Temps DSN is a drop-in replacement for a Sentry DSN — use the official Sentry SDK for the user's platform and point it at the Temps DSN via an environment variable.
Temps is Sentry wire-compatible, so every skill Sentry publishes for their SDKs works against a Temps DSN. If the user's CLI already has one of these installed, route them to it and only substitute the DSN:
| User's platform | Sentry skill | Source |
|---|---|---|
| Next.js | /sentry-nextjs-sdk | getsentry/sentry-for-ai |
| React (Vite, Remix, etc.) | /sentry-react-sdk | getsentry/sentry-for-ai |
| Vanilla browser JS | /sentry-browser-sdk | getsentry/sentry-for-ai |
| Node.js | /sentry-node-sdk | getsentry/sentry-for-ai |
| React Native | /sentry-react-native-sdk | getsentry/sentry-for-ai |
| Generic (language-agnostic) | /sentry-sdk-setup | getsentry/sentry-for-ai |
For platforms Sentry has no dedicated skill for (Vue, Svelte, Angular, Python, Go, Rust, Ruby, Java, PHP, .NET, Flutter, etc.), follow the setup in this file directly.
Always set the DSN from an environment variable — never hardcode it. The user will point the env var at their Temps DSN instead of a Sentry DSN.
Infer the platform from the codebase:
package.json with "next" → Next.js → @sentry/nextjspackage.json with "react" and Vite/Remix/CRA → React → @sentry/reactpackage.json with "vue" or "nuxt" → Vue → @sentry/vuepackage.json with "svelte" or "@sveltejs/kit" → Svelte → @sentry/sveltekitpackage.json with "@angular/core" → Angular → @sentry/angularpackage.json with "express", "fastify", "@nestjs/core" → Node.js → @sentry/nodepackage.json with "react-native" or "expo" → React Native → @sentry/react-nativerequirements.txt/pyproject.toml with Flask, Django, FastAPI → Python → sentry-sdkgo.mod → Go → github.com/getsentry/sentry-goCargo.toml → Rust → sentryGemfile with rails → Ruby → sentry-ruby + sentry-railspom.xml/build.gradle with Spring → Java → sentry-spring-boot-starter-jakartacomposer.json with laravel/framework or symfony/* → PHP → sentry/sentry.csproj with Microsoft.AspNetCore.* → .NET → Sentry.AspNetCorepubspec.yaml with flutter → Flutter → sentry_fluttertest cases passed, vs 11 / 23 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.