Reference
A Playbook is a folder of readable files, and this is what those files may contain. The exact fields, what an omission means, the one endpoint an external agent can call, and the limits a run actually meets.
Every number on these pages is one the runtime enforces. Looking for the knowledge a Playbook reads rather than the format it is written in? That is Reference files, which is a different page one URL away.
- playbook.mdThe Playbook document itself: the fields it must declare, the ones it may, what each optional field means by its absence, and the sections in its body.
- Play filesThe contract for one step: what every Play file has to declare, what it may add, and the rule about what a step reads when it does not say so.
- SKILL.mdThe reusable step format, spelled in capitals because that is the filename: what a Skill declares about itself, and the two sections in its body.
- The agent endpointThe one programmatic door into YAMO: what an agent can call, how a Service becomes a callable tool, and what consent and spend caps mean for the payer.
- LimitsThe boundaries a run actually meets: how long it may take, how often a step is retried, what gets truncated, and how large an uploaded file may be.