sentry-common-errors
/sentry-common-errors
Execute troubleshoot common Sentry integration issues and fixes. Use when encountering Sentry errors, missing events, or configuration problems. Trigger with phrases like "sentry not working", "sentry errors missing", "fix sentry", "sentry troubleshoot".
- Author
- HelixDevelopment ↗
- Repository
- agent ↗
- Licence
- MIT
- Last repository change
- 14.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 2
No signals detected. Repository changed on 14.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Execute troubleshoot common Sentry integration issues and fixes. Use when encountering Sentry errors, missing events, or configuration problems. Trigger with phrases like "sentry not working", "sentry errors missing", "fix sentry", "sentry troubleshoot".
Triggers from the description
Original author description
Execute troubleshoot common Sentry integration issues and fixes. Use when encountering Sentry errors, missing events, or configuration problems. Trigger with phrases like "sentry not working", "sentry errors missing", "fix sentry", "sentry troubleshoot".
How it works
- Prerequisites
- Instructions
- Output
- Error Handling
- Examples
- Resources
SKILL.md preview
---
name: sentry-common-errors
description: |
Execute troubleshoot common Sentry integration issues and fixes.
Use when encountering Sentry errors, missing events,
or configuration problems.
Trigger with phrases like "sentry not working", "sentry errors missing",
"fix sentry", "sentry troubleshoot".
allowed-tools: Read, Grep, Bash(npm:*), Bash(curl:*)
version: 1.0.0
license: MIT
author: Jeremy Longshore <jeremy@intentsolutions.io>
---
# Sentry Common Errors
## Prerequisites
- Sentry SDK installed
- Debug mode enabled for troubleshooting
- Access to Sentry dashboard
- Application logs available
## Instructions
1. Enable debug mode in SDK configuration for verbose output
2. Verify DSN is set correctly in environment variables
3. Check beforeSend function returns event (not undefined)
4. Review sampling rates to ensure events are not being dropped
5. Verify source maps are uploaded with correct release version
6. Set user context after authentication for user tracking
7. Add ignoreErrors patterns for noisy errors to reduce volume
8. Enable Breadcrumbs integration with appropriate options
9. Set tracesSampleRate greater than 0 for performance monitoring
10. Run diagnostic commands to verify connectivity and capture
## Output
- Issue root cause identified
- Configuration fix applied
- Error capture verified working
- Documentation of resolution
## Error Handling
See `{baseDir}/references/errors.md` for comprehensive error handling.
## Examples
See `{baseDir}/references/examples.md` for detailed examples.
## Resources
- [Sentry Troubleshooting](https://docs.sentry.io/platforms/javascript/troubleshooting/)
- [Sentry Status](https://status.sentry.io)
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · HelixDevelopment/agent | 100 | MIT |
| jeremylongshore/tons-of-skills-marketplace | 100 | MIT |
Database snapshot: 13.11.2026 · package version fdb00169dc98 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100sentry-advanced-troubleshooting
Execute advanced Sentry troubleshooting techniques. Use when debugging complex SDK issues, missing events, source map problems, or performance anomalies. Trigger with phrases like "sentry not working", "debug sentry", "sentry events missing", "fix sentry issues". - 95sentry
Use when the user asks to inspect Sentry issues or events, summarize recent production errors, or pull basic Sentry health data via the Sentry API; perform read-only queries with the bundled script and require `SENTRY_AUTH_TOKEN`. - 100sentry-integration
Use when the user shares a Sentry URL, says \"check Sentry\", or wants to investigate production errors. Uses Sentry MCP tools for deep analysis. - 100sentry
Inspect Sentry issues, summarize production errors, and pull health data via the Sentry API (read-only). Use when user says "check Sentry", "what errors in production?", "summarize Sentry issues", "recent crashes", or "production error report". Requires SENTRY_AUTH_TOKEN. Do NOT… - 100sentry
Inspect Sentry issues or events, summarize recent production errors, or pull basic Sentry health data via the Sentry API. Perform read-only queries with the bundled script. Requires SENTRY_AUTH_TOKEN. Use when investigating production errors, checking Sentry issues, or reviewing error trends. - 100sentry
Use when the user asks to inspect Sentry issues or events, summarize recent production errors, or pull basic Sentry health data via the Sentry API; perform read-only queries with the bundled script and require `SENTRY_AUTH_TOKEN`.