Creates and maintains concise AGENTS.md and CLAUDE.md project instruction files. Use when asked to create AGENTS.md, update AGENTS.md, maintain agent docs, set up CLAUDE.md, document repository agent conventions, or keep coding-agent instructions minimal and reference-backed.
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
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.
Define and maintain SECURITY_MODEL.md files that tell security review tools a repository's trust boundaries, invariants, reportable finding classes, and exclusions.
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 the Sentry javascript project queue by archiving non-actionable noise (third-party libs, browser quirks, transient 5xx, test traffic) with untilEscalating after user approval.
Python typing exclusion worker: remove assigned mypy exclusion modules in small scoped batches, fix typing issues, run validation, and produce a structured completion summary.
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-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/.
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.
---
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/.
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
Space-separated list of tools the skill can use. Do not use commas: Warden drops comma-suffixed names like Read,
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:
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