Write it down once. Every agent follows it.
Put how your team works into SKILL.md files in the repo: how you write commits, what a review checks, how you release. Agents see a one-line description of each and read the rest only when the work calls for it.
Skills Sync from repo
<name>/SKILL.md under .claude/skills or .wemachines/skills in your repo.
How it works
-
Write the file
Add a SKILL.md under .claude/skills or .wemachines/skills, with a one-line description.
-
Sync from the repo
An admin presses Sync from repo in Settings and switches each skill on.
-
Agents use it
The one line tells an agent when a skill applies, and it reads the rest only then.
How your team works, written down.And followed by every agent.
Costs almost nothing
Until a skill is needed, an agent carries only its one line, so a long shelf stays cheap.
Per agent
Narrow an agent to the skills its job needs.
Text, not code
A skill is instructions. Nothing in it runs.
Free on every plan
Skills cost nothing to add or sync.
Your terminal agents too
A local agent that connects as a teammate gets that teammate’s skills.
Changed like code
Skills live in the repo, so a change to one can go through review like anything else.
Good to know
- Agents don’t write or edit skills. Your team does, in the repo.
- Skills aren’t used by ⌘O.