sentry-debugger

Diagnose Sentry errors and exceptions in production systems.

Updated Nov 23, 2025
One-click install
npx skills add https://github.com/ak-eyther/model-project --skill sentry-debugger
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sentry-debugger
Source: https://github.com/ak-eyther/model-project/tree/main/.claude/skills/sentry-debugger
Command: npx skills add https://github.com/ak-eyther/model-project --skill sentry-debugger

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires requests, and includes scripts (resource) and references (resource) components.

What problem does it solve?

The skill helps you quickly identify what failed in production, separate crashes from reasoning issues, and turn Sentry alerts into actionable debugging steps.

Core Features & Use Cases

  • Issue triage: Find unresolved errors, group them by severity, and inspect counts, timestamps, and permalinks.
  • Stacktrace analysis: Pull the latest exception details for a specific issue and review the most relevant frames.
  • Pattern hunting: Search by error type, environment, or agent context to compare database, LLM, ChromaDB, and JSON failures.
  • Use case: When an app starts failing in production, use the skill to determine whether the problem is a crash, a timeout, a database issue, or a parsing error, then narrow it to the affected agent.

Quick Start

Use the sentry-debugger skill to list unresolved production issues with a valid SENTRY_AUTH_TOKEN, then fetch a specific issue by providing SENTRY_ISSUE_ID when you need the latest stacktrace.

Frequently Asked Questions about sentry-debugger

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

FAQPage Schema
How do I diagnose unresolved Sentry errors and review production stacktraces?

Triage Sentry errors by grouping unresolved issues by severity, inspecting counts and timestamps, then pulling the latest event details for a specific issue to review the most relevant stacktrace frames.

What is the best way to triage production exceptions and separate crashes from reasoning issues?

Triage production exceptions by listing unresolved issues, grouping them by severity, and comparing error types to distinguish crashes, timeouts, database failures, and parsing errors across different agent contexts.

Do I need a Sentry authentication token to query production issues and event details?

Yes, you need a valid SENTRY_AUTH_TOKEN along with the relevant organization, project, and issue identifiers to query the Sentry API and optionally retrieve the latest event details.

Can I search Sentry errors by environment or agent context to compare database and parsing failures?

Yes, you can search Sentry errors by error type, environment, or agent context to hunt for patterns and compare database, LLM, ChromaDB, and JSON parsing failures across different production components.

How do I narrow down a production timeout or database failure to the affected agent?

Narrow down production failures by analyzing error frequency and stacktrace details for a specific issue, then searching by agent context to identify whether the problem is a crash, timeout, database issue, or parsing error.