A Skill is a job you have handed to Nisa, written down so it can run again.
"Send me a brief every weekday at 07:55 with what changed in my inbox and calendar" is a Skill. So is "every Friday, read the sales stand and tell me which deals have gone quiet."
You do not write one. You describe it, and Nisa builds it.
What a Skill is made of
A trigger — when it runs. A schedule (every weekday at 07:55), an event (a new important
email arrives), or nothing at all, if you want to start it by hand.
Inputs — the things that change between runs. How many days to look back, which brand to watch, which spreadsheet to read.
What it reads — usually one or more Brain packs, and sometimes a connected app like Gmail or Google Sheets.
What it produces — a report, a draft, a list. It lands in Slack, and it is also written somewhere durable so you can ask about it later.
Why a Skill and not just a conversation
A conversation happens once. A Skill happens every morning without you remembering it.
The difference matters most for the things you would never do reliably by hand: noticing that a lead has been silent for three weeks, or that a number in a report has not moved while the text around it keeps saying it will.
Skills that need a connection arrive switched off
A Skill that reads your Gmail cannot run before Gmail is connected. Rather than failing every morning and telling you about it, those Skills arrive off. Connect the app, switch the Skill on, and it starts on its next scheduled slot.
Skills that need nothing — the ones that read only your Brain — arrive on.