Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Read Sentry issues, events, and production errors via the Sentry REST API. Use when the user wants to inspect errors, list recent issues, get stack traces, o...
Read Sentry issues, events, and production errors via the Sentry REST API. Use when the user wants to inspect errors, list recent issues, get stack traces, o...
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
Read production errors and issues from Sentry.
# Check token is set (does not print the value) [ -n "$SENTRY_AUTH_TOKEN" ] && echo "SENTRY_AUTH_TOKEN: set" || echo "SENTRY_AUTH_TOKEN: MISSING" echo "ORG=${SENTRY_ORG:-not set}" echo "PROJECT=${SENTRY_PROJECT:-not set}" If SENTRY_AUTH_TOKEN is missing: Go to https://sentry.io/settings/account/api/auth-tokens/ Create a token with scopes: project:read, event:read, org:read Set SENTRY_AUTH_TOKEN in your environment Set optional defaults to avoid passing flags every time: export SENTRY_ORG=your-org-slug export SENTRY_PROJECT=your-project-slug
SKILL_DIR="$(python3 -c "import os; print(os.path.dirname(os.path.realpath('$0')))" 2>/dev/null || echo "$HOME/.claude/skills/sentry")" SENTRY_API="$SKILL_DIR/scripts/sentry_api.py"
python3 "$SENTRY_API" list-issues \ --org "$SENTRY_ORG" \ --project "$SENTRY_PROJECT" \ --time-range 24h \ --environment prod \ --limit 20 \ --query "is:unresolved"
python3 "$SENTRY_API" issue-detail ISSUE_ID
python3 "$SENTRY_API" issue-events ISSUE_ID --limit 10
python3 "$SENTRY_API" event-detail \ --org "$SENTRY_ORG" \ --project "$SENTRY_PROJECT" \ EVENT_ID Add --include-entries to include stack traces.
python3 "$SENTRY_API" list-issues \ --org "$SENTRY_ORG" \ --project "$SENTRY_PROJECT" \ --query "ABC-123" \ --limit 1
FlagDefaultDescription--org$SENTRY_ORGOrg slug--project$SENTRY_PROJECTProject slug--time-range24hStats period (e.g. 7d, 30d)--environmentprodEnvironment filter--limit20Max results (max 50)--querySentry search query--base-urlhttps://sentry.ioFor self-hosted Sentry--no-redactDisable PII redaction โ avoid in shared/logged environments
PII (emails, IPs) is redacted by default Stack traces are excluded from event detail by default โ add --include-entries only when you need them and trust the environment --no-redact disables PII redaction โ avoid in shared or logged environments For self-hosted Sentry, set SENTRY_BASE_URL or use --base-url
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.