Verified:GitHub

sentry

Inspect Sentry issues and production errors via read-only API calls.

Updated Aug 27, 2026

Search Tags:#observability #sentry #issue triage #incident investigation #production errors #api read-only #error events

Ready to run

npx skills add https://github.com/luizgmassa/Useful-Agent-Skills --skill sentry-luizgmassa

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sentry
Source: https://github.com/luizgmassa/Useful-Agent-Skills/tree/main/skills/sentry
Command: npx skills add https://github.com/luizgmassa/Useful-Agent-Skills --skill sentry-luizgmassa

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps you quickly inspect Sentry issues and production error signals so you can understand what is failing and what events are happening now without manually navigating the Sentry UI.

Core Features & Use Cases

Issue triage and summarization: Lists unresolved issues for a time window and summarizes the most relevant recent failures by title, status, and tags.
Root-cause event inspection: Retrieves issue details and pulls recent events for a specific issue to identify the culprit and timestamps.
Operational observability (read-only): Fetches health/incident information through the Sentry API using GET requests only, with guardrails to prevent accidental configuration or alert changes.

Quick Start

Ask your AI assistant to list unresolved Sentry issues for your prod environment in the last 24 hours using the Sentry auth token set in your environment.

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 issues for my production environment?▼

To summarize unresolved Sentry issues, you can list production failures for a specified org, project, and time range. This Skill fetches issue details and recent error events via read-only Sentry API calls to help you triage crashes.

Can I investigate Sentry production errors without making accidental configuration changes?▼

Yes, you can investigate Sentry production errors safely. This Skill uses GET-only endpoints from the Sentry API, ensuring read-only access with guardrails to prevent accidental configuration or alert modifications during incident investigation.

What do I need to retrieve Sentry error events and issue details?▼

To retrieve Sentry error events, you need a SENTRY_AUTH_TOKEN with read-only scopes configured in your environment. The Skill uses this token to fetch issue details, event data, and health signals for your specified environment.

How does PII redaction work when inspecting Sentry issue details?▼

PII redaction is enforced automatically when inspecting Sentry issue details. The Skill applies redaction rules to fetched event data and prevents echoing the authentication token, ensuring sensitive information is not exposed during issue triage.

What is the best way to pull health signals and recent crashes from Sentry?▼

The best way to pull health signals is by querying the Sentry API for a specified time window and limit. This approach lists unresolved issues, retrieves related event data, and summarizes recent failures by title, status, and tags.

Are there limitations when fetching Sentry issues for incident investigation?▼

Yes, limitations include pagination capped at a predefined limit when fetching Sentry issues. The Skill supports read-only API calls for a specified org, project, and environment time range to ensure controlled data retrieval during incident investigation.