Agent skill

Sentry

by tech-leads-club in tech-leads-club/agent-skills

Inspect Sentry issues, summarize production errors, and pull health data via the Sentry API (read-only).

Apache-2.0Auto-check passedDevOps & Cloud

Install Sentry

skills CLI

$ npx skills add tech-leads-club/agent-skills --skill sentry -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install tech-leads-club/agent-skills sentry --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/tech-leads-club/agent-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/'packages/skills-catalog/skills/(monitoring)/sentry' .claude/skills/sentry && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "sentry" agent skill from https://github.com/tech-leads-club/agent-skills/tree/main/packages/skills-catalog/skills/(monitoring)/sentry into .claude/skills/sentry/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sentry", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/tech-leads-club/agent-skills/tree/main/packages/skills-catalog/skills/(monitoring)/sentry

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add tech-leads-club/agent-skills --skill sentry -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install tech-leads-club/agent-skills sentry --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/tech-leads-club/agent-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/'packages/skills-catalog/skills/(monitoring)/sentry' .agents/skills/sentry && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "sentry" agent skill from https://github.com/tech-leads-club/agent-skills/tree/main/packages/skills-catalog/skills/(monitoring)/sentry into .agents/skills/sentry/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sentry", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add tech-leads-club/agent-skills --skill sentry -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install tech-leads-club/agent-skills sentry --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/tech-leads-club/agent-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/'packages/skills-catalog/skills/(monitoring)/sentry' .cursor/skills/sentry && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "sentry" agent skill from https://github.com/tech-leads-club/agent-skills/tree/main/packages/skills-catalog/skills/(monitoring)/sentry into .cursor/skills/sentry/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sentry", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/tech-leads-club/agent-skills.git --path 'packages/skills-catalog/skills/(monitoring)/sentry'

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add tech-leads-club/agent-skills --skill sentry -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install tech-leads-club/agent-skills sentry --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/tech-leads-club/agent-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/'packages/skills-catalog/skills/(monitoring)/sentry' .gemini/skills/sentry && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "sentry" agent skill from https://github.com/tech-leads-club/agent-skills/tree/main/packages/skills-catalog/skills/(monitoring)/sentry into .gemini/skills/sentry/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sentry", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install tech-leads-club/agent-skills sentry

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add tech-leads-club/agent-skills --skill sentry -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/tech-leads-club/agent-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/'packages/skills-catalog/skills/(monitoring)/sentry' .github/skills/sentry && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "sentry" agent skill from https://github.com/tech-leads-club/agent-skills/tree/main/packages/skills-catalog/skills/(monitoring)/sentry into .github/skills/sentry/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sentry", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add tech-leads-club/agent-skills --skill sentry -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install tech-leads-club/agent-skills sentry --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/tech-leads-club/agent-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/'packages/skills-catalog/skills/(monitoring)/sentry' .opencode/skills/sentry && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "sentry" agent skill from https://github.com/tech-leads-club/agent-skills/tree/main/packages/skills-catalog/skills/(monitoring)/sentry into .opencode/skills/sentry/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sentry", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: sentry
GitHub stars: 7k
Token cost: ~1k tokens
SKILL.md length: 353 words
Files: 3 (incl. scripts)
Skills in repo: 74
Repo updated: Oct 9, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

Inspect Sentry issues, summarize production errors, and pull health data via the Sentry API (read-only).

Works in 5 steps: List issues (ordered by most recent) → Resolve an issue short ID to issue ID → Issue detail → …
User says check Sentry
SKILL.md covers Quick start, Core tasks (use bundled script), Skill path (set once) and API requirements, plus 3 more sections
Runs Python scripts from its folder; calls python3; needs SENTRY_AUTH_TOKEN

What it does

Sentry is an agent skill from tech-leads-club/agent-skills. Inspect Sentry issues, summarize production errors, and pull health data via the Sentry API (read-only). Use when user says "check Sentry", "what errors in production?", "summarize Sentry issues", "recent crashes", or "production error report". Requires SENTRYAUTHTOKEN. Do NOT use for setting up Sentry SDK, configuring alerts, or non-Sentry error monitoring.

Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including scripts (for example `scripts/sentry_api.py`).

