domains / families / devops / sentry

sentry

combined

Use when the user asks to inspect Sentry issues or events, summarize recent production errors, or pull basic Sentry health data via the Sentry API; perform read-only queries with the bundled script and require `SENTRY_AUTH_TOKEN`. Use when the user asks to inspect Sentry issues or events, summarize recent production errors, or pull basic Sentry health data via the Sentry CLI; perform read-only queries using the `sentry` command.

When to use

• inspect Sentry issues
• inspect Sentry events
• summarize recent production errors
• pull basic Sentry health data
• list issues
• resolve issue short ID
• view issue detail
• view issue events

When not to use

• write operations
• non-read-only queries
• printing raw stack traces
• echoing auth tokens

Skill page

Conflict

Both copies describe the same read-only Sentry observability task and share output formatting, PII redaction, and golden test inputs. However, they disagree on the execution mechanism: the openai/skills copy uses the official `sentry` CLI with auto-detection and AI-powered explain/plan commands, while the Vibe-Skills copy uses a bundled Python script with explicit org/project arguments and a fixed set of API endpoints. Crowning one would hide a real alternative for environments where the CLI is unavailable or where a deterministic script is preferred.