Standard Skill: Create a Skill
Create a Skill is a Standard Skill: it teaches the agent how to write a good Skill. The agent loads it when you ask it to turn a task or a way of working into a Skill, to improve a Skill, or when you ask what a good Skill looks like.
What a good Skill has
Section titled “What a good Skill has”- A precise name. One to 64 lowercase letters, digits and hyphens, such as
board-pack-check. - A description that says what the Skill does and when to use it, in the words you would use. The agent picks a Skill by its description, so this is the part that matters most.
- Short instructions, in the order of the work: the steps, what to check and what the answer looks like.
- For a workflow, the layout of an SOP. When you ask for a workflow, a procedure or a way of working as a Skill, the agent writes it as an SOP (Standard Operating Procedure): an overview, parameters marked required or optional, numbered steps, and where it helps examples and troubleshooting. Each step says what to do and then the constraints on it, worded with the keywords MUST, MUST NOT, SHOULD, SHOULD NOT and MAY as in RFC 2119: MUST and MUST NOT are binding, SHOULD and SHOULD NOT are advice, MAY is optional. A reference, a style guide or a domain explanation keeps a free form.
- The reason behind a rule, not a bare command.
- Examples of a request and a good result.
- Scripts only where code does better, such as arithmetic or a repeatable transformation.
- Files next to the instructions, such as templates or reference tables, that the agent reads only when it needs them.
Never put credentials or personal data in a Skill.
Saving the Skill
Section titled “Saving the Skill”Before it proposes the Skill, the agent walks the draft through a few realistic requests, one that should pick the Skill and ideally one that should not, and fixes the gaps it finds. The agent saves the Skill as a Personal Skill of yours, or as a new version of one, only after you approved it: you see the description and the files and accept, edit or reject them first. See Let the agent create a Skill. It never changes a Standard Skill, but offers a Personal Skill based on it. A Tenant Skill is changed only by a request: see Let the agent propose a change to a Tenant Skill.
When a Skill is the wrong choice
Section titled “When a Skill is the wrong choice”The agent tells you when something belongs elsewhere:
- A preference or a fact about you, such as the language or the level of detail you like, belongs in Memory.
- What a business term means, or how a metric is calculated, has no home of its own yet, because the Semantic Layer is not built. Until it exists, a Personal Skill is the only place to keep such a definition. It is a stopgap: only you can use your Personal Skill, so your colleagues’ answers do not use the definition, and it will move to the Semantic Layer once that exists. The agent tells you this when it saves such a Skill.
- A one-off request needs no Skill. A Skill pays off for a procedure that recurs, takes several steps, or needed several corrections.
Versions
Section titled “Versions”Each Standard Skill has a version number and a short changelog, which changes whenever the Skill does. The line the agent shows when it uses the Skill names the version it used.