skills

Open what this world already knows how to do. A skill packages the instructions for one job together with the assets, guides, and tools that job runs through, so opening one leaves you ready to act rather than ready to go looking.

Skills advertise themselves — every skill's name and one-line description rides your tool responses. list gives the roster; invoke opens one; release puts one down. The agent_skill tool reaches all three.

A skill with distinct branches carries subskills, addressed parent/sub. They are reachable only through their parent, so a skill can go several procedures deep while costing the roster a single line — invoke on the parent names the ones available.

A skill you open stays open

Opening a skill holds it. A held skill leads every advertisement with its own line and the subskills under it, each marked opened or not, and it stays there until you release it.

That is what carries a job across the calls it takes. A skill's later passes — the validation after the build, the publish after the validation — come due long after the roster line that leads to them stops looking relevant, because by then the scene is built and a skill about building scenes reads as spent. The held section keeps the passes you have left in front of you instead.

release is the other half: it says the job is finished and takes the lines back. Releasing a parent releases the subskills opened under it.

Write a new skill by creating a <name>.agentSkill/ folder anywhere under /zero/source/, and it joins the roster as soon as it exists. guides { path = "types/agentSkill" } is the authoring reference.