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
- Very specific: line 7
Use writing-skills before creating or editing any skill in skills/.
- Very specific: line 9
Keep each skill directory flat and include SKILL.md, assets/, references/, and scripts/.
- Very specific: line 10
Prefer shared repository references in references/ and shared templates in assets/.
- Distinctive: line 11
Do not embed machine-specific absolute paths in published docs or skills unless the file is an explicit local validation target.
- Distinctive: line 12
Treat the current public skill catalog as provisional until the sibling eval repo proves which candidate skills create real uplift.
- Distinctive: line 13
Keep the first builder path focused on standard Gear/Vara Sails, not Vara.eth-first workflows.
- Very specific: line 16
Run make verify before claiming the repo is ready.
- Very specific: line 17
Keep installation working through scripts/install-codex-skills.sh.
- Distinctive: line 18
Keep repository docs aligned with the product split: this repo owns skills and packaging.
≈ “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.
Files
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-skillsbefore creating or editing any skill inskills/. - 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/, andscripts/. - Prefer shared repository references in
references/and shared templates inassets/; 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 verifybefore 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.
Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 28,693 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository27 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- vara-skillsSkill
- vara-skillsSkill
- awesome-sails-vftSkill
- gear-architecture-plannerSkill
- gear-builtin-actorsSkill
- gear-gstd-api-mapSkill
- gear-message-executionSkill
- gtest-tdd-loopSkill
- idea-to-specSkill
- sails-architectureSkill
- sails-dev-envSkill
- sails-ethexe-architectureSkill
- sails-ethexe-implementerSkill
- sails-feature-workflowSkill
- sails-frontendSkill
- sails-gtestSkill
- sails-idl-clientSkill
- sails-indexerSkill
- sails-local-smokeSkill
- sails-new-appSkill
- sails-program-evolutionSkill
- sails-rust-implementerSkill
- ship-sails-appSkill
- task-decomposerSkill
- vara-skills-upgradeSkill
- vara-walletSkill
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
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.

