Agent skill

Add Error Tracking

by gotempsh in gotempsh/temps

Add Temps error tracking to applications using the Sentry-compatible SDK.

Apache-2.0Auto-check: notesMobile

Install Add Error Tracking

skills CLI
$ npx skills add gotempsh/temps --skill add-error-tracking -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install gotempsh/temps add-error-tracking --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/gotempsh/temps.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/add-error-tracking .claude/skills/add-error-tracking && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
add-error-tracking
GitHub stars
822
Token cost
~4.2k tokens
SKILL.md length
1,204 words
Files
1
Skills in repo
15
Repo updated
First seen
Licence
Apache-2.0

At a glance

Add Temps error tracking to applications using the Sentry-compatible SDK.

  • Works in 3 steps: Open their project in the Temps dashboard → Go to Error Tracking → DSN & Setup → Copy the DSN for the target environment
  • The user wants to:
  • SKILL.md covers Prefer Sentry's official…, Detect the platform, Get the DSN and Browser SDKs: also pass tunnel, plus 5 more sections
  • Calls npm, npx and flutter

What it does

Add Error Tracking is an agent skill from gotempsh/temps. 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. Use when the user wants to: (1) Add error tracking to any app (React, Next.js, Vue, Svelte, Angular, Node.js, Python, Go, Rust, Ruby, Java, PHP, .NET, React Native, Flutter), (2) Wire up uncaught exception and unhandled promise rejection capture, (3) Configure session replay for…

Its SKILL.md is about 4.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Mobile, covering Cross-platform mobile apps and Debugging. It works with Sentry, Next.js, React and Rust. The repository describes itself as: AI-native open-source alternative to Vercel + Sentry + PostHog + Pingdom + Resend + E2B. 440+ CLI operations with drop-in skills for Claude Code, Codex & OpenCode — deployments… The licence is Apache-2.0.