It sits in DevOps & Cloud, covering Health and fitness tracking. It works with Sentry. The repository describes itself as: The secure, validated skill registry for professional AI coding agents. Extend Antigravity, Claude Code, Cursor, Copilot and more with absolute confidence. The licence is Apache-2.0.

When your agent uses it

User says check Sentry
What errors in production?
Summarize Sentry issues
Production error report

Example prompts

“check Sentry”
“what errors in production?”
“summarize Sentry issues”
“/sentry”

Requirements

Python 3
A credential in SENTRY_AUTH_TOKEN

Workflow steps

5 steps, taken from the step headings in SKILL.md.

List issues (ordered by most recent)
Resolve an issue short ID to issue ID
Issue detail
Issue events
Event detail (no stack traces by default)

What it can do on your machine

Read from SKILL.md and the folder at commit 6df68d5. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 1 file in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
- python3
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
- sentry.io
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
- SENTRY_AUTH_TOKEN
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Sentry loads about 1k tokens when it runs. Until then it costs about 92 tokens; SKILL.md has 353 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~92
When it runs · the whole SKILL.md, loaded when a task matches: ~1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from tech-leads-club/agent-skills at commit 6df68d5, republished under its Apache-2.0 licence (© tech-leads-club). 353 words, ~1,008 tokens.

Download SKILL.mdSave it as .claude/skills/sentry/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.

name: sentry
description: Inspect Sentry issues, summarize production errors, and pull health data via the Sentry API (read-only). Use when user says "check Sentry", "what errors in production?", "summarize Sentry issues", "recent crashes", or "production error report". Requires SENTRY_AUTH_TOKEN. Do NOT use for setting up Sentry SDK, configuring alerts, or non-Sentry error monitoring.
metadata.author: github.com/openai/skills
metadata.version: 1.0.0

Sentry (Read-only Observability)

Quick start

If not already authenticated, ask the user to provide a valid SENTRY_AUTH_TOKEN (read-only scopes such as project:read, event:read) or to log in and create one before running commands.
Set SENTRY_AUTH_TOKEN as an env var.
Optional defaults: SENTRY_ORG, SENTRY_PROJECT, SENTRY_BASE_URL.
Defaults: org/project {your-org}/{your-project}, time range 24h, environment prod, limit 20 (max 50).
Always call the Sentry API (no heuristics, no caching).

If the token is missing, give the user these steps:

Create a Sentry auth token: https://sentry.io/settings/account/api/auth-tokens/
Create a token with read-only scopes such as project:read, event:read, and org:read.
Set SENTRY_AUTH_TOKEN as an environment variable in their system.
Offer to guide them through setting the environment variable for their OS/shell if needed.

Never ask the user to paste the full token in chat. Ask them to set it locally and confirm when ready.

Core tasks (use bundled script)

Use scripts/sentry_api.py for deterministic API calls. It handles pagination and retries once on transient errors.

Skill path (set once)

bash

export AGENT_SKILLS_HOME="${AGENT_SKILLS_HOME:-$HOME/.agent-skills}"
export SENTRY_API="$AGENT_SKILLS_HOME/skills/sentry/scripts/sentry_api.py"

User-scoped skills install under $AGENT_SKILLS_HOME/skills (default: ~/.agent-skills/skills).

1) List issues (ordered by most recent)

bash

python3 "$SENTRY_API" \
  list-issues \
  --org {your-org} \
  --project {your-project} \
  --environment prod \
  --time-range 24h \
  --limit 20 \
  --query "is:unresolved"

2) Resolve an issue short ID to issue ID

bash

python3 "$SENTRY_API" \
  list-issues \
  --org {your-org} \
  --project {your-project} \
  --query "ABC-123" \
  --limit 1

Use the returned id for issue detail or events.

3) Issue detail

bash

python3 "$SENTRY_API" \
  issue-detail \
  1234567890

4) Issue events

bash

python3 "$SENTRY_API" \
  issue-events \
  1234567890 \
  --limit 20

5) Event detail (no stack traces by default)

bash

