agentleFS
dgalarzadgalarza/agent-skills/AGENTS.md

agent-skills

AGENTS.md72 starsChanged 6 months agoMITView on GitHub

Contributor guide for this skills library. Codex, Cursor, and other agents that read AGENTS.md should follow this file. The marketplace name is dgalarza-agent-skills. The GitHub repository is dgalarza/agent-skills. It was renamed from dgalarza/claude-code-workflows. Do not create a repository with the old name, because that breaks GitHub's redirect. Architecture and the reasons for the layout are in ARCHITECTURE.md. Claude Code plugins are codebase-readiness, agent-ready, and engineering-skills. herdr-code-review (an engineering skill outside the bundle) and the operator utilities buffer and code-snippet stay…

  • Commits and pushes

The file

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

8 rules. About 0 are common, 2 are distinctive, and 6 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 6

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Commit messages follow conventional commits: feat:, fix:, chore:, docs:.

    line 36
  2. Very specific:

    Add or edit the skill under skills/<name>/.

    line 40
  3. Very specific:

    Commit the version bump with the change, or as chore: bump <plugin> to YYYY.MM.PATCH.

    line 64
  4. Distinctive:

    After the merge to main:

    line 65
  5. Distinctive:

    Create a GitHub release from the tag with a short summary.

    line 72
  6. Very specific:

    Create skills/<name>/SKILL.md with frontmatter and instructions.

    line 78
  7. Very specific:

    Add a short row to the matching group in README.md and INSTALL.md.

    line 80
  8. Very specific:

    Leave operator utilities out of .claude-plugin/marketplace.json.

    line 81

≈ “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

Agent Skills

Contributor guide for this skills library. Codex, Cursor, and other agents that read AGENTS.md should follow this file. The marketplace name is dgalarza-agent-skills. The GitHub repository is dgalarza/agent-skills. It was renamed from dgalarza/claude-code-workflows. Do not create a repository with the old name, because that breaks GitHub's redirect.

Architecture and the reasons for the layout are in ARCHITECTURE.md.

Repository Structure

skills/<name>/
  SKILL.md                    # Canonical skill (required)
  scripts/                    # Executable code (optional)
  references/                 # Docs loaded into context as needed (optional)
  assets/                     # Templates and files used in output (optional)
plugins/<plugin-name>/
  .claude-plugin/plugin.json  # Thin manifest: name, version, description, author
  README.md                   # User-facing plugin docs
  skills/<name>               # Symlink to ../../../skills/<name>
  tests/                      # Tests of that plugin's templates, when present
.claude-plugin/marketplace.json
.agents/skills/               # Vendored skill-creator used by CI. Not a published skill

Claude Code plugins are codebase-readiness, agent-ready, and engineering-skills. herdr-code-review (an engineering skill outside the bundle) and the operator utilities buffer and code-snippet stay under skills/ and are installed with npx skills only.

Symlinks stay inside this repository. Claude Code dereferences a symlink whose target is another directory in the same marketplace and copies that content into the plugin cache.

Key Conventions

  • Plugin versions live in plugins/<name>/.claude-plugin/plugin.json and in .claude-plugin/marketplace.json (the plugin entry and the marketplace version). Keep them in sync.
  • Versions use calendar versioning: YYYY.MM.PATCH (this consolidation is 2026.10.0). Increment PATCH for later changes in the same month.
  • SKILL.md frontmatter requires name (kebab-case, max 64 characters) and description (max 1024 characters, no angle brackets).
  • Skill instructions use imperative or infinitive form.
  • Skill steps that can run in parallel must also say what to do when the runtime has no subagents.
  • JSON files must be valid. CI checks this.
  • Commit messages follow conventional commits: feat:, fix:, chore:, docs:.

Development Workflow

  1. Add or edit the skill under skills/<name>/.
  2. For a Claude plugin, point plugins/<plugin>/skills/<name> at ../../../skills/<name> and list the plugin in .claude-plugin/marketplace.json.
  3. Validate locally: python3 .agents/skills/skill-creator/scripts/quick_validate.py skills/<name>
  4. CI validates skills and JSON on pull requests.
  5. Bump the CalVer version in both plugin.json and marketplace.json before merging behavior changes.

Releasing

Git tags for the marketplace snapshot stay YYYY.MM.DD. If more than one tag lands on the same day, append a suffix: YYYY.MM.DD.2. Plugin and marketplace versions stay YYYY.MM.PATCH.

When to Release

Cut a release when one or more of these land on main:

  • New plugin or skill added
  • New feature or language support added to an existing skill
  • Bug fix that affects skill or plugin behavior

Documentation-only changes do not need a release.

Release Checklist

  1. Bump the plugin version in plugins/<name>/.claude-plugin/plugin.json using YYYY.MM.PATCH.
  2. Set the same version on that plugin's entry and on the top-level version in .claude-plugin/marketplace.json.
  3. Commit the version bump with the change, or as chore: bump <plugin> to YYYY.MM.PATCH.
  4. After the merge to main:

    git tag YYYY.MM.DD
    git push origin YYYY.MM.DD
  5. Create a GitHub release from the tag with a short summary.

Retired plugin names stay in the marketplace renames map. Map a removed plugin to null. Map a plugin that moved into another plugin to that plugin's name. Keep old renames entries when adding new ones.

Adding a Skill

  1. Create skills/<name>/SKILL.md with frontmatter and instructions.
  2. To ship it in Claude Code, add a symlink under the right plugin and a marketplace entry.
  3. Add a short row to the matching group in README.md and INSTALL.md.
  4. Leave operator utilities out of .claude-plugin/marketplace.json.

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.