Setting the issue. One moment.
Contents
Issue No. 66Sentry · Official
getsentry /skills
Agent Skills used by the Sentry team for development.
28 chapters · 1 hour 28 minutes · 18,882 words
Agent Skills used by the Sentry team for development.
28 chapters · 1 hour 28 minutes · 18,882 words
28 chapters · 88 min
npx skills add getsentry/skills/plugin marketplace add getsentry/skills[!NOTE] For skills to help set up Sentry in your project or debug production issues, see https://github.com/getsentry/sentry-for-ai (opens in a new tab)
Agent skills for Sentry employees, following the Agent Skills (opens in a new tab) open format.
main, last pushed 8 August 2026.SKILL.md, not by matching a directory convention. One layout observed: skills/*/SKILL.md.h1 and no skipped levels:.claude-plugin/marketplace.json by Sentry, declaring 1 plugin. It is read for editorial metadata only — never as the skill index, which is always the repository tree./getsentry/skills.md, and each chapter at its own .md URL.claude plugin marketplace add getsentry/skills
claude plugin install sentry-skills@sentry-skillsIf you use claude plugin marketplace add --sparse for this repo, include skills and agents alongside .claude-plugin because the root plugin manifest loads repo-root skills/ and agents/.
Restart Claude Code after installation. Skills activate automatically when relevant.
Update:
claude plugin marketplace update
claude plugin update sentry-skills@sentry-skillsOr run /plugin to open the plugin manager.
For agents supporting the skills.sh (opens in a new tab) ecosystem:
npx skills add getsentry/skillsWorks with Claude Code, Cursor, Cline, GitHub Copilot, and other compatible agents.
| Skill | Description |
|---|---|
| agents-md | Create and maintain concise, reference-backed AGENTS.md and CLAUDE.md files. |
| blog-writing-guide | Write, review, and improve blog posts for the Sentry engineering blog following Sentry’s specific writing standards, voice, and quality bar. |
| brand-guidelines | Write copy following Sentry brand guidelines. |
| claude-settings-audit | Analyze a repository to generate recommended Claude Code settings.json permissions. |
| code-review | Perform code reviews following Sentry engineering practices. |
| code-simplifier | Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. |
| commit | ALWAYS use this skill when committing code changes — never commit directly without it. |
| create-branch | Create git branches following Sentry naming conventions. |
| django-access-review | Django access control and IDOR security review. |
| django-perf-review | Django performance code review. |
| doc-coauthoring | Guide users through a structured workflow for co-authoring documentation. |
| document-api-endpoint | Document and type a Sentry API endpoint with drf-spectacular OpenAPI schema — write/fix @extend_schema, specify response TypedDicts, type parameters, fix type drift, and promote to PUBLIC. |
| find-bugs | Find bugs, security vulnerabilities, and code quality issues in local branch changes. |
| gh-review-requests | Fetch unread GitHub notifications for open PRs where review is requested from a specified team or opened by a team member. |
| gha-security-review | GitHub Actions security review for workflow exploitation vulnerabilities. |
| iterate-pr | Iterate on a PR until CI passes and actionable review feedback is addressed. |
| presentation-creator | Create data-driven presentation slides using React, Vite, and Recharts with Sentry branding. |
| pr-link-issue | Append a GitHub issue link and its Linear ticket to the current PR’s description. |
| pr-writer | Create, refresh, and rewrite pull request titles and descriptions following Sentry conventions. |
| prompt-optimizer | Optimize prompts with evals, model-family adapters, and exact external context references. |
| replay-ux-research | Analyze Sentry session replays to surface UX patterns, pain points, and user journeys for a given product area. |
| security-review | Security code review for vulnerabilities. |
| skill-scanner | Scan agent skills for security issues. |
| skill-writer | Canonical workflow to synthesize, create, and iteratively improve agent skills for this repository. |
| sred-project-organizer | Take a list of projects and their related documentation, and organize them into the SRED format for submission. |
| sred-work-summary | Go back through the previous year of work and create a Notion doc that groups relevant links into projects that can then be documented as SRED projects. |
| triage-frontend-issues | Triage the Sentry javascript project queue by archiving non-actionable noise (third-party libs, browser quirks, transient 5xx, test traffic) with untilEscalating after user approval. |
| typing-exclusion-worker | Python typing exclusion worker: remove assigned mypy exclusion modules in small scoped batches, fix typing issues, run validation, and produce a structured completion summary. |
| Subagent | Description |
|---|---|
| code-simplifier (opens in a new tab) | Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality |
| senpai (opens in a new tab) | Senior engineer and technical mentor for new Sentry hires. Explains infrastructure, architecture, and engineering concepts step-by-step with references |
git clone git@github.com:getsentry/skills.git ~/sentry-skills
claude plugin marketplace add ~/sentry-skills
claude plugin install sentry-skillsIf you use claude plugin marketplace add --sparse for this repo, include skills and agents alongside .claude-plugin because the root plugin manifest loads repo-root skills/ and agents/.
sentry-skills/
├── .claude-plugin/
│ ├── marketplace.json # Marketplace manifest
│ └── plugin.json # Root plugin manifest for sentry-skills
├── .agents/
│ └── skills -> ../skills # Local mirror for agent tooling
├── agents/
│ ├── code-simplifier.md
│ └── senpai.md
├── skills/
│ ├── code-review/
│ │ └── SKILL.md
│ └── commit/
│ └── SKILL.md
├── AGENTS.md # Agent-facing documentation
├── CLAUDE.md # Symlink to AGENTS.md
└── README.md # This fileThe canonical skill source for the sentry-skills plugin lives at repo-root skills/.
.agents/skills mirrors that tree for local agent tooling, and the root plugin manifest loads repo-root skills/ and agents/.
New skills and materially changed skills should include a root-level SPEC.md alongside SKILL.md.
Skills follow the Agent Skills specification (opens in a new tab). Each skill requires a SKILL.md file with YAML frontmatter.
For repeatable skill-writer evaluation prompts, see skills/skill-writer/EVAL.md (opens in a new tab).
Create a new directory under skills/:
skills/my-skill/
├── SKILL.md
└── SPEC.mdSKILL.md format:
---
name: my-skill
description: A clear description of what this skill does and when to use it. Include keywords that help agents identify when this skill is relevant.
---
# My Skill Name
## Instructions
Step-by-step guidance for the agent.
## Examples
Concrete examples showing expected input/output.
## Guidelines
- Specific rules to follow
- Edge cases to handleSPEC.md format:
Use SPEC.md as the maintenance contract for the skill. It should describe intent, scope, trigger context, source/evidence model, reference architecture, evaluation expectations, known limitations, and maintenance notes. Keep runtime instructions in SKILL.md; keep source inventories in SOURCES.md; keep durable examples in references/evidence/.
| Field | Description |
|---|---|
license | License name or path to license file |
compatibility | Environment requirements (max 500 chars) |
allowed-tools | Comma-separated list of tools the skill can use |
metadata | Arbitrary key-value pairs for additional properties |
---
name: my-skill
description: What this skill does
license: Apache-2.0
allowed-tools: Read, Grep, Glob
---Skills should live in the appropriate location based on their scope:
| Scope | Location | Example |
|---|---|---|
| Global - Used across Sentry | sentry-skills plugin | commit, code-review, pr-writer |
| Domain-specific - Used by a team or domain | Dedicated plugin in this repo (e.g., infra-skills) | gcp-logs, terraform-review |
| Repo-specific - Only relevant to one repo | The repository itself (.claude/skills/) | Project-specific workflows |
When deciding where to place a skill:
sentry-skillsThis repository is a Claude Code marketplace - a collection of plugins that can be installed independently. The marketplace manifest (.claude-plugin/marketplace.json) lists all available plugins:
{
"plugins": [
{
"name": "sentry-skills",
"source": "./"
},
{ "name": "infra-skills", "source": "./plugins/infra-skills" }
]
}Marketplace entries point at a plugin source directory. That source can be a dedicated plugin directory with its own .claude-plugin/plugin.json, or repo root when the root also carries a plugin manifest. The sentry-skills entry in this repo uses repo root as its plugin source so it can keep canonical skills/ and agents/ at top level.
Users can install individual plugins:
# Install just the global skills
claude plugin install sentry-skills@sentry-skills
# Install domain-specific skills
claude plugin install infra-skills@sentry-skillsTo add a new domain-specific plugin:
plugins/<plugin-name>/.claude-plugin/plugin.jsonplugins/<plugin-name>/skills/.claude-plugin/marketplace.jsonWe vendor (copy) skills and agents that we use regularly into this repository rather than depending on external sources at runtime. This approach:
When vendoring a skill or agent from an external source, retain proper attribution:
Add a comment at the top of the file referencing the original source:
<!--
Based on [Original Name] by [Author/Org]:
https://github.com/example/original-source
-->Include a LICENSE file in the skill directory if the original has specific licensing requirements:
skills/vendored-skill/
├── SKILL.md
└── LICENSE # Original license textThe code-simplifier agent is vendored from Anthropic’s official plugins (opens in a new tab). See the attribution comment at the top of the agent file.
Apache-2.0