Sentry
Sentry error tracking and performance monitoring. Use for error tracking.From its SKILL.md
npx -y skills add G1Joshi/Agent-Skills --skill sentryAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 12 stars12 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.5 KB, 352 tokens by cl100k_base, as published. Nobody here has run it
Sentry
Sentry provides self-hosted and cloud-based error monitoring. In 2025, it excels at Performance Monitoring and identifying AI Model hallucinations or errors.
When to Use
- Error Tracking: "My app crashed, what is the stack trace?"
- Frontend Performance: Web Vitals monitoring (LCP, FID).
- Release Tracking: Associate errors with specific git commits/releases.
Quick Start
import * as Sentry from "@sentry/node";
Sentry.init({
dsn: "https://[email protected]/0",
tracesSampleRate: 1.0,
});
try {
myFunction();
} catch (e) {
Sentry.captureException(e);
}
Core Concepts
Issues
Aggregated groups of events. Sentry expects 1000 events of "NullPointerException" to be grouped into 1 Issue.
Releases
Tying code versions to errors. Sentry can tell you "This error started in Release v3.4".
Distributed Tracing
Connects frontend errors to backend bottlenecks.
Best Practices (2025)
Do:
- Upload Source Maps: Essential for JS/TS debugging.
- Use
ignoreErrors: Filter out noise (like "Network Error" when user is offline) in the SDK config. - Use Session Replay: Video-like reproduction of user actions leading up to an error.
Don't:
- Don't log PII: Sanitize data before sending. Sentry has scrubbers, but do it client-side too.
References
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.