sentry
Inspect Sentry issues, summarize production errors, and pull health data via the Sentry API (read-only). Use when user says "check Sentry", "what errors in production?", "summarize Sentry issues", "recent crashes", or "production error report". Requires SENTRY_AUTH_TOKEN. Do NOT use for setting up Sentry SDK, configuring alerts, or non-Sentry error monitoring.
npx skills add tech-leads-club/agent-skills --skill sentry --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Sentry (Read-only Observability) ## Quick start - 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. - Set `SENTRY_AUTH_TOKEN` as an env var. - Optional defaults: `SENTRY_ORG`, `SENTRY_PROJECT`, `SENTRY_BASE_URL`. - Defaults: org/project `{your-org}`/`{your-project}`, time range `24h`, environment `prod`, limit 20 (max 50). - Always call the Sentry API (no heuristics, no caching). If the token is missing, give the user these steps: 1. Create a Sentry auth token: <https://sentry.io/settings/account/api/auth-tokens/> 2. Create a token with read-only scopes such as `project:read`, `event:read`, and `org:read`. 3. Set `SENTRY_AUTH_TOKEN` as an environment variable in their system. 4. Offer to guide them through setting the environment variable for their OS/shell if needed. - Never ask the user to paste the full token in chat. Ask them to set it locally and confirm when ready. ## Core tasks (use bundled script) Use `scripts/sentry_api.py` for deterministic API calls. It handles pagination and retries once on transient errors. ## Skill path (set on
- Quick start
- Core tasks (use bundled script)
- Skill path (set once)
- 1) List issues (ordered by most recent)
- 2) Resolve an issue short ID to issue ID
- 3) Issue detail
- 4) Issue events
- 5) Event detail (no stack traces by default)
- API requirements
- Inputs and defaults
- Output formatting rules
- Golden test inputs
export AGENT_SKILLS_HOME="${AGENT_SKILLS_HOME:-$HOME/.agent-skills}"
export SENTRY_API="$AGENT_SKILLS_HOME/skills/sentry/scripts/sentry_api.py"
python3 "$SENTRY_API" \
list-issues \
issue-detail \
issue-events \
event-detail \
abcdef1234567890What does the sentry skill do?
Inspect Sentry issues, summarize production errors, and pull health data via the Sentry API (read-only). Use when user says "check Sentry", "what errors in production?", "summarize Sentry issues", "recent crashes", or "production error report". Requires SENTRY_AUTH_TOKEN. Do NOT use for setting up Sentry SDK, configuring alerts, or non-Sentry error monitoring.
How do I install it?
Run `npx skills add tech-leads-club/agent-skills --skill sentry --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From tech-leads-club/agent-skills, a repository with 4,983 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.