Automated summary
Reviews an existing Sentry setup to surface common SDK pitfalls and apply the corresponding fixes.
Strengths
- Concrete checklist spanning SDK initialization, capturing Error objects, beforeSend return values, DSN handling and sample rates
- Covers easily missed items such as calling finish() on transactions in try/finally and matching source map URL prefixes
- Delivers tangible output: pitfalls identified, fixes applied and configuration validated
- Also addresses alert configuration to reduce alert fatigue
Limitations
- Assumes a Sentry implementation already exists and requires access to the codebase and SDK configuration
- Does not spell out details itself: it points to external reference files (errors.md, examples.md) not included here
- Stays at the level of general SDK pitfalls, without framework- or language-specific analysis
Use it when auditing or troubleshooting an existing Sentry integration, or before a production release to avoid classic configuration mistakes.
Avoid it if you are instrumenting Sentry for the first time or writing application tracing code rather than auditing a configuration.
Security analysis
SafeThe skill only uses Read, Write, Edit, and Grep tools for reviewing and fixing Sentry configuration issues. It does not execute shell commands, make network requests, or perform destructive or exfiltrating actions. The instructions are limited to code inspection and benign edits.
No concerns found
How this analysis is madeExamples
Review our Sentry SDK configuration and list every common pitfall we are hitting, then apply the fixes.Our Sentry dashboard is missing errors even though they show up in logs — check our setup against known Sentry pitfalls.Run a Sentry best-practices review before we ship: sample rates, init order, source maps and alert thresholds.name: sentry-known-pitfalls description: | Execute common Sentry pitfalls and how to avoid them. Use when troubleshooting Sentry issues, reviewing configurations, or preventing common mistakes. Trigger with phrases like "sentry mistakes", "sentry pitfalls", "sentry common issues", "sentry anti-patterns". allowed-tools: Read, Write, Edit, Grep version: 1.0.0 license: MIT author: Jeremy Longshore jeremy@intentsolutions.io
Sentry Known Pitfalls
Prerequisites
- Existing Sentry implementation to review
- Access to SDK configuration
- Understanding of current error patterns
- Codebase access for fixes
Instructions
- Verify SDK initialization happens before app starts
- Check for single initialization point (no multiple init calls)
- Use framework-specific SDK package for your framework
- Ensure Error objects are captured (not strings)
- Verify beforeSend returns event or null explicitly
- Check DSN is in environment variables (not hardcoded)
- Review sample rates for production appropriateness
- Verify all transactions call finish() in try/finally
- Check source map URL prefix matches actual URLs
- Review alert configuration for threshold-based rules (avoid alert fatigue)
Output
- Pitfalls identified in current setup
- Fixes applied for each issue
- Configuration validated
- Best practices checklist completed
Error Handling
See {baseDir}/references/errors.md for comprehensive error handling.
Examples
See {baseDir}/references/examples.md for detailed examples.
Resources
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/sentry-known-pitfalls-mtnxbs30/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/sentry-known-pitfalls-mtnxbs30' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/sentry-known-pitfalls-mtnxbs30/download' --output '.skill-downloads/sentry-known-pitfalls-mtnxbs30/SKILL.md.part' && mv '.skill-downloads/sentry-known-pitfalls-mtnxbs30/SKILL.md.part' '.skill-downloads/sentry-known-pitfalls-mtnxbs30/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, Write, Edit, Grep
Original excerpt: Prerequisites
- Existing Sentry implementation to review
- Access to SDK configuration
- Understanding of current error patterns
- Codebase access for fixes
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/sentry-known-pitfalls-mtnxbs30/SKILL.md' && test -s '.skill-downloads/sentry-known-pitfalls-mtnxbs30/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/sentry-known-pitfalls' && cp -R '.skill-downloads/sentry-known-pitfalls-mtnxbs30' '.claude/skills/sentry-known-pitfalls'Cursor
test -f '.skill-downloads/sentry-known-pitfalls-mtnxbs30/SKILL.md' && test -s '.skill-downloads/sentry-known-pitfalls-mtnxbs30/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/sentry-known-pitfalls' && cp -R '.skill-downloads/sentry-known-pitfalls-mtnxbs30' '.cursor/skills/sentry-known-pitfalls'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/sentry-known-pitfalls-mtnxbs30'openskills read 'sentry-known-pitfalls-mtnxbs30'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/sentry-known-pitfalls-mtnxbs30/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.