Skip to main content
A skill is a procedure saved as a file: a name, a line on when it applies, and the steps. When a worker has reasoned its way through the same job twice, the right move is to write it down, and then it runs the steps next time instead of working them out again.

​
What one looks like

The same open format coding agents use for their own skills. The description matters most: it is what the worker reads to decide whether the skill applies.

​
Where a skill lives

A skill sits in the skills/ folder of one memory level, and that decides who has it: one client, one worker, or the whole company. A skill of the same name in a narrower level shadows the broader one, so Acme can have its own way of doing status notes without anyone editing the shared skill. Your skills always beat Ergoly’s.

​
Writing one yourself

  1. Write the SKILL.md in Claude Code, Cursor, or any editor.
  2. Put it in the right level: the worker’s Knowledge tab, New file or Upload a file under skills/<name>/, or push it through the API.
  3. The worker has it on its next conversation. There is nothing to deploy.
Already have skills written for Claude Code? Hand one to a worker in Slack and say use this skill. It rewrites it in its own words, maps the tools it needs to your connections, and offers a test run. For a whole set, ask your AI Admin to import them; it proposes which workers should own which.

​
Workers writing their own

Worth knowing. Around thirty skills, a worker is getting broad. Around fifty, split it into two workers with two roles. See Role.