
getsentry / skills
✓ Official★ 844A skill package that teaches your agent 50 capabilities — every one documented and browsable below, no GitHub required · by sentry.
Each skill below is one capability this package teaches your agent. Install the whole package, or open a skill to install just that one.
Create and maintain minimal, high-signal agent documentation under 60 lines. Enforces research-backed best practices for agent-facing docs; instruction quality degrades with length Requires three core sections: Package Manager, File-Scoped Commands (per-file test/lint/typecheck), and Commit Attribution with agent identity Analyzes project structure (lock files, linter configs, CI commands, monorepo indicators) to determine what belongs in the file Uses headers and bullets only; references...
3 files — installable on its own
This skill should be used when the user asks to "create AGENTS.md", "update AGENTS.md", "maintain agent docs", "set up CLAUDE.md", or needs to keep agent…
3 files — installable on its own
Write, review, and improve blog posts for the Sentry engineering blog following Sentry's specific writing standards, voice, and quality bar. Use this skill…
1 file — installable on its own
Write, review, and improve blog posts for the Sentry engineering blog following Sentry's specific writing standards, voice, and quality bar. Use this skill…
1 file — installable on its own
Write copy following Sentry brand guidelines. Use when writing UI text, error messages, empty states, onboarding flows, 404 pages, documentation, marketing…
1 file — installable on its own
Write copy following Sentry brand guidelines. Use when writing UI text, error messages, empty states, onboarding flows, 404 pages, documentation, marketing…
1 file — installable on its own
Analyze a repository to generate recommended Claude Code settings.json permissions. Use when setting up a new project, auditing existing settings, or…
1 file — installable on its own
Analyze a repository to generate recommended Claude Code settings.json permissions. Use when setting up a new project, auditing existing settings, or…
1 file — installable on its own
Perform code reviews following Sentry engineering practices. Use when reviewing pull requests, examining code changes, or providing feedback on code quality.…
1 file — installable on its own
Code review framework following Sentry engineering practices for pull requests and code quality assessment. Covers six key problem areas: runtime errors, performance bottlenecks, side effects, backwards compatibility, ORM query issues, and security vulnerabilities Includes design assessment guidance for component interactions, architectural alignment, and requirement conflicts Requires appropriate test coverage across functional, integration, and end-to-end tests with verification of edge...
1 file — installable on its own
Code simplification and refactoring focused on clarity, consistency, and maintainability. Applies project-specific best practices from CLAUDE.md, including ES modules, explicit type annotations, and proper React patterns Eliminates unnecessary complexity through reduced nesting, clearer naming, and removal of redundant abstractions Avoids nested ternaries and overly compact solutions in favor of explicit, readable code structures Preserves all original functionality and behavior while...
1 file — installable on its own
Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Use when asked to "simplify code", "clean up…
1 file — installable on its own
Enforces Sentry conventional commit format with proper types, scopes, and issue references. Requires feature branch creation before committing to main or master; uses the create-branch skill to manage branch workflow Supports 12 commit types (feat, fix, ref, perf, docs, test, build, ci, chore, style, meta, license) with clear subject line rules and footer patterns for issue references Includes Co-Authored-By attribution for AI-generated changes and handles breaking changes with explicit...
1 file — installable on its own
ALWAYS use this skill when committing code changes — never commit directly without it. Creates commits following Sentry conventions with proper conventional…
1 file — installable on its own
Create a git branch following Sentry naming conventions. Use when asked to "create a branch", "new branch", "start a branch", "make a branch", "switch to a new…
1 file — installable on its own
Create a git branch following Sentry naming conventions. Use when asked to "create a branch", "new branch", "start a branch", "make a branch", "switch to a new…
1 file — installable on its own
Django access control and IDOR security review. Use when reviewing Django views, DRF viewsets, ORM queries, or any Python/Django code handling user…
6 files — installable on its own
Django access control and IDOR security review. Use when reviewing Django views, DRF viewsets, ORM queries, or any Python/Django code handling user…
6 files — installable on its own
Django performance code review. Use when asked to "review Django performance", "find N+1 queries", "optimize Django", "check queryset performance", "database…
2 files — installable on its own
Django performance code review. Use when asked to "review Django performance", "find N+1 queries", "optimize Django", "check queryset performance", "database…
2 files — installable on its own
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision…
1 file — installable on its own
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision…
1 file — installable on its own
Find bugs, security vulnerabilities, and code quality issues in local branch changes. Use when asked to review changes, find bugs, security review, or audit…
1 file — installable on its own
Comprehensive code review identifying bugs, security vulnerabilities, and quality issues in branch changes. Executes a structured five-phase review process: gathering the complete diff, mapping attack surfaces, running a detailed security checklist, verifying findings, and auditing coverage before conclusions Security checklist covers 11 critical areas including injection, XSS, authentication, authorization, CSRF, race conditions, session management, cryptography, information disclosure,...
1 file — installable on its own
Fetch unread GitHub notifications for open PRs where review is requested from a specified team or opened by a team member. Use when asked to "find PRs I need…
3 files — installable on its own
Fetch unread GitHub notifications for open PRs where review is requested from a specified team or opened by a team member. Use when asked to "find PRs I need…
3 files — installable on its own
GitHub Actions security review for workflow exploitation vulnerabilities. Use when asked to "review GitHub Actions", "audit workflows", "check CI security",…
11 files — installable on its own
GitHub Actions security review for workflow exploitation vulnerabilities. Use when asked to "review GitHub Actions", "audit workflows", "check CI security",…
11 files — installable on its own
Iterate on a PR until CI passes. Use when you need to fix CI failures, address review feedback, or continuously push fixes until all checks are green.…
7 files — installable on its own
Iterate on a PR until CI passes. Use when you need to fix CI failures, address review feedback, or continuously push fixes until all checks are green.…
7 files — installable on its own
Create and update pull requests following Sentry conventions. Use when opening a PR or refreshing an existing PR after material changes.
7 files — installable on its own
Create and update pull requests following Sentry conventions. Use when opening a PR or refreshing an existing PR after material changes.
7 files — installable on its own
Create data-driven presentation slides using React, Vite, and Recharts with Sentry branding. Use when asked to "create a presentation", "build slides", "make a…
6 files — installable on its own
Create data-driven presentation slides using React, Vite, and Recharts with Sentry branding. Use when asked to "create a presentation", "build slides", "make a…
6 files — installable on its own
Creates, optimizes, and iteratively refines agent prompts, system prompts, developer prompts, and reusable prompt templates. Use when asked to improve a…
8 files — installable on its own
Create, optimize, and iteratively refine agent prompts and system prompts. Use when asked to "improve a prompt", "optimize a system prompt", "rewrite an agent…
8 files — installable on its own
Analyze Sentry session replays to surface UX patterns, pain points, and user journeys for a given product area. Use when asked to "show me how users use", "day…
4 files — installable on its own
Analyze Sentry session replays to surface UX patterns, pain points, and user journeys for a given product area. Use when asked to "show me how users use", "day…
4 files — installable on its own
Systematic security code review identifying high-confidence vulnerabilities with data-flow verification. Focuses exclusively on HIGH CONFIDENCE findings: vulnerable patterns with confirmed attacker-controlled input, skipping theoretical issues and framework-mitigated code Requires codebase research before reporting: traces data flow, checks for validation/sanitization, and verifies exploitability rather than pattern-matching alone Covers 14 vulnerability categories (injection, XSS,...
25 files — installable on its own
Security code review for vulnerabilities. Use when asked to "security review", "find vulnerabilities", "check for security issues", "audit security", "OWASP…
25 files — installable on its own
Scan agent skills for security issues. Use when asked to "scan a skill",
7 files — installable on its own
Automated security scanning for agent skills before installation, detecting prompt injection, malicious code, excessive permissions, and supply chain risks. Runs static analysis via bundled Python scanner that outputs structured JSON findings with severity levels and URLs Validates SKILL.md frontmatter (required fields, tool justification, model overrides) and checks for config poisoning or scope creep in instructions Analyzes scripts for data exfiltration, reverse shells, credential theft,...
7 files — installable on its own
Create, synthesize, and iteratively improve agent skills following the Agent Skills specification. Use when asked to "create a skill", "write a skill",…
50 files — installable on its own
Create, synthesize, and iteratively improve agent skills following the Agent Skills specification. Use when asked to "create a skill", "write a skill",…
50 files — installable on its own
Take a list of projects and their related documentation, and organize them into the SRED format for submission.
4 files — installable on its own
Take a list of projects and their related documentation, and organize them into the SRED format for submission.
4 files — installable on its own
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.
1 file — installable on its own
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.
1 file — installable on its own
Python typing exclusion worker: remove assigned mypy exclusion modules in small scoped batches, fix typing issues, run validation, and produce a structured…
1 file — installable on its own
Python typing exclusion worker: remove assigned mypy exclusion modules in small scoped batches, fix typing issues, run validation, and produce a structured…
1 file — installable on its own
Sentry Skills
[!NOTE] For skills to help set up Sentry in your project or debug production issues, see https://github.com/getsentry/sentry-for-ai
Agent skills for Sentry employees, following the Agent Skills open format.
Installation
Claude Code
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.
Skills Package (skills.sh)
For agents supporting the skills.sh ecosystem:
npx skills add getsentry/skillsWorks with Claude Code, Cursor, Cline, GitHub Copilot, and other compatible agents.
Available Skills
| 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. |
Available Subagents
| Subagent | Description |
|---|---|
| code-simplifier | Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality |
| senpai | Senior engineer and technical mentor for new Sentry hires. Explains infrastructure, architecture, and engineering concepts step-by-step with references |
Contributing
Local Development
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/.
Repository Structure
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.
Creating New Skills
Skills follow the Agent Skills specification. Each skill requires a SKILL.md file with YAML frontmatter.
For repeatable skill-writer evaluation prompts, see skills/skill-writer/EVAL.md.
Skill Template
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/.
Naming Conventions
- name: 1-64 characters, lowercase alphanumeric with hyphens only
- description: Up to 1024 characters, include trigger keywords
- Keep SKILL.md under 500 lines; split longer content into reference files
Optional Fields
| 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
---Where Skills Belong
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:
- If most Sentry engineers would benefit, add it to
sentry-skills - If only a specific team needs it, create or use a domain-specific plugin
- If it only makes sense in one repo, keep it in that repo
Marketplace Structure
This 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:
- Create
plugins/<plugin-name>/.claude-plugin/plugin.json - Add skills under
plugins/<plugin-name>/skills/ - Register the plugin in
.claude-plugin/marketplace.json
Vendoring Skills
We vendor (copy) skills and agents that we use regularly into this repository rather than depending on external sources at runtime. This approach:
- Ensures consistency - Everyone on the team uses the same version of each skill
- Enables customization - We can adapt skills to Sentry-specific conventions
- Improves reliability - No external dependencies that could change or disappear
Attribution
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:
Copy & paste — that's it<!-- 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:
Copy & paste — that's itskills/vendored-skill/ ├── SKILL.md └── LICENSE # Original license text
Example: code-simplifier
The code-simplifier agent is vendored from Anthropic's official plugins. See the attribution comment at the top of the agent file.
References
License
Apache-2.0
Install the whole package (50 skills):
npx skills add https://github.com/getsentry/skillsOr install a single skill:
npx skills add https://github.com/getsentry/skills --skill <name>Pick the skill name from the Skills tab — each entry there installs independently.