Sentry Error Triage skill for Claude and Codex

Sentry Error Triage as an AI skill. It asks for Error list, Stack traces, Recent releases and 3 more, then does the rest. Free to install in Claude or Codex.

Install it once and Claude or Codex runs it for you. When your request matches, your AI loads the skill, asks for anything it is missing, and works through the template itself. Prefer to fill it in by hand? See the full prompt template.

Download the skill (.zip) · View SKILL.md

When it is used

Use when a batch of fresh production errors needs sorting into causes, deciding which are the team's own bugs and filing tickets. Do not use for setting up error monitoring or investigating a single bug in depth. Related topics: devops, coding.

What it will ask you for

• Error list (longer free text)
• Stack traces (longer free text)
• Recent releases (longer free text)
• Our code lives in (free text, e.g. "Folder names or package names")
• Release under suspicion (free text, e.g. "Version or none")
• Ticket format (choose one: Plain text, Markdown, Jira style)

How it works

1. Cluster the error list by shared failing frame or input, so each cluster stands for one cause.
2. Attach counts, affected users and first-seen timing to each cluster and relate them to the recent releases.
3. Label each cluster Ours, External or Unclear using the top in-app frame, and name the frame used.
4. Rank the Ours clusters by user impact and recency and choose the order to fix them.
5. Write one ticket per Ours cluster and one table row per External cluster explaining why it can be ignored.

What you get

A ranked table of clusters with owner label and impact, one ticket per owned cluster in the chosen format, and a short table of external noise with reasons.

What it watches out for

• Grouping by error message text, which splits one bug into five tickets and merges two different bugs that share a vague message.
• Blaming the latest release because it is the latest, when the first-seen time predates it.
• Filing tickets for browser-extension and bot errors, which burns engineering time on code the team does not control.

How to install

Claude.ai and the Claude desktop app

1. Download the skill .zip.
2. Open Settings, then Capabilities, and find Skills.
3. Choose Upload skill and select the .zip.
4. Ask Claude for help with the task. It loads the skill when your request matches.

Claude Code

1. Download the skill .zip.
2. Unzip it into ~/.claude/skills/ (or .claude/skills/ inside a project).
3. Start a new session. Claude Code loads the skill when your request matches.

Codex

1. Download the skill .zip.
2. Unzip it into ~/.agents/skills/ (or .agents/skills/ inside a project).
3. Codex picks it up on its own. Type $ and the skill name to use it, or just ask for the task.

Cursor

1. Download the Cursor rule (.mdc).
2. Save it in .cursor/rules/ inside your project.
3. Cursor's agent applies the rule when your request matches its description.

AGENTS.md (Codex, Cursor, and other coding agents)

1. Copy the AGENTS.md section.
2. Paste it into AGENTS.md at the root of your repository, creating the file if needed.
3. Coding agents that read AGENTS.md follow it when your request fits.