Automated summary
This skill integrates an error tracking service (Sentry, Rollbar, Bugsnag, etc.) into an application by detecting the framework and wiring up the SDK, error boundaries, context, and breadcrumbs.
Strengths
- Detects the framework (React, Vue, Angular, Express, Fastify, Django, Flask, Rails) before proposing a tailored setup
- Covers the full lifecycle: install, error boundaries, user context, breadcrumbs, manual capture, and source maps
- Includes practical safeguards such as PII scrubbing through beforeSend and ignoreErrors filters
- Ships copy-ready code samples for Sentry on both frontend and Node.js backends
Limitations
- Code samples are mostly Sentry- and JavaScript-centric; other services and languages are only listed
- Alert configuration and performance monitoring are described briefly without detailed examples
- Assumes the user already has an account and DSN with the chosen provider
Use it when you need to add production error monitoring or instrument an existing app with Sentry or a comparable service.
Avoid it for plain local development logging or when the team has not yet picked an error tracking provider.
Security analysis
CautionThe skill is legitimate and contains no destructive, exfiltrating, or obfuscated instructions. However, it uses Bash, Write, and Edit to install dependencies and modify application code, and it configures third-party error reporting that may transmit user PII. These are normal but powerful operations, so caution is appropriate.
- •Uses Bash to run npm install, which can execute third-party package lifecycle scripts; dependencies should be pinned/verified.
- •Sends user context including email/username to a third-party error service; ensure consent and PII scrubbing, although the skill includes a beforeSend scrub example.
- •Source map upload references SENTRY_AUTH_TOKEN; ensure the token is stored as a secret and never committed.
Examples
Add Sentry error tracking to my React app: initialize the SDK with the DSN from env, wrap the app in an ErrorBoundary, and set user context after login.Set up Sentry in my Express backend with the request handler and error handler middleware, and scrub password fields before sending events.Our error tracker is flooded with browser extension and non-error promise rejection noise — add filters and ignoreErrors rules to clean it up.name: error-tracking-integrator description: Adds comprehensive error tracking with Sentry, Rollbar, or similar services including error boundaries, context, and breadcrumbs. Use when user requests error monitoring or mentions production debugging. allowed-tools: Read, Grep, Glob, Write, Edit, Bash
Error Tracking Integrator
Integrates error tracking services into applications for better production debugging and monitoring.
When to Use
- User requests error monitoring or tracking
- Setting up production error logging
- User mentions "Sentry", "error tracking", "crash reporting", or "production debugging"
Instructions
1. Detect Framework
Identify application framework:
- React, Vue, Angular (frontend)
- Express, Fastify (Node.js backend)
- Django, Flask (Python)
- Rails (Ruby)
2. Choose Error Tracking Service
Popular services:
- Sentry: Most popular, comprehensive
- Rollbar: Good for backend
- Bugsnag: Multi-platform
- Airbrake: Ruby-focused
- LogRocket: Session replay + errors
3. Install and Configure
Sentry (React example):
npm install @sentry/react
import * as Sentry from "@sentry/react";
Sentry.init({
dsn: process.env.REACT_APP_SENTRY_DSN,
environment: process.env.NODE_ENV,
tracesSampleRate: 1.0,
integrations: [
new Sentry.BrowserTracing(),
new Sentry.Replay()
],
});
Sentry (Node.js/Express):
const Sentry = require("@sentry/node");
Sentry.init({
dsn: process.env.SENTRY_DSN,
environment: process.env.NODE_ENV,
tracesSampleRate: 1.0,
});
// Request handler (first middleware)
app.use(Sentry.Handlers.requestHandler());
// Error handler (after all routes, before error middleware)
app.use(Sentry.Handlers.errorHandler());
4. Add Error Boundaries (React)
import { ErrorBoundary } from '@sentry/react';
function App() {
return (
<ErrorBoundary fallback={<ErrorFallback />}>
<YourApp />
</ErrorBoundary>
);
}
5. Add Context
User context:
Sentry.setUser({
id: user.id,
email: user.email,
username: user.username
});
Tags:
Sentry.setTag("page_locale", "en-US");
Sentry.setTag("feature_flag", "new_ui");
Context:
Sentry.setContext("order", {
id: order.id,
total: order.total,
items: order.items.length
});
6. Breadcrumbs
Track user actions leading to error:
Sentry.addBreadcrumb({
category: "auth",
message: "User logged in",
level: "info"
});
Sentry.addBreadcrumb({
category: "ui",
message: "Button clicked",
data: { buttonId: "submit-form" }
});
7. Manual Error Capture
try {
riskyOperation();
} catch (error) {
Sentry.captureException(error, {
tags: { section: "payment" },
level: "error",
extra: { orderId: order.id }
});
}
8. Filter Sensitive Data
Scrub PII:
Sentry.init({
beforeSend(event, hint) {
// Don't send if contains sensitive data
if (event.request?.data?.password) {
delete event.request.data.password;
}
return event;
},
ignoreErrors: [
// Ignore browser extension errors
/extensions\//i,
/^Non-Error promise rejection/,
]
});
9. Source Maps (Production)
Enable source maps for readable stack traces:
Webpack:
// webpack.config.js
module.exports = {
devtool: 'source-map',
plugins: [
new SentryWebpackPlugin({
org: "your-org",
project: "your-project",
authToken: process.env.SENTRY_AUTH_TOKEN,
include: "./dist",
}),
],
};
10. Alert Configuration
Set up alerts for:
- New issues
- Regression (resolved issue occurs again)
- Spike in error rate
- Critical errors (payment, auth failures)
11. Performance Monitoring
Add transaction tracking:
const transaction = Sentry.startTransaction({
name: "processOrder",
op: "task"
});
try {
await processOrder();
} finally {
transaction.finish();
}
12. Best Practices
- Environment separation: Different projects for dev/staging/prod
- Release tracking: Tag errors with release version
- Sample rates: 100% errors, lower% for performance
- Team notifications: Slack/email integration
- Issue assignment: Auto-assign to code owners
- Error grouping: Custom fingerprinting for better grouping
- Don't log sensitive data: PII, passwords, tokens
Supporting Files
templates/sentry-react.js: React integration templatetemplates/sentry-node.js: Node.js integration templatetemplates/sentry-python.py: Python integration template
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/error-tracking-integrator-mrzxur6g/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/error-tracking-integrator-mrzxur6g' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/error-tracking-integrator-mrzxur6g/download' --output '.skill-downloads/error-tracking-integrator-mrzxur6g/SKILL.md.part' && mv '.skill-downloads/error-tracking-integrator-mrzxur6g/SKILL.md.part' '.skill-downloads/error-tracking-integrator-mrzxur6g/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
Tools declared by the author (check availability in your agent): Read, Grep, Glob, Write, Edit, Bash
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/error-tracking-integrator-mrzxur6g/SKILL.md' && test -s '.skill-downloads/error-tracking-integrator-mrzxur6g/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/error-tracking-integrator' && cp -R '.skill-downloads/error-tracking-integrator-mrzxur6g' '.claude/skills/error-tracking-integrator'Cursor
test -f '.skill-downloads/error-tracking-integrator-mrzxur6g/SKILL.md' && test -s '.skill-downloads/error-tracking-integrator-mrzxur6g/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/error-tracking-integrator' && cp -R '.skill-downloads/error-tracking-integrator-mrzxur6g' '.cursor/skills/error-tracking-integrator'Codex
test -f '.skill-downloads/error-tracking-integrator-mrzxur6g/SKILL.md' && test -s '.skill-downloads/error-tracking-integrator-mrzxur6g/SKILL.md' && mkdir -p '.agents/skills' && test ! -e '.agents/skills/error-tracking-integrator' && cp -R '.skill-downloads/error-tracking-integrator-mrzxur6g' '.agents/skills/error-tracking-integrator'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/error-tracking-integrator-mrzxur6g'openskills read 'error-tracking-integrator-mrzxur6g'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/error-tracking-integrator-mrzxur6g/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
Configure a Chat Channel with SecretRefs
DevOps
Set up chat channels using non-interactive commands, with secrets only as SecretRefs. Covers gather, mutate, repair, and prove steps for reliable delivery.
Investigate ClickHouse CI Failures
DevOps
Investigate a ClickHouse CI failure end-to-end from a PR or S3 report URL. Fetches failed tests, classifies flaky vs real regression, and checks for existing issues/fixes.
Ansible PR Review
DevOps
Reviews an Ansible PR following the project's standardized process, including changelog checks, test coverage validation, and feedback tracking.