The Skill library
Reusable steps kept in your account: what a Skill is, how one is imported into a Playbook as a step, and what a Skill file has to say for itself.
On this page
A Skill is a reusable step kept in your account rather than inside one Playbook. Importing one into a Playbook creates a step from it. So a Skill is where a step comes from, and a Play is what it becomes.
Your Skill library
It lives in your account settings, under Skill Library, and it has two parts.
- Your skills, which you have imported.
- Shipped with YAMO, the ones that come with every account. These are what the seed templates lean on, which is why a fresh account can run everything in the Playbook Library without adding anything.
Importing one into a Playbook
From a Playbook with no steps yet, the add control offers to import from the library. Importing wires the Skill in as the next step: its position, what it takes, what it hands on and the tools it needs are all resolved into the chain rather than left for you to reconcile.
A step imported this way records which Skill it came from. A step written by hand does not, and does not need to.
Skills reach a Playbook through the library and nowhere else. That is a deliberate single door: a step cannot arrive from a file drop or a paste, so what a Playbook can call is always something your account holds.
What a Skill file says
A Skill is a folder whose one required file is SKILL.md. That file declares
its name, a description of what it does, whether it is one of yours or one of
YAMO's, the tools it needs, the shape of its input and output, and the format it
produces. Below the front matter it carries its instructions, and optionally a
persona.
Importing a new Skill into your library is a SKILL.md upload. A Skill that
declares a tool you have not connected is refused rather than accepted and left
broken. See the SKILL.md reference.
What is not built
There is no way to promote a step you wrote back into the library as a Skill. The path runs one way today: from the library into a Playbook. Reuse of a good step means writing it again, or copying its file.
More in Build
Related
Build from a template
Copying a working Playbook into your account: what you get, what stays yours, and what the copy asks you to replace before it is really about you.Build from scratch
Starting with nothing but a description of the work: the five questions YAMO asks, what each answer writes down, and what you have when they end.Writing the steps
The ordered steps that do the work: what each one declares, how they hand work along the chain, and how instructions are written and changed.Deploy: making it runnable
The setup checklist and what it checks, what Deploy actually does to a Draft Service, and why nobody at all can run a Playbook before that point.Pricing
How YAMO charges: you pay for the runs you make, and nothing for the ones you do not. What a run is, what it includes, and what publishing costs.Who it's for
The six kinds of expert YAMO is built for, and what changes when the method you already follow becomes a Service that somebody else can run.
Open a Playbook that does this
Every template in the library publishes its contract and a real example output.