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-skills

If 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-skills

Or run /plugin to open the plugin manager.

Skills Package (skills.sh)

For agents supporting the skills.sh ecosystem:

npx skills add getsentry/skills

Works with Claude Code, Cursor, Cline, GitHub Copilot, and other compatible agents.

Available Skills

Available Subagents

Contributing

Local Development

git clone [email protected]:getsentry/skills.git ~/sentry-skills
claude plugin marketplace add ~/sentry-skills
claude plugin install sentry-skills

If 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 file

The 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.

Create a new directory under skills/:

skills/my-skill/
├── SKILL.md
└── SPEC.md

SKILL.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 handle

SPEC.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/.

• •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

---
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:

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

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-skills

To add a new domain-specific plugin:

1. Create plugins/<plugin-name>/.claude-plugin/plugin.json
2. Add skills under plugins/<plugin-name>/skills/
3. 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

When vendoring a skill or agent from an external source, retain proper attribution:

1. Add a comment at the top of the file referencing the original source:

``markdown <!-- Based on [Original Name] by [Author/Org]: https://github.com/example/original-source --> ``

1. Include a LICENSE file in the skill directory if the original has specific licensing requirements:

`` skills/vendored-skill/ ├── SKILL.md └── LICENSE # Original license text ``

The code-simplifier agent is vendored from Anthropic's official plugins. See the attribution comment at the top of the agent file.

References

• •Agent Skills Specification
• •Sentry Engineering Practices

License

Apache-2.0