sentry

Fetch and analyze Sentry issues and events via the Sentry API across organizations and projects.

1|Updated Dec 29, 2025
One-click install
npx skills add https://github.com/nunomen/claude-skills --skill sentry-nunomen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sentry
Source: https://github.com/nunomen/claude-skills/tree/main/sentry
Command: npx skills add https://github.com/nunomen/claude-skills --skill sentry-nunomen

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill fetches and analyzes Sentry data via the API to speed up debugging, triage, and investigations.

Core Features & Use Cases

  • Retrieve issue details, events, transactions, and logs to understand problems.
  • List open issues and view key metadata to triage quickly.
  • Fetch the latest event with breadcrumbs and context for rapid root-cause analysis.

Quick Start

Use the Sentry skill to fetch details for a specific issue or event, for example: fetch-issue.js 5765604106 --org myorg --project backend

Frequently Asked Questions about sentry

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

FAQPage Schema
How do I fetch and analyze Sentry issues and events for debugging?

To debug Sentry issues, fetch specific issue details and events via the Sentry API using your organization and project parameters. This retrieves key metadata, breadcrumbs, and context needed to investigate and resolve errors quickly.

What is the best way to triage open Sentry issues across multiple projects?

The best way to triage open Sentry issues across multiple projects is to query the Sentry API. By passing organization and project parameters, you retrieve key issue metadata to prioritize investigation and accelerate debugging.

Do I need an auth token to retrieve Sentry logs and transactions?

Yes, you need an auth token stored in the ~/.sentryclirc file to retrieve Sentry logs and transactions. This token authenticates API requests so you can securely fetch issue details, events, and breadcrumbs for root-cause analysis.

Can I use Sentry API data to perform root-cause analysis with breadcrumbs?

Yes, you can use Sentry API data to perform root-cause analysis with breadcrumbs. Fetching the latest event for a specific issue retrieves associated breadcrumbs and context, providing the sequence of events leading to the error for rapid investigation.

How do I resolve a specific Sentry event using command line inputs?

To resolve a specific Sentry event using command line inputs, execute a fetch script with the event or issue ID and include the --org and --project flags. This resolves the target resources and pulls the relevant debugging data from the Sentry API.

What are the limitations of automating Sentry debugging via API scripts?

Limitations of automating Sentry debugging via API scripts include the strict dependency on the ~/.sentryclirc file for authentication and the requirement to explicitly provide --org and --project inputs for every query to successfully resolve target resources.