Analyze Sentry issues, spans, crashes, and performance metrics. Use when user requests check in Sentry, asks about performance metrics and spans or asks about crash rates.
71
86%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Low
Low-risk findings worth noting
Use Sentry skill when:
The Sentry MCP server is configured in .mcp.json and gives Claude Code direct access to Sentry.
Setup (one-time per engineer): On first use, Claude Code will open a browser OAuth login to Sentry. Sign in and authorize — no manual token setup required.
Use these tools for data analysis:
| Tool | Purpose |
|---|---|
mcp__sentry__find_releases | Find release versions for scoping queries |
mcp__sentry__search_issues | Search for errors/crashes by query, project, date range |
mcp__sentry__search_events | Query raw events/spans (performance data, durations) |
mcp__sentry__search_issue_events | Get individual events for a known issue ID |
mcp__sentry__get_issue_tag_values | Inspect tag distributions (e.g. device, version) on an issue |
mcp__sentry__get_sentry_resource | Fetch a specific Sentry resource by URL/ID |
Do not use mcp__sentry__analyze_issue_with_seer — AI analysis is out of scope for this skill.
Always use:
expensifyapp0498f1e
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.