agentleFS
WeaverseWeaverse/.agents/AGENTS.md

.agents

AGENTS.md0 starsChanged 6 days agoMITView on GitHub

This public repository holds Weaverse's team rules, first-party skills and optional Claude Code glue. The shared instructions live in rules/weaverse-team.md; follow them when changing this repository.

The file

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

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

  • ≈1

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    Very specific

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

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

    Put it in skills/<lowercase-hyphen-name>/SKILL.md and add its folder to the .gitignore allowlist.

    line 7
  2. Very specific:

    Keep metadata a string-to-string map.

    line 10
  3. Very specific:

    Avoid built-in command names.

    line 12
  4. Distinctive:

    Keep each skill under 150 lines where practical.

    line 13
  5. Distinctive:

    Keep only team contracts, executable helpers, current platform traps or verification a model would miss.

    line 16
  6. Common:

    Keep customer data, personal names, private paths, identifiers and credentials out of every public file.

    line 19
  7. Very specific:

    Test installer changes only with a throwaway HOME.

    line 23
  8. Very specific:

    Test notifications with --dry-run.

    line 24
  9. Distinctive:

    Keep shell files compatible with Bash 3.2 and check them with ShellCheck.

    line 25
  10. Distinctive:

    Update the README catalogue and migration notes with behavior changes.

    line 26

≈ “Common” is an estimate: at least 1 in 5 of the 41,581 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

Contributing to .agents

This public repository holds Weaverse's team rules, first-party skills and optional Claude Code glue. The shared instructions live in rules/weaverse-team.md; follow them when changing this repository.

Add a skill

  • Put it in skills/<lowercase-hyphen-name>/SKILL.md and add its folder to the .gitignore allowlist.
  • Match name to the folder (1 to 64 ASCII lowercase letters, digits and single hyphens).
  • Set a string description of at most 1024 characters, including a specific "Use when" trigger.
  • Keep metadata a string-to-string map; use allowed-tools for tool hints, not metadata.tools.
  • Set disable-model-invocation: true for workflows that only a person should initiate.
  • Avoid built-in command names; scripts/claude-commands.json records the checked collision list.
  • Keep each skill under 150 lines where practical; 500 lines is the validation ceiling.

Apply the frontier filter

  • Keep only team contracts, executable helpers, current platform traps or verification a model would miss.
  • Cut generic advice and incident narratives. Explain the non-obvious failure, not textbook practice.
  • Reference maintained upstream skills with pinned sources. Do not copy third-party skills here.
  • Keep customer data, personal names, private paths, identifiers and credentials out of every public file.

Verify and maintain

  • Install the pinned validation dependencies as described in README.md, then run bash scripts/validate.sh.
  • Test installer changes only with a throwaway HOME; use --dry-run before any real installation.
  • Test notifications with --dry-run; never send a desktop notification from a test.
  • Keep shell files compatible with Bash 3.2 and check them with ShellCheck.
  • Update the README catalogue and migration notes with behavior changes.
  • Review quarterly; use upstream skill-creator evaluations before major skill changes or model/tool upgrades.

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.