agentleFS
preetamnathpreetamnath/agent-skills/AGENTS.md

agent-skills

AGENTS.md4 starsChanged 7 months agoMITView on GitHub

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:

    Read WRITING-GUIDE.md before authoring or editing a skill or agent.

    line 5
  2. Distinctive:

    Write skill files and other instructions for reliable AI execution: make each instruction clear, coherent, explicit, and actionable without …

    line 6
  3. Distinctive:

    Before reporting an instruction-text edit complete, invoke these skills (the lenses) in order:

    line 7
  4. Very specific:

    When updating a shared schema in references/, sync all consumers per WRITING-GUIDE.md.

    line 15
  5. Very specific:

    When a skill/agent/command is added, removed, or renamed, sync both the README.md list and .claude-plugin/plugin.json's skills array to …

    line 16
  6. Very specific:

    When a skill/agent/command's purpose changes, update its README.md description.

    line 17
  7. Very specific:

    Run scripts/validate-skills.sh once when I ask to commit.

    line 21
  8. Very specific:

    After a commit that adds or updates a skill/agent/command, offer to install the changed ones based on the instructions below:

    line 22

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

Authoring

  • Read WRITING-GUIDE.md before authoring or editing a skill or agent.
  • Write skill files and other instructions for reliable AI execution: make each instruction clear, coherent, explicit, and actionable without relying on human inference.
  • Before reporting an instruction-text edit complete, invoke these skills (the lenses) in order:
    1. On a file created this run, invoke the compress-file skill via the Skill tool.
    2. Invoke the tighten-instruction skill, then the structure-prose skill, via the Skill tool.
    3. Invoke the check-coherence skill via the Skill tool.
  • Apply a lens change only when it materially improves instruction clarity or reliable execution, has confidence ≥ 0.80, and preserves every instruction's meaning.

Sync on change

  • When updating a shared schema in references/, sync all consumers per WRITING-GUIDE.md.
  • When a skill/agent/command is added, removed, or renamed, sync both the README.md list and .claude-plugin/plugin.json's skills array to match skills/ — alphabetical order.
  • When a skill/agent/command's purpose changes, update its README.md description.

Commit & install

  • Run scripts/validate-skills.sh once when I ask to commit.
  • After a commit that adds or updates a skill/agent/command, offer to install the changed ones based on the instructions below:
TypeInstall
Skillrun npx skills add preetamnath/agent-skills --skill <changed names> (prefill the names)
Agentcopy agents/<name>.md → ~/.claude/agents/<name>.md
Commandcopy commands/<name>/<name>.md → ~/.claude/commands/<name>.md (flat — no subdir)

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.