Agent skill · data analytics · jeremylongshore
sentry-advanced-troubleshooting
Advanced Sentry troubleshooting for complex SDK issues, silent event
Why this skill is useful
Provides specific troubleshooting commands and systematic diagnosis paths for complex Sentry SDK issues that the AI wouldn't reliably generate on its own.
What it needs
Requires @sentry/cli installed locally. About 7k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Sentry Advanced Troubleshooting Overview This skill addresses complex Sentry issues that go beyond basic setup: events that silently drop, source maps that refuse to resolve, distributed traces with gaps between services, SDK memory leaks, conflicts with other observability libraries, and network-level DSN blocking. Each section provides a systematic diagnosis path with concrete commands and code to identify root causes. Prerequisites Sentry SDK v8 installed and initialized (see sentry-install-auth skill) Access to application logs, Sentry dashboard, and project settings Sentry CLI installed (npm install -g @sentry/cli) for source map debugging Network diagnostic tools available (curl, dig) debug: true enabled in SDK init for verbose console output during troubleshooting Instructions Step 1 — Diagnose Silently Dropped Events Events can vanish at multiple points between your code and the Sentry dashboard. Work through each layer systematically. Enable debug mode to see SDK internals: Systematic event-drop diagnosis: Check for tunnel misconfiguration: If you route events through a server-side tunnel (to bypass ad blockers), verify the tunnel endpoint proxies correctly: Step 2 — Debug Source Maps, Distributed Tracing, and Memory Leaks Source map resolution failures: Source maps break when the artifact URL stored in Sentry does not match the URL in the error's stack frame. Use sentry-cli sourcemaps explain to pinpoint the exact mismatch: Validate before uploading: Check the URL matching rule: The stack frame URL (e.g., https://example.com/static/js/main.abc123.js) must match the artifact URL (e.g., ~/static/js/main.abc123.js) after the tilde prefix substitution. If your CDN rewrites paths, the prefix must account for the rewritten path. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/sentry-advanced-troubleshooting--7af4a3