error-monitoring-setup
Skill0 starsChanged 3 months agoMITView on GitHub
Automated Sentry and error tracking setup for production applications. Apply automatically when the request matches; the user does not need to mention this skill.
- Reads credentials
- Installs packages
1 other project uses a version of this.
Adopted by
Most recently taken up by
- codecharmhq/claude-code-skillstheir own version, first seen May 17, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- codecharmhq/claude-code-skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository76 other files it gives its agents.
- app-store-submission-packagerSkill
- digital-product-inventorSkill
- ios-testflight-github-actionsSkill
- meta-ads-analyzerSkill
- get-to-know-a-clientSkill
- investigate-before-recommendSkill
- production-system-auditSkill
- similarweb-analyticsSkill
- stock-analysisSkill
- system-architectSkill
- autonomous-github-syncSkill
- autonomous-sync-scriptSkill
- github-gem-seekerSkill
- organize-github-reposSkill
- using-git-worktreesSkill
- brainstorm-logosSkill
- brand-driven-ux-overhaulSkill
- canvas-designSkill
- excel-generatorSkill
- frontend-designSkill
- inspirational-music-video-productionSkill
- theme-factorySkill
- video-generatorSkill
- multiplayer-game-builderSkill
- promo-code-systemSkill
- realistic-ai-persona-builderSkill
- role-based-access-controlSkill
- serverless-debuggingSkill
- vertical-expansion-blueprintSkill
- manus-mcp-configuratorSkill
- mcp-auto-recoverySkill
- mcp-builderSkill
- mcp-connector-testerSkill
- mcp-ecosystem-optimizerSkill
- voice-ai-integrationSkill
- api-endpoint-builderSkill
- database-schema-generatorSkill
- testing-frameworkSkill
- deployment-automationSkill
- github-workflow-automationSkill
- analytics-dashboardSkill
- email-system-builderSkill
- feature-flag-systemSkill
- user-authentication-systemSkill
- cron-job-schedulerSkill
- file-upload-systemSkill
- notification-systemSkill
- payment-integrationSkill
- search-implementationSkill
- debug-mining-engineSkill
- doc-coauthoringSkill
- docxSkill
- internet-skill-finderSkill
- pdfSkill
- pptxSkill
- project-handoff-ingestionSkill
- serverless-debuggingSkill
- skill-arsenal-builderSkill
- skill-creatorSkill
- skill-demo-builderSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 9 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈9
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 47
Create account (free tier available)
- Distinctive: line 215
Import at the top of your main file:
- Distinctive: line 232
Import in your main file:
- Distinctive: line 308
Verify test error appears
- Distinctive: line 309
Check stack trace and context
- Distinctive: line 331
Look for requests to sentry.io
- Distinctive: line 430
github-workflow-automation: - Add Sentry to CI/CD
- Distinctive: line 431
testing-framework: - Test error handling
- Distinctive: line 463
Create Sentry account: 5 min
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
error-monitoring-setup
Automated Sentry and error tracking setup for production applications
Overview
Automate the setup of Sentry error monitoring for Next.js, React, Node.js, and Python applications. Detects project type, installs dependencies, and configures error tracking in minutes.
Time Saved: ~45 minutes per setup
Complexity: Low
Prerequisites: Node.js/Python, Sentry account
When to Use
- Setting up error monitoring for new projects
- Adding Sentry to existing applications
- Standardizing error tracking across projects
- Deploying to production
- Improving application reliability
Supported Platforms
- Next.js - Full-stack React framework
- React - Frontend applications
- Node.js - Backend APIs and services
- Python - Flask, Django, FastAPI
Quick Start
1. Get Sentry DSN
- Go to sentry.io
- Create account (free tier available)
- Create new project
- Copy your DSN (looks like:
https://...@sentry.io/...)
2. Run Setup Script
python3 /home/ubuntu/skills/error-monitoring-setup/scripts/setup_sentry.py /path/to/project <your-dsn>3. Test Error Tracking
// Throw a test error
throw new Error("Test error - Sentry is working!");4. Check Sentry Dashboard
Visit your Sentry dashboard to see the error.
How It Works
Phase 1: Detection
- Scans project for
package.json,requirements.txt, etc. - Identifies: Next.js, React, Node.js, or Python
Phase 2: Installation
- Installs appropriate Sentry package
@sentry/nextjs,@sentry/react,@sentry/node, orsentry-sdk
Phase 3: Configuration
- Creates Sentry config files
- Sets up error tracking
- Configures performance monitoring
- Enables session replay (where applicable)
Usage Examples
Example 1: Setup Sentry for Next.js
python3 /home/ubuntu/skills/error-monitoring-setup/scripts/setup_sentry.py ~/my-nextjs-app https://abc123@sentry.io/456
# Output:
# 📁 Project: /home/ubuntu/my-nextjs-app
# 🔑 DSN: https://abc123...
# ✅ Detected project type: nextjs
# 📦 Installing Sentry package for nextjs...
# ✅ Sentry package installed
# 📝 Creating Sentry configuration...
# ✅ Created Sentry config files
# ✅ Sentry setup complete!Example 2: Setup Sentry for React
python3 /home/ubuntu/skills/error-monitoring-setup/scripts/setup_sentry.py ~/my-react-app https://abc123@sentry.io/456
# Output:
# 📁 Project: /home/ubuntu/my-react-app
# 🔑 DSN: https://abc123...
# ✅ Detected project type: react
# 📦 Installing Sentry package for react...
# ✅ Sentry package installed
# 📝 Creating Sentry configuration...
# ✅ Created Sentry config file
# ✅ Sentry setup complete!Example 3: Setup Sentry for Python
python3 /home/ubuntu/skills/error-monitoring-setup/scripts/setup_sentry.py ~/my-python-app https://abc123@sentry.io/456
# Output:
# 📁 Project: /home/ubuntu/my-python-app
# 🔑 DSN: https://abc123...
# ✅ Detected project type: python
# 📦 Installing Sentry package for python...
# ✅ Sentry package installed
# 📝 Creating Sentry configuration...
# ✅ Created Sentry config file
# ✅ Sentry setup complete!Configuration Files Created
Next.js
sentry.client.config.js- Client-side error trackingsentry.server.config.js- Server-side error trackingsentry.edge.config.js- Edge runtime error tracking
React
src/sentry.js- Browser error tracking
Node.js
sentry.js- Server error tracking
Python
sentry_config.py- Application error tracking
Features Enabled
Error Tracking ✅
- Automatic error capture
- Stack traces
- Error grouping
- User context
- Custom tags
Performance Monitoring ✅
- Transaction tracking
- Slow query detection
- API performance
- Page load times
Session Replay ✅ (Next.js/React)
- Video-like replay of user sessions
- See what users saw when errors occurred
- Privacy controls (mask sensitive data)
Integration Steps
Next.js
Automatic - Sentry config files are automatically loaded.
Test:
// pages/index.js
export default function Home() {
return (
<button onClick={() => {
throw new Error("Test error");
}}>
Test Sentry
</button>
);
}React
Import in src/index.js:
import './sentry';
import React from 'react';
import ReactDOM from 'react-dom/client';
import App from './App';
const root = ReactDOM.createRoot(document.getElementById('root'));
root.render(<App />);Node.js
Import at the top of your main file:
const Sentry = require('./sentry');
const express = require('express');
const app = express();
// Your routes...
// Error handler (must be last)
app.use(Sentry.Handlers.errorHandler());
app.listen(3000);Python
Import in your main file:
from sentry_config import *
from flask import Flask
app = Flask(__name__)
# Your routes...
if __name__ == '__main__':
app.run()Advanced Configuration
Custom Sample Rates
Edit config files to adjust:
Sentry.init({
dsn: "your-dsn",
tracesSampleRate: 0.1, // 10% of transactions (production)
replaysSessionSampleRate: 0.1, // 10% of sessions
replaysOnErrorSampleRate: 1.0, // 100% of error sessions
});User Context
Sentry.setUser({
id: user.id,
email: user.email,
username: user.username
});Custom Tags
Sentry.setTag("page", "checkout");
Sentry.setTag("feature", "payment");Custom Context
Sentry.setContext("order", {
id: "123",
total: 99.99,
items: 3
});Testing Error Tracking
Manual Test
// Throw error
throw new Error("Test error - Sentry is working!");
// Or capture manually
Sentry.captureMessage("Test message");
Sentry.captureException(new Error("Test exception"));Check Dashboard
- Go to Sentry dashboard
- Navigate to Issues
- Verify test error appears
- Check stack trace and context
Troubleshooting
Errors Not Appearing
Check DSN:
console.log(process.env.NEXT_PUBLIC_SENTRY_DSN);Verify Initialization:
console.log("Sentry initialized");
Sentry.captureMessage("Test");Check Network:
- Open browser DevTools
- Check Network tab
- Look for requests to sentry.io
Wrong Project Type Detected
Manually specify project type by editing config files.
Package Installation Failed
# Next.js/React/Node.js
npm install --save @sentry/nextjs
# Python
pip install sentry-sdkBest Practices
1. Set Appropriate Sample Rates
- Development: 100% (tracesSampleRate: 1.0)
- Production: 10-20% (tracesSampleRate: 0.1)
2. Use Environments
environment: process.env.NODE_ENV3. Track Releases
release: "my-app@1.0.0"4. Add User Context
Sentry.setUser({ id: user.id });5. Filter Sensitive Data
beforeSend(event) {
// Remove sensitive data
delete event.request?.cookies;
return event;
}6. Set Up Alerts
- Configure Slack notifications
- Set up email alerts
- Create alert rules
7. Review Regularly
- Check dashboard daily
- Triage new errors
- Track trends
- Prioritize fixes
Sentry Pricing
Free Tier
- 5,000 errors/month
- 10,000 performance units/month
- 500 replays/month
- Perfect for side projects
Team ($26/month)
- 50,000 errors/month
- 100,000 performance units/month
- 5,000 replays/month
- Good for small teams
Business ($80/month)
- 500,000 errors/month
- 1M performance units/month
- 50,000 replays/month
- For growing companies
Files
Scripts
scripts/setup_sentry.py- Automated Sentry setup
Templates
templates/sentry.client.config.js- Next.js client config
References
references/monitoring_guide.md- Complete monitoring guide
Related Skills
- deployment-automation - Deploy after setting up monitoring
- github-workflow-automation - Add Sentry to CI/CD
- testing-framework - Test error handling
Workflow
1. User creates Sentry account
2. User gets DSN from Sentry dashboard
3. User runs setup script with project path and DSN
4. Script detects project type
5. Script installs Sentry package
6. Script creates config files
7. User tests error tracking
8. Errors appear in Sentry dashboardSuccess Criteria
✅ Sentry package installed
✅ Config files created
✅ Error tracking working
✅ Errors appear in dashboard
✅ Stack traces visible
Time Savings
Manual Setup: ~45 minutes
- Create Sentry account: 5 min
- Read documentation: 10 min
- Install package: 2 min
- Configure: 15 min
- Test: 5 min
- Troubleshoot: 8 min
With This Skill: ~5 minutes
- Get DSN: 2 min
- Run script: 1 min
- Test: 2 min
Savings: ~40 minutes per setup
Future Enhancements
- Support for more platforms (Vue, Angular, Ruby, Go)
- Automatic source map upload
- Custom error boundaries
- Performance optimization suggestions
- Alert rule templates
- Integration with other monitoring tools
Created: February 10, 2026
Status: Production Ready
Tested: Next.js, React, Node.js, Python
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

