sentry
Run read-only queries on Sentry issues and events with the sentry CLI: summarise recent production errors and basic health data.
- Kind
- Skill
- Works with
- Codex, Claude Code
- Source
- openai/skills @ 49f948faa925
- Path
- skills/.curated/sentry/SKILL.md
- License
- Apache-2.0
- Jobs
- Debugging
InstallCopy it from the source repository, or sign in and let the assistant adapt it for your project.
# Sentry (Read-only Observability) ## 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: 1. Install the Sentry CLI: `curl https://cli.sentry.dev/install -fsS | bash` 2. Authenticate: `sentry auth login` 3. 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. …