Help us improve
Share bugs, ideas, or general feedback.
From sentry
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`.
npx claudepluginhub robinebers/converted-plugins --plugin sentryHow this skill is triggered — by the user, by Claude, or both
Slash command
/sentry:sentryThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
- If not already authenticated, ask the user to provide a valid `SENTRY_AUTH_TOKEN` (read-only scopes such as `project:read`, `event:read`) or to log in and create one before running commands.
Mandates invoking relevant skills via tools before any response in coding sessions. Covers access, priorities, and adaptations for Claude Code, Copilot CLI, Gemini CLI.
Share bugs, ideas, or general feedback.
SENTRY_AUTH_TOKEN (read-only scopes such as project:read, event:read) or to log in and create one before running commands.SENTRY_AUTH_TOKEN as an env var.SENTRY_ORG, SENTRY_PROJECT, SENTRY_BASE_URL.{your-org}/{your-project}, time range 24h, environment prod, limit 20 (max 50).If the token is missing, give the user these steps:
project:read, event:read, and org:read.SENTRY_AUTH_TOKEN as an environment variable in their system.Use scripts/sentry_api.py for deterministic API calls. It handles pagination and retries once on transient errors.
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.
python3 "$SENTRY_API" \
--org {your-org} \
--project {your-project} \
list-issues \
--environment prod \
--time-range 24h \
--limit 20 \
--query "is:unresolved"
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.
python3 "$SENTRY_API" \
--org {your-org} \
issue-detail \
1234567890
python3 "$SENTRY_API" \
--org {your-org} \
issue-events \
1234567890 \
--environment prod \
--time-range 24h \
--limit 20
python3 "$SENTRY_API" \
--org {your-org} \
--project {your-project} \
event-detail \
abcdef1234567890
Always use these endpoints (GET only):
/api/0/projects/{org_slug}/{project_slug}/issues//api/0/organizations/{org_slug}/issues/{issue_id}//api/0/organizations/{org_slug}/issues/{issue_id}/events//api/0/projects/{org_slug}/{project_slug}/events/{event_id}/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.{your-org}{your-project}{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.