メニュー
Sentry error tracking and performance monitoring. Use when investigating application errors, checking error frequency, managing issue status, or reviewing releases.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Pull incident context from alerting platforms (PagerDuty). Use when investigating who's on-call, incident history, alert patterns, or MTTR metrics.
Opsgenie alert management and on-call scheduling. Use for listing alerts, checking on-call, computing MTTA/MTTR, and alert fatigue analysis. Supports team and priority filtering.
Amplitude product analytics. Use when querying user events, funnels, retention, or product usage data. Provides event segmentation, user activity lookup, and annotation queries.
Google BigQuery data warehouse queries and schema inspection. Use when running SQL queries, listing datasets/tables, or inspecting table schemas in BigQuery.
MySQL/MariaDB database inspection and queries. Use when investigating table schemas, running queries, checking processlist, replication status, InnoDB engine status, or lock contention.
PostgreSQL database inspection and queries. Use when investigating table schemas, running queries, checking locks, replication status, or long-running queries.
| name | observability-sentry |
| description | Sentry error tracking and performance monitoring. Use when investigating application errors, checking error frequency, managing issue status, or reviewing releases. |
| allowed-tools | Bash(python *) |
IMPORTANT: Credentials are injected automatically by a proxy layer. Do NOT check for SENTRY_AUTH_TOKEN in environment variables - it won't be visible to you. Just run the scripts directly; authentication is handled transparently.
Configuration environment variables you CAN check (non-secret):
SENTRY_ORGANIZATION - Sentry organization slugSENTRY_PROJECT - Default Sentry project slugStart with listing issues, then drill into details.
LIST ISSUES -> GET DETAILS -> CHECK STATS -> REVIEW RELEASES
All scripts are in .claude/skills/observability-sentry/scripts/
python .claude/skills/observability-sentry/scripts/list_issues.py --project PROJECT_SLUG [--query "is:unresolved"]
# Examples:
python .claude/skills/observability-sentry/scripts/list_issues.py --project api-backend
python .claude/skills/observability-sentry/scripts/list_issues.py --project api-backend --query "is:unresolved level:error"
python .claude/skills/observability-sentry/scripts/get_issue.py --issue-id 12345678
python .claude/skills/observability-sentry/scripts/update_issue_status.py --issue-id 12345678 --status resolved
# Status options: resolved, unresolved, ignored, resolvedInNextRelease
python .claude/skills/observability-sentry/scripts/list_projects.py
python .claude/skills/observability-sentry/scripts/get_project_stats.py --project PROJECT_SLUG [--stat received] [--resolution 1h]
python .claude/skills/observability-sentry/scripts/list_releases.py --project PROJECT_SLUG [--limit 10]
is:unresolved # Status
level:error # Level
first-release:1.2.0 # Release
firstSeen:-24h # Time
assigned:user@company.com # Assignment
is:unresolved level:error firstSeen:-24h # Combined
1. list_issues.py --project api --query "is:unresolved"
2. get_issue.py --issue-id <id>
3. list_releases.py --project api
4. get_project_stats.py --project api --stat received --resolution 1h