agentleFS
Seth090502Seth090502/osanwe-public/.claude/skills/AGENTS.md

osanwe-public / skills

AGENTS.md0 starsChanged 52 days agoMITView on GitHub

Canon moved (cross-harness migration S2, 2026-08-10): skill-authoring conventions live in .agents/skills/AGENTS.md; the canonical skill sources live in .agents/skills/<name>/. Read the canon router before authoring or editing ANY skill.

The file

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

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    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. Very specific:

    Never-touch (sync neither writes nor deletes): _archive/ and this AGENTS.md.

    line 7

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

.claude/skills/ -- DERIVED tree router (Claude Code side)

Canon moved (cross-harness migration S2, 2026-08-10): skill-authoring conventions live in .agents/skills/AGENTS.md; the canonical skill sources live in .agents/skills/<name>/. Read the canon router before authoring or editing ANY skill.

  • Files here are GENERATED copies (.agents/scripts/sync.py) for Claude Code discovery. NEVER hand-edit a file carrying the GENERATED marker -- edit canon, re-run sync, commit both trees together. Consistency: python .agents/scripts/checkall.py.
  • MIGRATION WINDOW (S3, 2026-08): skills whose canon is still a legacy pointer stub remain CANONICAL HERE until their batch lands; tools/router-check.py enforces skill-tree set-equality and sync/driftcheck skip unmigrated skills.
  • Never-touch (sync neither writes nor deletes): _archive/ and this AGENTS.md. This file is a pointer router only: add skill-authoring rules to the canon rulebook, .agents/skills/AGENTS.md, not here.
  • Root invariant still binds: /gate b before building or materially extending any skill.

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.