agentleFS
gear-foundationgear-foundation/vara-skills/AGENTS.md

vara-skills

AGENTS.md17 starsChanged 7 months agoMITView on GitHub

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

9 rules. About 0 are common, 4 are distinctive, and 5 are very specific to this project.

  • ≈0

    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:

    Use writing-skills before creating or editing any skill in skills/.

    line 7
  2. Very specific:

    Keep each skill directory flat and include SKILL.md, assets/, references/, and scripts/.

    line 9
  3. Very specific:

    Prefer shared repository references in references/ and shared templates in assets/.

    line 10
  4. Distinctive:

    Do not embed machine-specific absolute paths in published docs or skills unless the file is an explicit local validation target.

    line 11
  5. Distinctive:

    Treat the current public skill catalog as provisional until the sibling eval repo proves which candidate skills create real uplift.

    line 12
  6. Distinctive:

    Keep the first builder path focused on standard Gear/Vara Sails, not Vara.eth-first workflows.

    line 13
  7. Very specific:

    Run make verify before claiming the repo is ready.

    line 16
  8. Very specific:

    Keep installation working through scripts/install-codex-skills.sh.

    line 17
  9. Distinctive:

    Keep repository docs aligned with the product split: this repo owns skills and packaging.

    line 18

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

AGENTS.md

Purpose

This repository is the provisional product repo for a portable Vara Sails-builder skill pack. It owns builder-facing skill content, shared references, validation scripts, and installation surfaces for Codex first, with Claude and OpenClaw packaging added in-repo.

Working Rules

  • Use writing-skills before creating or editing any skill in skills/.
  • Apply TDD to repository behavior: add or update tests before changing scripts, validation logic, or published skill contracts.
  • Keep each skill directory flat and include SKILL.md, assets/, references/, and scripts/.
  • Prefer shared repository references in references/ and shared templates in assets/; skill files may reference them via relative paths.
  • Do not embed machine-specific absolute paths in published docs or skills unless the file is an explicit local validation target.
  • Treat the current public skill catalog as provisional until the sibling eval repo proves which candidate skills create real uplift.
  • Keep the first builder path focused on standard Gear/Vara Sails, not Vara.eth-first workflows.

Verification

  • Run make verify before claiming the repo is ready.
  • Keep installation working through scripts/install-codex-skills.sh.
  • Keep repository docs aligned with the product split: this repo owns skills and packaging; the sibling eval repo owns measurement.

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.