python3 "$SENTRY_API" \
  event-detail \
  --org {your-org} \
  --project {your-project} \
  abcdef1234567890

Show full SKILL.md (142 more words)Show less

API requirements

Always use these endpoints (GET only):

List issues: /api/0/projects/{org_slug}/{project_slug}/issues/
Issue detail: /api/0/issues/{issue_id}/
Events for issue: /api/0/issues/{issue_id}/events/
Event detail: /api/0/projects/{org_slug}/{project_slug}/events/{event_id}/

Inputs and defaults

org_slug, project_slug: default to {your-org}/{your-project} (avoid non-prod orgs).
time_range: default 24h (pass as statsPeriod).
environment: default prod.
limit: default 20, max 50 (paginate until limit reached).
search_query: optional query parameter.
issue_short_id: resolve via list-issues query first.

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.

Files

SKILL.md and 2 other files (scripts) in packages/skills-catalog/skills/(monitoring)/sentry of tech-leads-club/agent-skills.

SKILL.md
LICENSE.txt
scripts/sentry_api.py

Open the folder on GitHubat commit 6df68d5

Compare with similar skills

Sentry next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Sentry compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Sentry this skilltech-leads-club/agent-skills	7k	—	~1k	Automated safety check: Pass	Apache-2.0	today
Sentry Miniapp SDKlizhiyao/sentry-miniapp	687	—	~5.4k	Automated safety check: Pass	MIT	today
SentryJetBrains/skills	366	2 repos	~988	Automated safety check: Pass	Apache-2.0	3 mo ago
Openai Sentrytrailofbits/skills-curated	513	—	~744	Automated safety check: Notes	CC-BY-SA-4.0	2 mo ago
Logging Observabilitygetsentry/toolkit	920	—	~2.6k	Automated safety check: Pass	Custom licence	today
Temps Best Practicesgotempsh/temps	831	—	~2.9k	Automated safety check: Pass	Apache-2.0	today

Similar skills

Sentry Miniapp SDK
lizhiyao/sentry-miniapp
Full Sentry SDK setup for Mini Programs — error monitoring, tracing, offline cache, source maps.
687 GitHub stars~5.4k tokensUpdated today
DevOps & CloudAuto-check passed
Sentry
JetBrains/skills
Official
A skill your agent uses when the user asks to inspect Sentry issues or events, summarize recent production errors, or pull basic Sentry health data via the Sentry API; perform read-only queries with…
366 GitHub starsUsed in 2 repos~988 tokens
Productivity & AutomationAuto-check passed
Openai Sentry
trailofbits/skills-curated
Official
A skill your agent uses when the user asks to inspect Sentry issues or events, summarize recent production errors, or pull basic Sentry health data via the Sentry API; perform read-only queries with…
513 GitHub stars~744 tokensUpdated 2 mo ago
Productivity & AutomationAuto-check: notes
Logging Observability
getsentry/toolkit
Official
Review code for correct logging and error handling patterns.
920 GitHub stars~2.6k tokensUpdated today
DevOps & CloudAuto-check passed
Temps Best Practices
gotempsh/temps
Best-practices reference for preparing and instrumenting applications on Temps.
831 GitHub stars~2.9k tokensUpdated today
DevOps & CloudAuto-check passed
Axiom SRE Investigator
openclaw/clawhub
Investigates incidents and production problems with hypothesis-driven debugging, queries Axiom observability data when available, and keeps secrets out of commands and output.
9.5k GitHub stars~7.1k tokensUpdated today
DevOps & CloudAuto-check passed

More from tech-leads-club/agent-skills

All 74 skills in this repo

