This page is also available in Arabic.
What it does
A skill is a written method: how this team prepares a variance commentary, what a supplier onboarding check covers, the house style for a board note. The assistant reads a skill when a request matches its description, and follows it. Skills can be exported as SKILL.md and copied to make your own version.
Why it is there
Good practice lives in people's heads and in old files. A skill writes it down once, in a form the assistant applies every time, and a reviewer can read exactly what it was told to do.
When to open it
- To see what the assistant follows for a kind of request
- To copy a built-in skill and adapt it to the team's way
- When a reviewer asks why a report has the shape it has
How it works
Front matter names the skill (lowercase, hyphens) and says when to use it; the body is the method, with reference files if it needs them. Nothing in a skill is executed; it is read.
A scenario
The team copies the built-in month-end commentary skill, adds always state the three largest variances with their account and party, and from the next close every commentary opens that way.
Steps
Read a skill
Its description says when the assistant uses it.
Make your own copy
Adapt the method; the original stays.