Labsco
openai logo

sentry

✓ Official★ 4,081

by openai · part of openai/plugins

Use when the user asks to inspect Sentry issues or events, summarize recent production errors, or pull basic Sentry health data via the Sentry API; perform read-only queries with the bundled script and require `SENTRY_AUTH_TOKEN`.

🔥🔥🔥✓ VerifiedFreeQuick setup
#git#monitoring
🧩 One of 7 skills in the openai/plugins package — works on its own, and pairs well with its siblings.

This is the playbook your agent receives when the skill activates — you don't need to read it to use the skill, but it's here to audit before installing.

Sentry (Read-only Observability)

Core tasks (use bundled script)

Use scripts/sentry_api.py for deterministic API calls. It handles pagination and retries once on transient errors.

Bundled script path

export SENTRY_API="plugins/sentry/skills/sentry/scripts/sentry_api.py"

If you are running from an installed plugin copy instead of this repo checkout, use the same skills/sentry/scripts/sentry_api.py path inside the installed plugin directory.

1) List issues (ordered by most recent)

python3 "$SENTRY_API" \
  --org {your-org} \
  --project {your-project} \
  list-issues \
  --environment prod \
  --time-range 24h \
  --limit 20 \
  --query "is:unresolved"

2) Resolve an issue short ID to issue ID

python3 "$SENTRY_API" \
  --org {your-org} \
  --project {your-project} \
  list-issues \
  --query "ABC-123" \
  --limit 1

Use the returned id for issue detail or events.

3) Issue detail

python3 "$SENTRY_API" \
  --org {your-org} \
  issue-detail \
  1234567890

4) Issue events

python3 "$SENTRY_API" \
  --org {your-org} \
  issue-events \
  1234567890 \
  --environment prod \
  --time-range 24h \
  --limit 20

5) Event detail (no stack traces by default)

python3 "$SENTRY_API" \
  --org {your-org} \
  --project {your-project} \
  event-detail \
  abcdef1234567890

Inputs and defaults

  • org_slug: default to {your-org} (required for issue detail, issue events, and event detail).
  • project_slug: default to {your-project} (required for list issues and event detail).
  • time_range: default 24h (pass as statsPeriod for list issues and issue events).
  • environment: default prod (used by list issues and issue events).
  • limit: default 20, max 50 (paginate until limit reached).
  • search_query: optional query parameter.
  • issue_short_id: resolve via list-issues query first.

Output formatting rules

  • Issue list: show title, short_id, status, first_seen, last_seen, count, environments, top_tags; order by most recent.
  • Event detail: include culprit, timestamp, environment, release, url.
  • If no results, state explicitly.
  • Redact PII in output (emails, IPs). Do not print raw stack traces.
  • Never echo auth tokens.

Golden test inputs

  • Org: {your-org}
  • Project: {your-project}
  • Issue short ID: {ABC-123}

Example prompt: “List the top 10 open issues for prod in the last 24h.” Expected: ordered list with titles, short IDs, counts, last seen.