sentry

Query Sentry REST API for issues, events, and health metrics with read-only access and redacted output.

Updated Apr 14, 2026
One-click install
npx skills add https://github.com/dallay/opencode-docker --skill sentry-dallay
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sentry
Source: https://github.com/dallay/opencode-docker/tree/main/config/skills/sentry
Command: npx skills add https://github.com/dallay/opencode-docker --skill sentry-dallay

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Helps engineers rapidly inspect and summarize Sentry issues and events without manual API exploration by providing deterministic, read-only queries and formatted, redacted outputs.

Core Features & Use Cases

  • Read-only Sentry API queries: List issues, fetch issue details, retrieve events, and view event details using the Sentry REST API.
  • Deterministic, paginated retrieval: Uses a bundled Python script to handle pagination, transient retries, and per-request limits.
  • Safety and redaction: Enforces use of a SENTRY_AUTH_TOKEN, avoids echoing secrets, and redacts emails and IPs from responses.
  • Use Case: Triage recent production errors for a specific org/project and produce an ordered summary of top unresolved issues with counts and timestamps.

Quick Start

Ask the skill to list the top 20 unresolved production issues in the last 24h for your org and project.

Frequently Asked Questions about sentry

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I summarize unresolved Sentry production issues for incident triage?

To summarize Sentry issues for triage, query the Sentry REST API with a read-only auth token to list top unresolved issues, fetch details, and retrieve events within a configurable time range. The script handles paginated retrieval and formats outputs for quick inspection.

Can I retrieve Sentry events and issue details without exposing sensitive data?

Yes, Sentry event retrieval enforces safety by redacting PII such as emails and IPs from responses. The bundled Python script avoids echoing secrets and requires a SENTRY_AUTH_TOKEN with read-only scopes to ensure sensitive data is not exposed during issue inspection.

What's the best way to list recent Sentry errors for a specific organization and project?

The best way to list recent Sentry errors is using a deterministic Python script that performs paginated GET requests against the Sentry API. Specify your organization and project, set a time range, and the script will retrieve and format the top issues with counts and timestamps.

Does querying Sentry API issues require a specific authentication token scope?

Querying Sentry API issues requires a SENTRY_AUTH_TOKEN configured with read-only scopes. This token authorizes the bundled script to perform paginated GET requests for issues, events, and basic health metrics without allowing any state-changing operations.

How does the Sentry error triage script handle API pagination and transient failures?

The Sentry error triage script handles API pagination and transient failures by implementing deterministic, paginated retrieval with built-in retries and per-request limits. This ensures complete data extraction for issues and events across large result sets without dropping records.

Are there limitations to using read-only Sentry observability queries for error inspection?

Read-only Sentry observability queries are limited to retrieving issues, events, and basic health metrics via GET requests. The script cannot modify issue states, resolve errors, or write data, and it restricts output to redacted, formatted summaries to prevent secret exposure.