| name | sentry |
| description | 用于只读查询 Sentry issues、events 和服务健康数据,汇总线上错误并辅助生产问题排查。 |
| zh_description | 用于只读查询 Sentry issues、events 和服务健康数据,汇总线上错误并辅助生产问题排查。 |
| version | 1.0.0 |
| author | seaworld008 |
| source | in-house |
| source_url | |
| tags | ["security", "sentry"] |
| created_at | 2026-03-04 |
| updated_at | 2026-03-20 |
| quality | 4 |
| complexity | intermediate |
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:
- Create a Sentry auth token: https://sentry.io/settings/account/api/auth-tokens/
- Create a token with read-only scopes such as
project:read, event:read, and org:read.
- Set
SENTRY_AUTH_TOKEN as an environment variable in their system.
- 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 once)
export CODEX_HOME="${CODEX_HOME:-$HOME/.codex}"
export SENTRY_API="$CODEX_HOME/skills/sentry/scripts/sentry_api.py"
User-scoped skills install under $CODEX_HOME/skills (default: ~/.codex/skills).
1) List issues (ordered by most recent)
python3 "$SENTRY_API" \
list-issues \
--org {your-org} \
--project {your-project} \
--environment prod \
--time-range 24h \
--limit 20 \
--query