sentry

Retrieve Sentry issue lists, event details, and error summaries via the Sentry API.

2|Updated Mar 29, 2026
One-click install
npx skills add https://github.com/NagyVikt/codex-plugins --skill sentry-nagyvikt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sentry
Source: https://github.com/NagyVikt/codex-plugins/tree/main/plugins/sentry/skills/sentry
Command: npx skills add https://github.com/NagyVikt/codex-plugins --skill sentry-nagyvikt

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and assets (resource) components.

What problem does it solve?

This skill eliminates the manual overhead of navigating the Sentry web dashboard by providing direct, programmatic access to production error data, issue tracking, and event details.

Core Features & Use Cases

  • Error Monitoring: Quickly list and filter unresolved production issues to identify critical system failures.
  • Event Analysis: Retrieve specific event details and stack traces to accelerate debugging and root cause analysis.
  • Use Case: When a user reports a bug, use this skill to pull the last 24 hours of error events for the production environment to determine if the issue is a known regression or a new incident.

Quick Start

Ask the assistant to list the top 20 unresolved issues for the production environment in the last 24 hours using your configured Sentry credentials.

Frequently Asked Questions about sentry

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

FAQPage Schema
How do I retrieve unresolved production errors from Sentry without using the web dashboard?

You can retrieve unresolved production errors programmatically by executing authenticated GET requests through the Sentry API. This skill filters issue lists and pulls event details directly, bypassing manual dashboard navigation for quicker observability.

Can I pull specific event stack traces to accelerate debugging and root cause analysis?

Yes, you can pull specific event stack traces to accelerate debugging. By querying the Sentry API with your project slugs, the skill retrieves detailed event data and error summaries needed for root cause analysis.

What credentials do I need to authenticate Sentry API requests for issue monitoring?

To authenticate Sentry API requests for issue monitoring, you need a valid SENTRY_AUTH_TOKEN along with your specific organization and project slugs. These credentials authorize the read-only GET requests to fetch production error data.

How do I check if a user-reported bug is a known regression or a new incident?

To check if a user-reported bug is a regression or new incident, list the top unresolved issues and error events from the last 24 hours. Querying the Sentry API for your production environment reveals matching recent errors.

Does this Sentry integration provide write access to modify issue statuses or create new alerts?

No, this integration does not provide write access to modify issue statuses or create alerts. It offers strictly read-only access to Sentry observability data, limiting actions to retrieving issue lists, event details, and error summaries.