sentry

SKILL.md

Read-only Sentry API queries for production error inspection and health summaries.

Requires SENTRY_AUTH_TOKEN with read-only scopes (project:read, event:read, org:read); supports optional org, project, and base URL environment variables

Core commands: list unresolved issues, fetch issue details, retrieve events for an issue, and inspect individual event data with automatic PII redaction

Defaults to 24-hour time range, production environment, and 20-result limit (max 50); supports pagination and optional search queries

Built-in Python script handles API pagination, transient error retries, and deterministic GET-only calls to five core Sentry endpoints

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:

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)