Native Sentry

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...

Security Scan

The skill is internally consistent: it is a read-only Sentry REST API helper that only requires a Sentry auth token and Python 3 and its code and instructions match that purpose.

Purpose & Capability

Name/description, required binaries, declared primary env (SENTRY_AUTH_TOKEN) and included Python script all align with a read-only Sentry API helper. The script only implements listing issues, fetching events, and event/issue details — exactly what the description promises.

Instruction Scope

SKILL.md instructions restrict operations to HTTP reads against the configured Sentry base URL and only reference SENTRY_AUTH_TOKEN, SENTRY_ORG, SENTRY_PROJECT and optional SENTRY_BASE_URL. The instructions and script redaction behavior are explicit. Note: the skill allows disabling redaction (--no-redact) and supports overriding the base URL, which could result in tokens/data being sent to a non-Sentry host if misconfigured; the README and SKILL.md warn about PII exposure.

Install Mechanism

This is an instruction-only skill with a bundled pure-stdlib Python script; there is no install step that downloads external code or runs package managers. No risky install URLs or extract operations are present.

Credentials

Only SENTRY_AUTH_TOKEN is required (primary credential) and is appropriate for the stated read-only purpose. Optional environment variables (SENTRY_ORG, SENTRY_PROJECT, SENTRY_BASE_URL) are used for convenience; they are not required. The requested env access is proportional to the functionality.

Persistence & Privilege

The skill does not request always:true, has no install that persists to system locations beyond its own script, and does not modify other skills or system configs. Autonomous invocation is allowed by default (platform behavior) but is not combined with other privileged requests.

Assessment

This skill appears to do exactly what it says: read-only access to Sentry via the REST API. Before installing, confirm you provide a Sentry token with only read scopes (project:read, event:read, org:read). Be cautious if you override the base URL (SENTRY_BASE_URL or --base-url) because the token will be sent to that host — only point it at trusted Sentry instances. Avoid using --no-redact in shared or logged environments because it can expose PII and stack traces. If you need a higher assurance, review the included scripts/sentry_api.py yourself (it is small and uses only stdlib networking).

Sentry (Read-only)

Read production errors and issues from Sentry.

Setup

# 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:

1. Go to https://sentry.io/settings/account/api/auth-tokens/
2. Create a token with scopes: project:read, event:read, org:read
3. 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

Script path

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"

Commands

List recent issues

python3 "$SENTRY_API" list-issues \
  --org "$SENTRY_ORG" \
  --project "$SENTRY_PROJECT" \
  --time-range 24h \
  --environment prod \
  --limit 20 \
  --query "is:unresolved"

Get issue detail

python3 "$SENTRY_API" issue-detail ISSUE_ID

Get events for an issue

python3 "$SENTRY_API" issue-events ISSUE_ID --limit 10

Get event detail (no stack traces by default)

python3 "$SENTRY_API" event-detail \
  --org "$SENTRY_ORG" \
  --project "$SENTRY_PROJECT" \
  EVENT_ID

Add --include-entries to include stack traces.

Resolve a short ID (e.g. ABC-123) to issue ID

python3 "$SENTRY_API" list-issues \
  --org "$SENTRY_ORG" \
  --project "$SENTRY_PROJECT" \
  --query "ABC-123" \
  --limit 1

Parameters

Flag	Default	Description
--org	$SENTRY_ORG	Org slug
--project	$SENTRY_PROJECT	Project slug
--time-range	24h	Stats period (e.g. 7d, 30d)
--environment	prod	Environment filter
--limit	20	Max results (max 50)
--query		Sentry search query
--base-url	https://sentry.io	For self-hosted Sentry
--no-redact		Disable PII redaction — avoid in shared/logged environments

Notes

• 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