When your agent uses it

  • The user wants to:
  • Add error tracking to any app (React
  • Wire up uncaught exception and unhandled promise rejection capture
  • Configure session replay for errors

Example prompts

  • “add error tracking”
  • “add sentry”
  • “track exceptions”
  • “/add-error-tracking”

Requirements

  • Python 3
  • Node.js

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

  1. Open their project in the Temps dashboard
  2. Go to Error Tracking → DSN & Setup
  3. Copy the DSN for the target environment

What it can do on your machine

Read from SKILL.md and the folder at commit 80aff9a. 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:

    • npm
    • npx
    • flutter
    • pip
    • go
    • cargo
    • bundle
    • composer
    • dotnet

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use npm, npx and pip, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Add Error Tracking loads about 4.2k tokens when it runs. Until then it costs about 200 tokens; SKILL.md has 1,204 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~200
When it runs · the whole SKILL.md, loaded when a task matches
~4.2k

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: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NoteMentions a .env fileSKILL.md:72
    # .env
  • NoteMentions a .env fileSKILL.md:566
    nvironment sets the DSN env var — local `.env` files are not copied automatically.

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.

SKILL.md

The full file from gotempsh/temps at commit 80aff9a, republished under its Apache-2.0 licence (© gotempsh). 1,204 words, ~4,214 tokens.

Download SKILL.mdSave it as .claude/skills/add-error-tracking/SKILL.md (or your agent's skills folder).
name
add-error-tracking
description
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. Use when the user wants to: (1) Add error tracking to any app (React, Next.js, Vue, Svelte, Angular, Node.js, Python, Go, Rust, Ruby, Java, PHP, .NET, React Native, Flutter), (2) Wire up uncaught exception and unhandled promise rejection capture, (3) Configure session replay for errors, (4) Upload source maps for readable stack traces, (5) Report releases and environments, (6) Capture custom errors/messages. Triggers: "add error tracking", "add sentry", "track exceptions", "report errors", "temps error tracking", "wire up error monitoring".

Add Error Tracking

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.

Prefer Sentry's official per-framework skills when available

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 platformSentry skillSource
Next.js/sentry-nextjs-sdkgetsentry/sentry-for-ai
React (Vite, Remix, etc.)/sentry-react-sdkgetsentry/sentry-for-ai
Vanilla browser JS/sentry-browser-sdkgetsentry/sentry-for-ai
Node.js/sentry-node-sdkgetsentry/sentry-for-ai
React Native/sentry-react-native-sdkgetsentry/sentry-for-ai
Generic (language-agnostic)/sentry-sdk-setupgetsentry/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.

Detect the platform

Infer the platform from the codebase:

  • package.json with "next" → Next.js → @sentry/nextjs
  • package.json with "react" and Vite/Remix/CRA → React → @sentry/react
  • package.json with "vue" or "nuxt" → Vue → @sentry/vue
  • package.json with "svelte" or "@sveltejs/kit" → Svelte → @sentry/sveltekit
  • package.json with "@angular/core" → Angular → @sentry/angular
  • package.json with "express", "fastify", "@nestjs/core" → Node.js → @sentry/node
  • package.json with "react-native" or "expo" → React Native → @sentry/react-native
  • requirements.txt/pyproject.toml with Flask, Django, FastAPI → Python → sentry-sdk
  • go.mod → Go → github.com/getsentry/sentry-go
  • Cargo.toml → Rust → sentry
  • Gemfile with rails → Ruby → sentry-ruby + sentry-rails
  • pom.xml/build.gradle with Spring → Java → sentry-spring-boot-starter-jakarta
  • composer.json with laravel/framework or symfony/* → PHP → sentry/sentry
  • .csproj with Microsoft.AspNetCore.* → .NET → Sentry.AspNetCore
  • pubspec.yaml with flutter → Flutter → sentry_flutter

Get the DSN

The user's Temps project exposes a DSN at Error Tracking → DSN & Setup. It looks like:

https://<public_key>@<temps-host>/<project_id>

If the user has not provided a DSN, tell them to:

  1. Open their project in the Temps dashboard
  2. Go to Error Tracking → DSN & Setup
  3. Copy the DSN for the target environment

Always store the DSN in an environment variable. The exact variable name depends on the platform (browser bundlers often require a prefix to expose vars to the client):

PlatformEnv var name
Next.jsNEXT_PUBLIC_SENTRY_DSN
Vite / React / VueVITE_SENTRY_DSN
SvelteKitPUBLIC_SENTRY_DSN
AngularSENTRY_DSN (injected via environment.ts)
Everything else (Node, Python, Go, Rust, Ruby, Java, PHP, .NET, Flutter)SENTRY_DSN
bash
# .env
SENTRY_DSN=https://<public_key>@<temps-host>/<project_id>

Browser SDKs: also pass tunnel

For every browser platform (Next.js client config, React, Vue, Svelte, vanilla JS — not server-side SDKs, not React Native/Flutter), also pass tunnel in the same Sentry.init call:

ts
Sentry.init({
  dsn: process.env.NEXT_PUBLIC_SENTRY_DSN,
  tunnel: process.env.NEXT_PUBLIC_SENTRY_TUNNEL,
});

Why: without tunnel, the SDK POSTs straight to the DSN's host (the Temps console), which is a third-party, cross-origin request from the app's own domain — ad blockers commonly block it, and it costs a CORS preflight on every event. With tunnel set to a same-origin path, the browser posts to the app's own domain instead; Temps' proxy forwards anything under /api/_temps to the console regardless of which project domain it arrived on, so this works unmodified on custom domains and preview URLs.

The value is a fixed path, not a secret — Temps injects it automatically as an env var alongside the DSN, under the same bundler-specific public prefix (so if the DSN reaches the client bundle, the tunnel path does too):

PlatformDSN env varTunnel env var
Next.jsNEXT_PUBLIC_SENTRY_DSNNEXT_PUBLIC_SENTRY_TUNNEL
Vite / React / VueVITE_SENTRY_DSNVITE_SENTRY_TUNNEL
SvelteKitPUBLIC_SENTRY_DSNPUBLIC_SENTRY_TUNNEL
AngularSENTRY_DSN (via environment.ts)(none — no public-prefix convention; skip tunnel)

If deploying outside Temps (or the tunnel var isn't set for some other reason), you have two options. Omit tunnel — the SDK falls back to posting straight to the DSN host, which still works, just cross-origin. Or point tunnel at the absolute tunnel URL of the Temps instance, e.g. tunnel: "https://your-temps-instance.example.com/api/_temps/sentry/envelope": the endpoint resolves the project from the DSN the SDK embeds in the envelope, so it does not need the app to be served by Temps. That keeps the tunnel's ad-blocker resistance for an app Temps does not host, at the cost of the cross-origin request the same-origin variant avoids.

Leave out Sentry.replayIntegration() and tracesSampleRate for browser projects unless you specifically want them — Temps doesn't yet ingest Sentry session replay or performance transactions, so that traffic would be uploaded (through the tunnel, using the visitor's bandwidth) and discarded server-side. Use Temps' own session replay and analytics SDKs for those instead (see the add-session-recording and add-react-analytics skills).

Platform setup

Every snippet below reads the DSN from an env var — do not hardcode it.

Show full SKILL.md (477 more words)Show less
Next.js
bash
npx @sentry/wizard@latest -i nextjs

Or manually:

bash
npm install @sentry/nextjs
ts
// sentry.client.config.ts (or instrumentation-client.ts on newer @sentry/nextjs)
import * as Sentry from '@sentry/nextjs';

Sentry.init({
  dsn: process.env.NEXT_PUBLIC_SENTRY_DSN,
  tunnel: process.env.NEXT_PUBLIC_SENTRY_TUNNEL,
});

Mirror the dsn (no tunnel, no replay) in sentry.server.config.ts and sentry.edge.config.ts — those run server-side and post directly to the console.

Do not set tunnelRoute in withSentryConfig — it's a different mechanism (forwards through a Next.js server route) and its own docs state it doesn't work with self-hosted Sentry, which is what Temps' DSN compatibility layer is. Use the tunnel option shown above instead.

React (Vite, Remix, CRA)
bash
npm install @sentry/react
tsx
// src/sentry.ts — import this first in main.tsx / root.tsx
import * as Sentry from '@sentry/react';

Sentry.init({
  dsn: import.meta.env.VITE_SENTRY_DSN,
  tunnel: import.meta.env.VITE_SENTRY_TUNNEL,
  environment: import.meta.env.MODE,
});

Wrap the app root with <Sentry.ErrorBoundary> for React render errors.

Vue (Vue 3 / Nuxt)
bash
npm install @sentry/vue
ts
// src/main.ts
import { createApp } from 'vue';
import * as Sentry from '@sentry/vue';
import App from './App.vue';

const app = createApp(App);

Sentry.init({
  app,
  dsn: import.meta.env.VITE_SENTRY_DSN,
  tunnel: import.meta.env.VITE_SENTRY_TUNNEL,
});

app.mount('#app');
Svelte / SvelteKit
bash
npx @sentry/wizard@latest -i sveltekit
ts
// src/hooks.client.ts
import * as Sentry from '@sentry/sveltekit';
import { PUBLIC_SENTRY_DSN, PUBLIC_SENTRY_TUNNEL } from '$env/static/public';

Sentry.init({
  dsn: PUBLIC_SENTRY_DSN,
  tunnel: PUBLIC_SENTRY_TUNNEL,
});

export const handleError = Sentry.handleErrorWithSentry();

Mirror in src/hooks.server.ts using $env/dynamic/private for the server DSN.

Angular
bash
npm install @sentry/angular
ts
// src/main.ts
import * as Sentry from '@sentry/angular';
import { environment } from './environments/environment';

Sentry.init({
  dsn: environment.sentryDsn,
  tracesSampleRate: 1.0,
});

Populate environment.sentryDsn from process.env.SENTRY_DSN at build time. No public-prefix tunnel var is injected for Angular (no bundler convention to mirror) — skip tunnel here; the SDK posts directly to the DSN host.

Vanilla JavaScript (browser)
bash
npm install @sentry/browser
ts
import * as Sentry from '@sentry/browser';

Sentry.init({
  dsn: import.meta.env.VITE_SENTRY_DSN,
  tunnel: import.meta.env.VITE_SENTRY_TUNNEL,
});
Node.js
bash
npm install @sentry/node
ts
// Must be the first import in your entrypoint.
import * as Sentry from '@sentry/node';

Sentry.init({
  dsn: process.env.SENTRY_DSN,
  environment: process.env.NODE_ENV,
  tracesSampleRate: 1.0,
});

For Express:

ts
import express from 'express';
import * as Sentry from '@sentry/node';

const app = express();
Sentry.setupExpressErrorHandler(app);
React Native
bash
npx @sentry/wizard@latest -s -i reactNative
ts
import * as Sentry from '@sentry/react-native';

Sentry.init({
  dsn: process.env.SENTRY_DSN,
  tracesSampleRate: 1.0,
  replaysSessionSampleRate: 0.1,
  replaysOnErrorSampleRate: 1.0,
});

export default Sentry.wrap(App);
Python
bash
pip install sentry-sdk
python
import os
import sentry_sdk

sentry_sdk.init(
    dsn=os.environ["SENTRY_DSN"],
    environment=os.environ.get("ENV", "development"),
    traces_sample_rate=1.0,
    profiles_sample_rate=1.0,
)

Framework integrations:

python
# Flask
from sentry_sdk.integrations.flask import FlaskIntegration
sentry_sdk.init(dsn=os.environ["SENTRY_DSN"], integrations=[FlaskIntegration()])

# Django
from sentry_sdk.integrations.django import DjangoIntegration
sentry_sdk.init(dsn=os.environ["SENTRY_DSN"], integrations=[DjangoIntegration()])

# FastAPI
from sentry_sdk.integrations.starlette import StarletteIntegration
from sentry_sdk.integrations.fastapi import FastApiIntegration
sentry_sdk.init(
    dsn=os.environ["SENTRY_DSN"],
    integrations=[StarletteIntegration(), FastApiIntegration()],
)
Go
bash
go get github.com/getsentry/sentry-go
go
package main

import (
    "log"
    "os"
    "time"

    "github.com/getsentry/sentry-go"
)

func main() {
    err := sentry.Init(sentry.ClientOptions{
        Dsn:              os.Getenv("SENTRY_DSN"),
        TracesSampleRate: 1.0,
        Environment:      os.Getenv("ENV"),
    })
    if err != nil {
        log.Fatalf("sentry.Init: %s", err)
    }
    defer sentry.Flush(2 * time.Second)
}
Rust
bash
cargo add sentry sentry-tracing
rust
use std::env;

fn main() {
    let _guard = sentry::init((
        env::var("SENTRY_DSN").expect("SENTRY_DSN must be set"),
        sentry::ClientOptions {
            release: sentry::release_name!(),
            traces_sample_rate: 1.0,
            environment: env::var("ENV").ok().map(Into::into),
            ..Default::default()
        },
    ));

    // Your app entrypoint
}
Ruby (Rails)
bash
bundle add sentry-ruby sentry-rails
ruby
# config/initializers/sentry.rb
require "sentry-ruby"
require "sentry-rails"

Sentry.init do |config|
  config.dsn = ENV["SENTRY_DSN"]
  config.environment = ENV.fetch("RAILS_ENV", "development")
  config.traces_sample_rate = 1.0
end
Java (Spring Boot)
xml
<!-- pom.xml -->
<dependency>
  <groupId>io.sentry</groupId>
  <artifactId>sentry-spring-boot-starter-jakarta</artifactId>
  <version>7.14.0</version>
</dependency>
properties
# application.properties — Spring reads ${SENTRY_DSN} from the environment
sentry.dsn=${SENTRY_DSN}
sentry.environment=${ENV:development}
sentry.traces-sample-rate=1.0
PHP
bash
composer require sentry/sentry
php
<?php
\Sentry\init([
    'dsn' => $_ENV['SENTRY_DSN'],
    'environment' => $_ENV['APP_ENV'] ?? 'development',
    'traces_sample_rate' => 1.0,
]);

For Laravel, use sentry/sentry-laravel and configure via config/sentry.php reading env('SENTRY_DSN').

.NET (ASP.NET Core)
bash
dotnet add package Sentry.AspNetCore
csharp
// Program.cs
builder.WebHost.UseSentry(options =>
{
    options.Dsn = Environment.GetEnvironmentVariable("SENTRY_DSN");
    options.Environment = builder.Environment.EnvironmentName;
    options.TracesSampleRate = 1.0;
});
Flutter
bash
flutter pub add sentry_flutter
dart
import 'package:flutter/widgets.dart';
import 'package:sentry_flutter/sentry_flutter.dart';

Future<void> main() async {
  await SentryFlutter.init(
    (options) {
      options.dsn = const String.fromEnvironment('SENTRY_DSN');
      options.tracesSampleRate = 1.0;
    },
    appRunner: () => runApp(const MyApp()),
  );
}

Pass the DSN at build time: flutter run --dart-define=SENTRY_DSN=$SENTRY_DSN.

Capture custom errors

JavaScript / TypeScript
ts
import * as Sentry from '@sentry/react'; // or /browser, /node, /nextjs, etc.

try {
  doRiskyThing();
} catch (err) {
  Sentry.captureException(err);
}

Sentry.captureMessage('Something notable happened', 'warning');
Python
python
try:
    do_risky_thing()
except Exception as exc:
    sentry_sdk.capture_exception(exc)

sentry_sdk.capture_message("Something notable happened", level="warning")
Go
go
sentry.CaptureException(err)
sentry.CaptureMessage("Something notable happened")
Rust
rust
sentry::capture_error(&err);
sentry::capture_message("Something notable happened", sentry::Level::Warning);

Source maps (JS/TS only)

Upload source maps during CI so the Temps dashboard shows original source in stack traces.

bash
npm install --save-dev @sentry/cli
bash
sentry-cli sourcemaps inject ./dist
sentry-cli sourcemaps upload \
  --url-prefix '~/' \
  --release "$GIT_SHA" \
  ./dist

The Temps dashboard also accepts source map uploads via Error Tracking → Source Maps in the UI.

Verification

After wiring up:

  1. Throw a deliberate error from the app:
    • JS / TS: throw new Error('Temps error tracking test');
    • Python: raise Exception('Temps error tracking test')
    • Go: sentry.CaptureException(errors.New("Temps test"))
    • Rust: panic!("Temps test") (inside a handler caught by the Sentry integration)
  2. Run the app and trigger the path that throws.
  3. Open Error Tracking → Error Groups in the Temps dashboard — the error should appear within a few seconds.
  4. Confirm the stack trace and environment are populated.

Common issues

  • Nothing shows up: Verify the DSN env var is loaded and the SDK is initialized before any code that might throw. For Node, Sentry.init must be the very first import.
  • Minified stack traces: Upload source maps (see above).
  • Browser apps not reporting: Make sure the env var uses the bundler's public prefix (NEXT_PUBLIC_, VITE_, PUBLIC_) so it reaches the client bundle.
  • Events missing in production: Confirm the deployment environment sets the DSN env var — local .env files are not copied automatically.
  • Tunneled requests get 403: the tunnel endpoint checks that the request's Origin (or Referer) matches the domain it arrived on — this rejects a script sending forged events to someone else's project, but also anything proxying/rewriting the request in a way that drops or rewrites Origin. Confirm nothing between the browser and the app strips that header.
  • Tunneled requests get 404: the tunnel resolves the project from the Host header via Temps' routing table — this only works for the domain(s) actually deployed on Temps. A tunnel env var used on a domain temps doesn't serve (e.g. testing against a different environment's URL) has nowhere to resolve to.

© gotempsh, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/add-error-tracking of gotempsh/temps.

Open the folder on GitHubat commit 80aff9a

Compare with similar skills

Add Error Tracking 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.

Add Error Tracking compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Add Error Tracking this skillgotempsh/temps822—~4.2kAutomated safety check: NotesApache-2.0
React Devtoolssanity-io/sanity6.4k3 repos~2.1kAutomated safety check: PassMIT
Screenmapaleqsio/screenmap239—~7.2kAutomated safety check: PassMIT
Lunora Realtimeanolilab/lunora283—~2.4kAutomated safety check: PassCustom licence
Data Client Setupreactive/data-client2k—~2.2kAutomated safety check: PassApache-2.0
Expo Web To Nativeexpo/skills2.7k—~2.6kAutomated safety check: PassMIT

Similar skills

  • React Devtools

    sanity-io/sanity

    Official

    React DevTools CLI for AI agents. An agent skill from sanity-io/sanity.

    6.4k GitHub starsUsed in 3 repos~2.1k tokens
    MobileAuto-check passed
  • Screenmap

    aleqsio/screenmap

    Generate a visual navigation map of an Expo / React Native or NativeScript app.

    239 GitHub stars~7.2k tokensUpdated 3 days ago
    MobileAuto-check passed
  • Lunora Realtime

    anolilab/lunora

    Wires Lunora's live data into a client. An agent skill from anolilab/lunora.

    283 GitHub stars~2.4k tokensUpdated today
    MobileAuto-check passed
  • Data Client Setup

    reactive/data-client

    Install and set up @data-client/react or @data-client/vue in a project.

    2k GitHub stars~2.2k tokensUpdated today
    MobileAuto-check passed
  • Official

    Migrate an existing web React app to a native iOS/Android app with Expo.

    2.7k GitHub stars~2.6k tokensUpdated yesterday
    MobileAuto-check passed
  • Sentry SDK Setup

    getsentry/sentry-for-ai

    Official

    Set up Sentry in any language or framework. An agent skill from getsentry/sentry-for-ai.

    268 GitHub stars~1.7k tokensUpdated today
    MobileAuto-check passed

More from gotempsh/temps

All 15 skills in this repo
  • Temps

    gotempsh/temps

    Manage, deploy, operate, and instrument applications with Temps.

    822 GitHub stars~1.9k tokensUpdated today
    Auto-check passed
  • Add React Analytics

    gotempsh/temps

    Add Temps analytics to React applications with comprehensive tracking capabilities including page views, custom events, scroll tracking, engagement monitoring, session recording, and Web Vitals…

    822 GitHub stars~2.7k tokensUpdated today
    Auto-check passed
  • Temps Best Practices

    gotempsh/temps

    Best-practices reference for preparing and instrumenting applications on Temps.

    822 GitHub stars~2.9k tokensUpdated today
    Auto-check passed
  • Temps CLI

    gotempsh/temps

    Operate Temps through the pinned @temps-sdk/cli package with bunx or npx.

    822 GitHub stars~2k tokensUpdated today
    Auto-check passed
  • Temps Plugin

    gotempsh/temps

    Design, build, test, and distribute external Temps plugins with TypeScript/Bun; provide development and local-testing guidance for existing Rust plugins.

    822 GitHub stars~1.8k tokensUpdated today
    Auto-check passed
  • Add Custom Domain

    gotempsh/temps

    Add a custom domain to a Temps project and provision an automatic SSL/TLS certificate via Let's Encrypt, driven entirely from the @temps-sdk/cli CLI.

    822 GitHub stars~988 tokensUpdated today
    Auto-check passed

Categories

Questions about Add Error Tracking

What does Add Error Tracking do?

Add Temps error tracking to applications using the Sentry-compatible SDK. Add Error Tracking is an agent skill from gotempsh/temps. Add Temps error tracking to applications using the Sentry-compatible SDK.

When should I use Add Error Tracking?

Add Error Tracking fits situations like: the user wants to:; add error tracking to any app (React; wire up uncaught exception and unhandled promise rejection capture; configure session replay for errors.

How do I install Add Error Tracking in Claude Code?

Run `npx skills add gotempsh/temps --skill add-error-tracking -a claude-code`. Or copy the skill folder (skills/add-error-tracking in gotempsh/temps) into .claude/skills/add-error-tracking in your project. Claude Code loads it when a task matches its description.

How do I install Add Error Tracking in Codex?

Run `npx skills add gotempsh/temps --skill add-error-tracking -a codex`. Or copy the skill folder (skills/add-error-tracking in gotempsh/temps) into .agents/skills/add-error-tracking in your project. Codex loads it when a task matches its description.

Can I use Add Error Tracking 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 gotempsh/temps --skill add-error-tracking -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/add-error-tracking, .gemini/skills/add-error-tracking, .github/skills/add-error-tracking and .opencode/skills/add-error-tracking in your project.

What does Add Error Tracking need to run?

Going by SKILL.md and its folder, Add Error Tracking needs the command-line tools its instructions call (npm, npx, flutter, pip, go and cargo). Our summary lists: Python 3; Node.js.

Does Add Error Tracking access the network?

SKILL.md contains no URLs. Its commands use npm, npx and pip, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Add Error Tracking safe to install?

Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Add Error Tracking use?

Add Error Tracking is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Add Error Tracking use?

About 4.2k tokens (SKILL.md is roughly 17k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Add Error Tracking?

Skills that share tags, products or a category with Add Error Tracking: React Devtools (sanity-io/sanity, 6.4k stars), Screenmap (aleqsio/screenmap, 239 stars), Lunora Realtime (anolilab/lunora, 283 stars) and Data Client Setup (reactive/data-client, 2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Add Error Tracking?

gotempsh (a GitHub organization) maintains it in gotempsh/temps, which has 822 GitHub stars. The repository holds 15 skills in this directory. The repository was last updated on October 7, 2026.

Source: gotempsh/temps on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.