agentleFS
SentryKnown publishergetsentry/sdk-skills/AGENTS.md

sdk-skills

AGENTS.md4 starsChanged 10 months agoApache-2.0View on GitHub

A collection of agent skills for managing feature development across Sentry SDKs, primarily designed for Claude Code. This repository is structured as a Claude Code plugin (see plugins/), but the skills themselves follow the open Agent Skills specification format to maintain compatibility with other tools that adopt the standard. Each skill is a directory containing a SKILL.md file with YAML frontmatter (name, description) and markdown instructions. Required: - name - kebab-case, 1-64 chars - description - up to 1024 chars,…

The file

We split this AGENTS.md into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Add YAML frontmatter (see below)

    line 18
  2. Distinctive:

    Write clear instructions in markdown

    line 19
  3. Distinctive:

    Update README.md to include the new skill in the Available Skills table

    line 20

≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
AGENTS.md

Sentry SDK Agent Skills

A collection of agent skills for managing feature development across Sentry SDKs, primarily designed for Claude Code.

This repository is structured as a Claude Code plugin (see plugins/), but the skills themselves follow the open Agent Skills specification format to maintain compatibility with other tools that adopt the standard.

Structure

plugins/sentry-sdk-skills/skills/<skill-name>/SKILL.md

Each skill is a directory containing a SKILL.md file with YAML frontmatter (name, description) and markdown instructions.

Creating a Skill

  1. Create plugins/sentry-sdk-skills/skills/<skill-name>/SKILL.md
  2. Add YAML frontmatter (see below)
  3. Write clear instructions in markdown
  4. Update README.md to include the new skill in the Available Skills table

Frontmatter

Required:

  • name - kebab-case, 1-64 chars
  • description - up to 1024 chars, include trigger keywords

Optional:

  • model - override model (sonnet, opus, haiku)
  • allowed-tools - space-delimited list of permitted tools
  • license - license name or path
  • compatibility - environment requirements (max 500 chars)
---
name: example-skill
description: What this skill does and when to use it. Include trigger keywords.
model: sonnet
allowed-tools: Read Grep Glob Bash
---

# Example Skill

Instructions for the agent.

References

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.