Skills
A Skill is a packaged, reusable set of instructions that gives a Clone or Agent a real capability. Your Clone is Claude running on your behalf, and Agents are the few permanent specialists it dispatches. Skills are what they actually know how to do.
What a Skill is
Think of a Skill as a well-written playbook the system can pick up and run. It holds the steps, the standards, and the judgment for one capability, written once and reused every time that work comes up.
A Skill is not a person and not a tool. It is the know-how. The same Skill can be loaded by your Clone or by any Agent that needs it.
Each Skill stays small and sharp. It carries a short hint that says when to use it, and a body that loads only when the work calls for it. Nothing is paid for until it is needed.
Capability lives in Skills. Orchestration lives in Agents.
This is the core idea, and it shapes the whole system.
Agents own domains and run the work. They decide what happens, in what order, and when it is good enough. That is orchestration.
Skills hold the actual capability. They are the deep, specialized craft a domain needs. An Agent without Skills is an empty manager. Skills without an Agent are instructions no one is running.
So the design is simple to say: few powerful Agents, world-class Skills. A small set of genuine masters, each equipped with deeply built Skills. Not a crowd of narrow workers pretending to be specialists.
How the system grows: add a Skill, not an Agent
When a new capability is needed, the answer is almost always a new Skill.
The team is capped at six: your Clone plus five Agents. Three work agents the Clone dispatches: the Maker Agent (makes new parts and Skills), the Manager Agent (manages recurring real-world work like inbox, calendar, and sending), and the Monitor Agent (watches how things perform over time, plus research and analysis). Two framework agents build and run the system itself: the Customizer (onboarding and ongoing tuning with you) and the Updater (autonomous upkeep).
A seventh Agent is never the answer. A new Skill is.
The rule holds because a new job is a new capability, and capability belongs in a Skill. Adding a Skill deepens an Agent that already exists. Spawning a narrow Agent just clutters the team and splits the work. The system grows by getting deeper, not wider.
| Need | Wrong move | Right move |
|---|---|---|
| A new capability | Spawn a narrow Agent | Add a Skill |
| Make an Agent stronger | Split off its work | Give it a better Skill |
| Cover a niche topic | Build a one-off Agent | Add a Sub-Skill |
Sub-Skills in plain terms
Some topics need extra depth inside a Skill. That is what a Sub-Skill is for.
A Sub-Skill is a Skill that deepens another Skill for one subtopic. It does not repeat what the main Skill already says. It adds the few extra things that one corner of the work needs, and it loads alongside the main Skill when that corner comes up.
For example, a research Skill can have a Sub-Skill that goes deeper on one kind of research. The main Skill carries the shared method. The Sub-Skill carries the special rules for that one area. Together they read as a pair.
How every part gets built
Skills are not thrown together. The Maker Agent builds and rebuilds them with the same disciplined steps, every time.
In plain words, the path is:
- Line it up to the outcome. State the result this Skill exists to produce, first.
- Review the context. Read what already exists so nothing is duplicated.
- Research. Learn the domain well before writing.
- Plan. Decide the shape before building.
- Build. Write the actual Skill.
- Test. Run it and see if it holds up.
- Refine. Fix what the test exposed.
- Deploy. Put it into real use.
- Check. Confirm the live result is right.
- Learn. Capture what to do better next time.
The path adapts to the job. The point is discipline, not a rigid march: take the shortest path that still does all of this well.
The bar every Skill clears: the 4 E's of Excellence
A Skill is not done until it clears four standards. All four, or it is not done.
- Effective. It achieves the outcome it named. Not "ran without error." Not "looks finished." It moved the thing that mattered.
- Efficient. It uses the least waste for the same result. Not the fewest words: the least burn.
- Ethical. It puts security first and does the right thing, always.
- Easy. It is easy on you. Calm to drive, clear to read, nothing to babysit. Effort you spend understanding the output is effort the system failed to save.
Miss any one and it is not done. Effective without Easy buries you in work. Easy without Effective is just theater. Efficient at the cost of Effective is a false saving. Ethical is never traded away. All four, or refine until all four.
Every Skill clears this bar. That is how the system keeps its craft high while it grows.