AI SummarySentry booster enables developers to inspect production errors, summarize recent issues, and pull health data from Sentry via read-only API queries. Ideal for on-call engineers and DevOps teams needing quick observability access without leaving their coding environment.
Install
Copy this and paste it into Claude Code, Cursor, or any AI assistant:
I want to install the "sentry" skill in my project. Please run this command in my terminal: # Install skill into your project (5 files) mkdir -p .claude/skills/sentry && curl --retry 3 --retry-delay 2 --retry-all-errors -o .claude/skills/sentry/SKILL.md "https://raw.githubusercontent.com/openai/skills/main/skills/.curated/sentry/SKILL.md" && curl --retry 3 --retry-delay 2 --retry-all-errors -o .claude/skills/sentry/LICENSE.txt "https://raw.githubusercontent.com/openai/skills/main/skills/.curated/sentry/LICENSE.txt" && mkdir -p .claude/skills/sentry/agents && curl --retry 3 --retry-delay 2 --retry-all-errors -o .claude/skills/sentry/agents/openai.yaml "https://raw.githubusercontent.com/openai/skills/main/skills/.curated/sentry/agents/openai.yaml" && mkdir -p .claude/skills/sentry/assets && curl --retry 3 --retry-delay 2 --retry-all-errors -o .claude/skills/sentry/assets/sentry-small.svg "https://raw.githubusercontent.com/openai/skills/main/skills/.curated/sentry/assets/sentry-small.svg" && mkdir -p .claude/skills/sentry/assets && curl --retry 3 --retry-delay 2 --retry-all-errors -o .claude/skills/sentry/assets/sentry.png "https://raw.githubusercontent.com/openai/skills/main/skills/.curated/sentry/assets/sentry.png" Then restart Claude Code (or reload the window in Cursor) so the skill is picked up.
Description
Use when the user asks to inspect Sentry issues or events, summarize recent production errors, or pull basic Sentry health data via the Sentry CLI; perform read-only queries using the `sentry` command.
Quick start
• If not already authenticated, ask the user to run sentry auth login or set SENTRY_AUTH_TOKEN as an env var. • The CLI auto-detects org/project from DSNs in .env files, source code, config defaults, and directory names. Only specify <org>/<project> if auto-detection fails or picks the wrong target. • Defaults: time range 24h, environment production, limit 20. • Always use --json when processing output programmatically. Use --json --fields to select specific fields and reduce output size. • Use sentry schema <resource> to discover API endpoints quickly. If the CLI is not installed, give the user these steps: • Install the Sentry CLI: curl https://cli.sentry.dev/install -fsS | bash • Authenticate: sentry auth login • Confirm authentication: sentry auth status • Never ask the user to paste the full token in chat. Ask them to set it locally and confirm when ready.
Core tasks (use Sentry CLI)
Use the sentry CLI for all queries. It handles authentication, org/project detection, pagination, and retries automatically. Use --json for machine-readable output.
1) List issues (ordered by most recent)
`bash sentry issue list \ --query "is:unresolved environment:production" \ --period 24h \ --limit 20 \ --json --fields shortId,title,priority,level,status ` If auto-detection doesn't resolve org/project, pass them explicitly: `bash sentry issue list {your-org}/{your-project} \ --query "is:unresolved environment:production" \ --period 24h \ --limit 20 \ --json `
2) Resolve an issue short ID to issue detail
`bash sentry issue view {ABC-123} --json ` Use the short ID format (e.g., ABC-123), not the numeric ID.
Discussion
Health Signals
My Fox Den
Community Rating
Sign in to rate this booster