agentleFS
joris887joris887/exosuit/.claude/skills/CLAUDE.md

exosuit / skills

CLAUDE.md9 starsChanged 3 months agoMITView on GitHub

Each subdirectory is a skill. SKILL.md is the entry point.

The file

We split this CLAUDE.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:

    Keep SKILL.md under 150 lines.

    line 10

≈ “Common” is an estimate: at least 1 in 5 of the 26,980 CLAUDE.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
CLAUDE.md

Skills Directory

Each subdirectory is a skill. SKILL.md is the entry point.

Canonical format:

  • YAML frontmatter: name, version, description, trigger, depends-on, references, plus operational attributes
  • references/ for on-demand content (grep for sections, don't read entire files)
  • scripts/ for executables (run, don't read into context)
  • assets/ for output templates (copy, don't read)
  • Keep SKILL.md under 150 lines; move detail to references/. Exception: orchestration skills (story-cycle, sprint-end, bootstrap) keep procedural content inline — reference loading is advisory and LLMs skip it
  • See SKILL_TEMPLATE.md for format reference

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.