agentleFS
mrzlimrzli/skills/AGENTS.md

skills

AGENTS.md0 starsChanged 6 days agoMITView on GitHub

When repository-local and user-installed skills share a name, use the repository-local copy under .agents/skills/ or .claude/skills/. When testing a skill, report the resolved SKILL.md path. After every skill change, including additions, edits, renames, and removals: The user's global agent instructions live in /home/mrzli/projects/personal/mrzli/archon/data/home/.codex/AGENTS.md, deployed to ~/.codex/AGENTS.md. Keep the skills consistent with them without depending on them, as writing-skills and maintain-skills describe. Changes to that file go to archon as a handoff.

The file

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

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

  • 3

    Very specific

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

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

    When repository-local and user-installed skills share a name, use the repository-local copy under .agents/skills/ or .claude/skills/.

    line 3
  2. Distinctive:

    After every skill change, including additions, edits, renames, and removals:

    line 5
  3. Distinctive:

    Run the repository-local tidy-docs skill with its default scope.

    line 7
  4. Very specific:

    Run bash scripts/sync-skills.sh from the repository root to synchronize discovery links in .agents/skills and .claude/skills.

    line 8
  5. Very specific:

    Add or update routing cases for the changed skills, following maintain-skills.

    line 9

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

Skill changes

When repository-local and user-installed skills share a name, use the repository-local copy under .agents/skills/ or .claude/skills/. When testing a skill, report the resolved SKILL.md path.

After every skill change, including additions, edits, renames, and removals:

  1. Run the repository-local tidy-docs skill with its default scope. Treat its cleanup edits as part of the same change. Do not invoke it recursively for its own edits.
  2. Run bash scripts/sync-skills.sh from the repository root to synchronize discovery links in .agents/skills and .claude/skills.
  3. Add or update routing cases for the changed skills, following maintain-skills. Run them once the user has installed the changes.

User's rules

The user's global agent instructions live in /home/mrzli/projects/personal/mrzli/archon/data/home/.codex/AGENTS.md, deployed to ~/.codex/AGENTS.md. Keep the skills consistent with them without depending on them, as writing-skills and maintain-skills describe. Changes to that file go to archon as a handoff.

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.