sentry

Query Sentry APIs to list issues and retrieve event summaries read-only.

Updated Mar 17, 2026
One-click install
npx skills add https://github.com/Estom/aiflex --skill sentry-estom
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sentry
Source: https://github.com/Estom/aiflex/tree/main/skills-repo/openai-skills/sentry
Command: npx skills add https://github.com/Estom/aiflex --skill sentry-estom

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill provides a reliable, read-only way to inspect Sentry issues and events so engineers can quickly triage production errors without manually navigating the Sentry UI.

Core Features & Use Cases

  • List recent issues: Retrieve ordered lists of recent production issues with counts, timestamps, and top tags.
  • Inspect details and events: Fetch issue detail records and associated event summaries while avoiding raw stack trace exposure.
  • Safe, deterministic access: Uses a bundled Python script to call Sentry APIs with pagination, retry logic, and PII redaction, suitable for incident triage and postmortem preparation.

Quick Start

Use the sentry skill to list the top 10 open production issues for the last 24h.

Frequently Asked Questions about sentry

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

FAQPage Schema
How do I summarize Sentry errors quickly for incident triage?

To summarize Sentry errors quickly, you can query Sentry APIs in read-only mode to retrieve and summarize production issues and event details, handling pagination and PII redaction for safe incident triage.

Can I fetch Sentry issue details without exposing raw stack traces?

You can fetch issue detail records and associated event summaries while avoiding raw stack trace exposure, as the API uses PII redaction to ensure safe troubleshooting and postmortem preparation.

Do I need a Sentry auth token to list recent production issues?

You need a SENTRY_AUTH_TOKEN with read-only scopes to query Sentry APIs, ensuring deterministic access to list issues and retrieve event summaries for production org and project scopes.

What is the best way to automate Sentry error monitoring for postmortems?

The best way to automate Sentry error monitoring for postmortems is using a bundled deterministic Python script to call Sentry APIs, handling pagination, retries, and PII redaction for reliable observability issue retrieval.

Does pagination work when retrieving Sentry events through the API?

Pagination works when retrieving Sentry events through the API by using a bundled deterministic Python script that handles pagination and retries, ensuring complete retrieval of observability issues and event summaries.