Sentry issues and events

Reads Sentry issues and events through the sentry CLI without changing anything: recent production errors, issue and event details, AI root-cause summaries, with PII redacted. Use when you ask what is failing in production according to Sentry.

DebuggingPack: OpenAI skills120 linessentry
Author
Source
openai/skills/skills/.curated/sentry @ 49f948f
License
Apache-2.0

About this skill

What it does

The skill reads production errors from Sentry through the sentry command-line tool and changes nothing there. It lists issues, opens one by its short ID (ABC-123), pulls the issue's events and single-event details, and can run the CLI's AI root-cause analysis (sentry issue explain) and fix plan (sentry issue plan). Anything without a dedicated command goes through sentry api ... --method GET, with sentry schema to find the endpoint.

The CLI detects the organization and project from DSNs in .env files, source code, config defaults and directory names; <org>/<project> is passed only when it guesses wrong. Defaults are the last 24 hours, the production environment and 20 results, with --json --fields to keep output small. An issue list shows title, short ID, status, first and last seen, count, environments and top tags, newest first; an event shows culprit, timestamp, environment, release and URL. Emails and IPs are redacted, raw stack traces are not printed, tokens are never echoed, and the agent never asks you to paste a token into the chat.

There are no scripts: the folder holds SKILL.md, agents/openai.yaml, icons and the licence.

When to use it, and when not

Use it to answer "what broke in production since yesterday", or to study an issue and its releases before fixing it.

It does not resolve, assign or comment on issues, and it does not touch your code. Without access to a Sentry organization it has nothing to read.

How to run it

The install command below puts the folder in place. Then install the CLI with curl https://cli.sentry.dev/install -fsS | bash and log in with sentry auth login, or set SENTRY_AUTH_TOKEN; sentry auth status confirms it works. The agent picks the skill up by its description; to call it yourself:

  • Claude Code: /sentry, or ask for the skill by name.
  • Codex: $sentry.
  • Cursor: type / in the Agent chat and pick sentry.

Example: /sentry List the ten newest unresolved production issues from the last 24 hours.

OpenAI has marked openai/skills deprecated; our copy is pinned to a commit there. The sentry skill in openai/plugins is an older version that queries the API through a bundled script instead of the Sentry CLI.

How it differs from similar skills

Log triage works on raw logs and finds the first failure by request ID and timestamp; this skill starts from errors Sentry has already grouped into issues. Observability and instrumentation decides before a release what gets logged and alerted on. The Sentry pack in this catalog comes from Sentry's own repository and covers code review, security and commits; none of its skills reads Sentry data. Once the cause is clear, Root-cause debugging takes the fix.

Install

Run one command — it saves SKILL.md and the files it uses into your agent's skills folder. Claude Code and Codex pick up a new skill without a restart; if it does not show up, restart the agent.

Claude Code — macOS, Linux
curl -fsSL --create-dirs -o ~/.claude/skills/sentry/SKILL.md https://anymodel.org/en/skills/openai/sentry/SKILL.md -o ~/.claude/skills/sentry/LICENSE.txt https://anymodel.org/en/skills/openai/sentry/LICENSE.txt -o ~/.claude/skills/sentry/agents/openai.yaml https://anymodel.org/en/skills/openai/sentry/agents/openai.yaml -o ~/.claude/skills/sentry/assets/sentry-small.svg https://anymodel.org/en/skills/openai/sentry/assets/sentry-small.svg -o ~/.claude/skills/sentry/assets/sentry.png https://anymodel.org/en/skills/openai/sentry/assets/sentry.png
Codex, Cursor — macOS, Linux
curl -fsSL --create-dirs -o ~/.agents/skills/sentry/SKILL.md https://anymodel.org/en/skills/openai/sentry/SKILL.md -o ~/.agents/skills/sentry/LICENSE.txt https://anymodel.org/en/skills/openai/sentry/LICENSE.txt -o ~/.agents/skills/sentry/agents/openai.yaml https://anymodel.org/en/skills/openai/sentry/agents/openai.yaml -o ~/.agents/skills/sentry/assets/sentry-small.svg https://anymodel.org/en/skills/openai/sentry/assets/sentry-small.svg -o ~/.agents/skills/sentry/assets/sentry.png https://anymodel.org/en/skills/openai/sentry/assets/sentry.png
Claude Code — Windows PowerShell
foreach ($f in 'SKILL.md','LICENSE.txt','agents/openai.yaml','assets/sentry-small.svg','assets/sentry.png') { $p = Join-Path "$HOME\.claude\skills\sentry" $f; New-Item -ItemType Directory -Force (Split-Path $p) | Out-Null; Invoke-WebRequest "https://anymodel.org/en/skills/openai/sentry/$f" -UseBasicParsing -OutFile $p }
Codex, Cursor — Windows PowerShell
foreach ($f in 'SKILL.md','LICENSE.txt','agents/openai.yaml','assets/sentry-small.svg','assets/sentry.png') { $p = Join-Path "$HOME\.agents\skills\sentry" $f; New-Item -ItemType Directory -Force (Split-Path $p) | Out-Null; Invoke-WebRequest "https://anymodel.org/en/skills/openai/sentry/$f" -UseBasicParsing -OutFile $p }