Evolutionary Modular Architecture
tech-leads-club/agent-skills
Guides design of modular-monolith platforms with DDD, flat-by-aggregate modules, anti-corruption layers, outbox events and resilience, plus an architecture document with SVG diagrams.
7k GitHub stars~3.7k tokensUpdated today
Auto-check passed
Excalidraw Diagram Studio
tech-leads-club/agent-skills
Generates Excalidraw diagram files from plain descriptions, choosing among flowcharts, mind maps, architecture, swimlane, class, sequence and ER diagrams.
7k GitHub stars~3.6k tokensUpdated today
Auto-check passed
Mermaid Studio
tech-leads-club/agent-skills
Creates, validates and renders Mermaid diagrams to SVG, PNG or ASCII, including C4 and AWS architecture-beta, flowcharts, sequence diagrams and ERDs.
7k GitHub stars~4.6k tokensUpdated today
Auto-check passed
AWS Cloud Advisor
tech-leads-club/agent-skills
Answers AWS architecture, security and service-selection questions by searching AWS documentation through MCP tools first, then adapting advice to your stack and team.
7k GitHub stars~2.1k tokensUpdated today
Auto-check passed
Harness Eval
tech-leads-club/agent-skills
Evaluates a repository's agent harness (AGENTS.md, rules, skills) for broken paths, redundant instructions and usefulness, and stops at reports.
7k GitHub stars~3.9k tokensUpdated today
Auto-check passed
NestJS Modular Monolith Architect
tech-leads-club/agent-skills
Designs scalable NestJS modular monoliths with domain-driven design, Clean Architecture layers and optional CQRS, defining bounded contexts and strict module boundaries.
7k GitHub stars~3.9k tokensUpdated today
Auto-check passed

Works with

Sentry

Questions about Sentry

What does Sentry do?

Inspect Sentry issues, summarize production errors, and pull health data via the Sentry API (read-only). Sentry is an agent skill from tech-leads-club/agent-skills. Inspect Sentry issues, summarize production errors, and pull health data via the Sentry API (read-only).

When should I use Sentry?

Sentry fits situations like: user says check Sentry; what errors in production?; summarize Sentry issues; production error report.

How do I install Sentry in Claude Code?

Run `npx skills add tech-leads-club/agent-skills --skill sentry -a claude-code`. Or copy the skill folder (packages/skills-catalog/skills/(monitoring)/sentry in tech-leads-club/agent-skills) into .claude/skills/sentry in your project. Claude Code loads it when a task matches its description.

How do I install Sentry in Codex?

Run `npx skills add tech-leads-club/agent-skills --skill sentry -a codex`. Or copy the skill folder (packages/skills-catalog/skills/(monitoring)/sentry in tech-leads-club/agent-skills) into .agents/skills/sentry in your project. Codex loads it when a task matches its description.

Can I use Sentry in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add tech-leads-club/agent-skills --skill sentry -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/sentry, .gemini/skills/sentry, .github/skills/sentry and .opencode/skills/sentry in your project.

What does Sentry need to run?

Going by SKILL.md and its folder, Sentry needs Python for the scripts in its folder, the command-line tools its instructions call (python3) and credentials named SENTRY_AUTH_TOKEN. Our summary lists: Python 3; A credential in SENTRY_AUTH_TOKEN.

Does Sentry access the network?

SKILL.md names 1 domain. As links in the text: sentry.io. This is read from the text; nothing was executed.

Is Sentry safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Sentry use?

Sentry is published under the Apache-2.0 licence (from the LICENSE file in the skill folder). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Sentry use?

About 1k tokens (SKILL.md is roughly 4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Sentry?

Skills that share tags, products or a category with Sentry: Sentry Miniapp SDK (lizhiyao/sentry-miniapp, 687 stars), Sentry (JetBrains/skills, 366 stars), Openai Sentry (trailofbits/skills-curated, 513 stars) and Logging Observability (getsentry/toolkit, 920 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Sentry?

tech-leads-club (a GitHub organization) maintains it in tech-leads-club/agent-skills, which has 7,045 GitHub stars. The repository holds 74 skills in this directory. The repository was last updated on October 9, 2026.

Source: tech-leads-club/agent-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Sentry

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Sentry (Read-only Observability)

Quick start

Core tasks (use bundled script)

Skill path (set once)

1) List issues (ordered by most recent)

2) Resolve an issue short ID to issue ID

3) Issue detail

4) Issue events

5) Event detail (no stack traces by default)

API requirements

Inputs and defaults

Output formatting rules

Golden test inputs

Files

Compare with similar skills

Similar skills

More from tech-leads-club/agent-skills

Related

Questions about Sentry