agentleFS
jara-r-kjara-r-k/claude-code-skills/examples/AGENTS.md

claude-code-skills / examples

AGENTS.md1 starsChanged 46 days agoMITView on GitHub

Adaptation templates, not ready-to-use skills. Each example is a SKILL.md with placeholders (e.g. PROJECT_PATH, APP_URL) plus a references/ directory holding the supporting template and customisation guide. Users copy an example into their own skills directory and fill in the placeholders there.

The file

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

3 rules. About 0 are common, 2 are distinctive, and 1 is 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.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Keep placeholders generic — never fill in project-specific paths, URLs, or IDs here.

    line 20
  2. Distinctive:

    Add new examples to the README Examples table.

    line 24
  3. Very specific:

    Run the local CI command from the root AGENTS.md, then /skill-compliance-checklist examples/{name}/SKILL.md (placeholder values are …

    line 28

≈ “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
<!-- Parent: ../AGENTS.md --><!-- Generated: 2026-06-30 | Updated: 2026-09-27 -->

examples/

Purpose

Adaptation templates, not ready-to-use skills. Each example is a SKILL.md with placeholders (e.g. PROJECT_PATH, APP_URL) plus a references/ directory holding the supporting template and customisation guide. Users copy an example into their own skills directory and fill in the placeholders there.

Subdirectories

DirectoryPurpose
persona-audit-pattern/Persona-driven UX audit template — discovery, verification, and fix phases via agent teams (see persona-audit-pattern/AGENTS.md)

For AI Agents

Working In This Directory

  • Keep placeholders generic — never fill in project-specific paths, URLs, or IDs here.
  • A new example needs {name}/SKILL.md plus {name}/references/ with at least a customisation guide.
  • CI validates examples/*/SKILL.md with the same hard checks as skills (frontmatter, kebab-case name, description length/angle brackets, word count). references/ files are not checked.
  • An example's frontmatter name may differ from its folder (persona-audit lives in persona-audit-pattern/); the install target directory should match name.
  • Add new examples to the README Examples table.

Testing Requirements

  • Run the local CI command from the root AGENTS.md, then /skill-compliance-checklist examples/{name}/SKILL.md (placeholder values are acceptable).
  • Confirm references/ contains the customisation guide the SKILL.md points to.

Common Patterns

  • Customisation guides are numbered steps listing what to replace.
  • Example SKILL.md files set user-invocable: true — they are invoked directly once customised.
  • Agent templates in references/ give the YAML frontmatter and the body as separate fenced blocks; join them (without the fences) to produce the .claude/agents/*.md file.

Dependencies

Internal

  • skills/skill-compliance-checklist/ — compliance audit for example SKILL.md files
<!-- MANUAL: -->

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.