Any other agent: save the file into its skills folder, or give it the link to the file: https://anymodel.org/en/skills/openai/sentry/SKILL.md

SKILL.md

Raw

Sentry (Read-only Observability)

Quick start

  • If not already authenticated, ask the user to run sentry auth login or set SENTRY_AUTH_TOKEN as an env var.
  • The CLI auto-detects org/project from DSNs in .env files, source code, config defaults, and directory names. Only specify <org>/<project> if auto-detection fails or picks the wrong target.
  • Defaults: time range 24h, environment production, limit 20.
  • Always use --json when processing output programmatically. Use --json --fields to select specific fields and reduce output size.
  • Use sentry schema <resource> to discover API endpoints quickly.

If the CLI is not installed, give the user these steps:

  1. Install the Sentry CLI: curl https://cli.sentry.dev/install -fsS | bash
  2. Authenticate: sentry auth login
  3. Confirm authentication: sentry auth status
  • Never ask the user to paste the full token in chat. Ask them to set it locally and confirm when ready.

Core tasks (use Sentry CLI)

Use the sentry CLI for all queries. It handles authentication, org/project detection, pagination, and retries automatically. Use --json for machine-readable output.

1) List issues (ordered by most recent)

sentry issue list \
  --query "is:unresolved environment:production" \
  --period 24h \
  --limit 20 \
  --json --fields shortId,title,priority,level,status

If auto-detection doesn't resolve org/project, pass them explicitly:

sentry issue list {your-org}/{your-project} \
  --query "is:unresolved environment:production" \
  --period 24h \
  --limit 20 \
  --json

2) Resolve an issue short ID to issue detail

sentry issue view {ABC-123} --json

Use the short ID format (e.g., ABC-123), not the numeric ID.

3) Issue detail

sentry issue view {ABC-123}

4) Issue events

sentry issue events {ABC-123} --limit 20 --json

5) Event detail

sentry event view {your-org}/{your-project}/{event_id} --json

6) AI-powered root cause analysis

sentry issue explain {ABC-123}

7) AI-powered fix plan

sentry issue plan {ABC-123}

Fallback: arbitrary API access

For endpoints not covered by dedicated CLI commands, use sentry api:

sentry api /api/0/organizations/{your-org}/ --method GET

Use sentry schema to discover available API endpoints:

sentry schema issues

Inputs and defaults

  • org_slug, project_slug: auto-detected by the CLI from DSNs, env vars, and directory names. Override with positional {your-org}/{your-project} if auto-detection fails.
  • time_range: default 24h (pass as --period 24h).
  • environment: default prod (pass as part of --query, e.g., environment:production).
  • limit: default 20 (pass as --limit).
  • search_query: optional --query parameter, uses Sentry search syntax (e.g., is:unresolved, assigned:me).
  • issue_short_id: use directly with sentry issue view.

Output formatting rules

  • Issue list: show title, short_id, status, first_seen, last_seen, count, environments, top_tags; order by most recent.
  • Event detail: include culprit, timestamp, environment, release, url.
  • If no results, state explicitly.
  • Redact PII in output (emails, IPs). Do not print raw stack traces.
  • Never echo auth tokens.

Golden test inputs

  • Org: {your-org}
  • Project: {your-project}
  • Issue short ID: {ABC-123}

Example prompt: "List the top 10 open issues for prod in the last 24h." Expected: ordered list with titles, short IDs, counts, last seen.

Connect through AnyModel API

This skill runs on whatever model your agent uses. Point Claude Code, Codex or Cursor at AnyModel to run it on Claude, GPT, Gemini and more with one key — pay per token, no subscription.

More from the pack OpenAI skills

ASP.NET Core apps

Guides the agent through current ASP.NET Core practice: choosing Blazor, Razor Pages, MVC or Minimal APIs, Program.cs and middleware order, auth, EF Core, tests and upgrades to .NET 10. Use when building, reviewing or upgrading an ASP.NET Core app.

ChatGPT Apps SDK

