agentleFS
akunzaiakunzai/agent-skills/AGENTS.md

agent-skills

AGENTS.md5 starsChanged 54 days agoMITView on GitHub

This is a repository of reusable agent skills (Engineering, Memory, Media). This project uses mise for the toolchain and task runner.

The file

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

10 rules. About 0 are common, 1 is distinctive, and 9 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 9

    Very specific

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

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

    When writing a skill or plugin, or matching shell and CI style, read CONTRIBUTING.md

    line 9
  2. Very specific:

    When adding or renaming a skill, read tests/skill-catalog-sync.sh

    line 11
  3. Very specific:

    When filing or triaging an issue, read docs/agents/issue-tracker.md

    line 12
  4. Very specific:

    When opening a pull or merge request, read docs/agents/pull-request.md

    line 13
  5. Very specific:

    Before running or reporting verification, read docs/agents/verification.md

    line 14
  6. Very specific:

    When applying a triage role, read docs/agents/triage-labels.md

    line 15
  7. Very specific:

    Before exploring, read docs/agents/domain.md

    line 16
  8. Very specific:

    When changing how a plugin loads or behaves under a specific runtime, read docs/agents/harnesses.md

    line 17
  9. Very specific:

    When changing a covered skill, read docs/evals/waza.md

    line 18
  10. Distinctive:

    Prune: When adding to a file, audit the rest of it in the same pass.

    line 24

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

This is a repository of reusable agent skills (Engineering, Memory, Media).

This project uses mise for the toolchain and task runner.

Pointers

  • When writing a skill or plugin, or matching shell and CI style, read CONTRIBUTING.md
  • Gold-standard test spec: tests/agents-memory-storage.sh
  • When adding or renaming a skill, read tests/skill-catalog-sync.sh
  • When filing or triaging an issue, read docs/agents/issue-tracker.md
  • When opening a pull or merge request, read docs/agents/pull-request.md
  • Before running or reporting verification, read docs/agents/verification.md
  • When applying a triage role, read docs/agents/triage-labels.md
  • Before exploring, read docs/agents/domain.md
  • When changing how a plugin loads or behaves under a specific runtime, read docs/agents/harnesses.md
  • When changing a covered skill, read docs/evals/waza.md

Prevent Recurrence

  • Candidate: Name who hits this again, in which file, on what change. No such scenario, nothing to propose.
  • Promote: Offer the first tier that reaches them and only that one, pending confirmation — enforce it (assert/type/test) with its size quoted, else a comment at that site, else an agent-facing doc (merge an existing topic doc, else docs/agents/<topic>.md, else docs/agents/lessons-learned.md) with one backtick-path line under Pointers and one sentence on why the tiers above cannot hold it.
  • Prune: When adding to a file, audit the rest of it in the same pass. Drop entries once stale (obsolete version, now enforced, duplicated, or a transcript) — not by a fixed count.

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.