author
Skill3 starsChanged 57 days agoMITView on GitHub
Creates, edits and shortens the skills, agents and skill scripts of the exo plugin. Use only inside the exo repository. Not for a rule or CLAUDE.md.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- databricks/databricks-ai-bridgetheir own version, first seen Nov 15, 2026
- nazmirket/skillstheir own version, first seen Nov 15, 2026
- iamibrahimriaz/piostheir own version, first seen Jul 31, 2026
- Autodesk/claude-browser-test-skillstheir own version, first seen Jul 8, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- databricks/databricks-ai-bridge★ 120same name
- Autodesk/claude-browser-test-skills★ 4same name
- iamibrahimriaz/pios★ 1same name
- nazmirket/skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 0 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 19
Run the check: Run the proof the brief names, or npm run validate:static when it names none.
- Very specific: line 34
Run claude --debug once on a new agent, because an unknown key is ignored silently.
- Very specific: line 38
Run as node scripts/<name>.mjs, with --help through parseFlags in lib/script-flags.mjs.
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Author
A skill earns its place only by stopping a mistake the model makes without it. Produce a skill or agent where every line changes what the model does and every rule carries its reason.
Process
- Prove the need. Change a skill, agent or check only for a user request or a failure seen in a real session. Grep the session transcripts for the failure, then add it with the count to the plugin docs folder's failures log before you edit, because an unrecorded failure cannot show later that the edit worked.
- Pick the home. A check or test when a machine can tell right from wrong, a script when the steps never vary, a template when only the content varies, and prose last. Prose is the dearest home because it loads every time.
- Write it small. Delete before you add: remove an overlapping rule before you write a new one. Cut what the model already does without being told. Give each rule one condition, one action and, where it sets the boundary, one clause of reason. Read
references/instruction-style.mdbefore you word a rule. - Run the check. Run the proof the brief names, or
npm run validate:staticwhen it names none. On a red check fix the structure; an exemption or allowlist entry only hides the failure.
Shape
descriptionsays what the skill does, then when to use it, in the third person and under 1,024 characters. The harness rejects angle brackets and line breaks. AddNot foronly where two skills could both match. Leave process steps out, because the model acts on the summary instead of reading the body.SKILL.mdstays under 500 lines and about 2,000 tokens.- Material only some runs need goes to
references/<topic>.md, named in the body with the condition for opening it. A reference sits one level deep and names no other.mdfile. - A skill never names a path into another skill, or
skills/<other>/. Say the one sentence you need, or write "runexo:<name>". - Text handed to a delegate sits beside
SKILL.mdas<role>-prompt.md. - A bare skill name in a skill body means
exo:<name>.
Agents
- Frontmatter holds
name,description(when the caller dispatches it),model,effortand atoolsallowlist, the cheapest set that does the job. - Plugin agents ignore
permissionMode,mcpServers,hooksandinitialPrompt, so leave them out. - Run
claude --debugonce on a new agent, because an unknown key is ignored silently.
Scripts
- Run as
node scripts/<name>.mjs, with--helpthroughparseFlagsinlib/script-flags.mjs. Use Node built-ins only. - Take input from flags, stdin or the environment, because a prompt hangs an unattended run. Print data to stdout and diagnostics to stderr.
- Take a constant from the repo, or use one overridable default or an
EXO_*_MSvariable throughenvironmentMs.
Judgment
- A rule a real failure showed outranks a rule that only reads well.
- Cut a rule only when the request names it, and keep each rule's reason clause.
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.