Builds ChatGPT apps on the Apps SDK: reads current OpenAI docs first, picks an app archetype, plans MCP tools, adapts an official example or scaffolds a Node server and widget, then tests in Developer Mode. Use when building or fixing an app inside ChatGPT.

CLI creator from API docs

Builds a durable CLI from API docs, an OpenAPI spec, curls or a script: JSON output, doctor and dry-run commands, safe auth, installed on PATH and paired with a companion skill. Use when an agent keeps hitting the same service through ad hoc calls.

Define a measurable goal

Turns a fuzzy intention into one measurable goal with a validator, scope and stop condition, then registers it via get_goal and create_goal. Use before goal-backed or long-running agent work, when "done" needs a number or a check.

Address GitHub PR comments

Fetches all comments, reviews and inline threads on the current branch's GitHub PR with a gh GraphQL script, numbers them and fixes only the ones you pick. Use when a PR has review comments to work through and you want to choose which get changed.

Fix failing GitHub Actions checks

Finds failing GitHub Actions checks on a PR with gh, pulls the logs, extracts the failure snippet and drafts a fix plan, changing code only after approval. Use when a PR's CI is red and you want the cause and a plan before any edit.

Jupyter notebooks

Creates and tidies Jupyter notebooks for experiments or tutorials from bundled templates via a stdlib script, with structure patterns and a run-top-to-bottom checklist. Use when starting a notebook or turning a messy one into something others can rerun.

Linear issues and projects

Works with Linear issues, projects and cycles through Linear's MCP server in a fixed order: setup, scope, read, then write, with sample workflows for triage, sprints and releases. Use when an agent should read or update Linear as part of a task.

Deploy to Netlify

Deploys the current project to Netlify with `npx netlify`: checks the login, links the folder to a site by Git remote or creates one, builds locally and returns a preview or production URL. Use when you want to publish a site to Netlify from your machine.

Browser automation with Playwright CLI

Drives a real browser from the terminal with playwright-cli: snapshots give element refs for clicks and typing, plus screenshots, console, network and traces, with no test files written. Use when a task needs a browser clicked through step by step.

Deploy to Render

Deploys an app to Render from a Git repo: writes and validates a render.yaml Blueprint with services, databases and secrets, or creates one service through the Render MCP server, then checks status and logs. Use when an app needs hosting on Render.

Security best-practice review

Checks Python, JavaScript/TypeScript and Go code against bundled security specs for ten frameworks, writes a report by severity with line numbers and fixes one finding at a time. Use when you explicitly ask for a security best-practice review.

Repository threat model

Writes a repository-grounded threat model: trust boundaries, assets, attacker capabilities and ranked abuse paths with mitigations, asking you to confirm key assumptions before the final file. Use when you explicitly ask to threat model a codebase.

Deploy to Vercel

Deploys a project to Vercel, as a preview unless told otherwise, through the Vercel CLI or, without an account, a bundled script that uploads the folder and returns a preview link and a claim link. Use when you want a shareable deployment link fast.

Figma MCP design context

Reads Figma frames through the Figma MCP server in a fixed order (design context, metadata, screenshot) and rebuilds them with the project's components and tokens; also covers server setup in Codex. Use when connecting Figma MCP or coding from a frame link.

Figma use_figma prerequisite

Sets the rules an agent must load before every use_figma call that runs Plugin API JavaScript in a Figma file: return values, page resets, colours, fonts, node IDs, small validated steps. Use when creating or editing anything inside a Figma file.

Implement a Figma design in code

Implements a Figma frame or component as code in your repo with 1:1 visual parity: fetches context and a screenshot, maps the output to project tokens and components, then runs a validation checklist. Use when a Figma link must become production UI.

Generate a Figma design from an app

Builds or updates a full screen in Figma from code or a description, section by section, using the file's published components, variables and styles instead of hardcoded values. Use when a page from your app should exist as a Figma screen.

Figma design system from a codebase

Builds a Figma design system library from a codebase in five supervised phases: discovery, variables and styles, page structure, components one by one, QA. Use when a product needs a Figma library that matches its code tokens and components.

Figma Code Connect components

Links published Figma components to the code components that implement them via Code Connect: finds unmapped ones, matches them in the codebase, maps only what the user approves. Use when a Figma library and its code both exist but are not linked.

Figma design system rules

Writes project rules for turning Figma designs into code into CLAUDE.md, AGENTS.md or a Cursor rules file, based on Figma's rule template and an analysis of the codebase. Use when setting up an agent for regular Figma-to-code work in a repo.

Create a new Figma file

Creates a blank Figma design file or FigJam board in your drafts, resolving the plan through whoami, and returns the file key and URL. Use when the next Figma step needs a fresh file to write into.