A Skill is a way of working you have handed to Nisa, written down so it is done the same way every time.
There are two ways to use one, and a Skill can do both.
Runs on a schedule or trigger. "Send me a brief every weekday at 07:55" is a Skill that runs. So is "when a new important email arrives, sort it." Nisa runs it for you and reports back.
Used in conversation. "This is how we review a client message before it goes out" is a Skill Nisa uses when you ask. She sees the name and one line about what it is for; when your request matches, she loads the whole thing and follows it. You can also name it: "use client reporting", or type /client-reporting at the start of a message. When she used one, the reply says so.
What a Skill is made of
One folder: SKILL.md with the instructions (and a name and one-line description at the top), a references/ folder for material she reads when the instructions point to it, and a scripts/ folder for small programs she can run in a sandbox. A Skill that runs on a schedule also carries its trigger and inputs.
Team and personal
A team Skill belongs to the workspace and works for every member. Owners and admins add, import, edit and approve team Skills; members use them. Anyone can keep personal Skills that work only for them, in their own conversations and never in a shared channel. A personal Skill can be offered to the team; an owner or admin approves the move.
How Skills get in
Ask Nisa in Slack, WhatsApp or iMessage to write one with you, or let Nisa propose one after she notices a way of working you keep asking for. The Skills page in the dashboard lists your Skills; it does not create or upload them. A new team Skill, or a change to what its scripts need, is live only after an owner or admin approves it on a card that shows what it is and what it can do: its text, its files, its scripts, the secrets its scripts need and whether they reach the network. An owner or admin's own edit to the words of a team Skill is live at once — they are the people who would approve it — and the Skill then runs with that person's keys; the team keeps using the old version until anything about the keys or the network changes and someone says yes to the new one. Nothing Nisa proposes is saved without a human yes.
Skills that need a connection arrive switched off
A Skill that reads your Gmail cannot run before Gmail is connected. Those Skills arrive off; connect the app, switch the Skill on, and it starts on its next slot. A Skill used in conversation whose scripts need a key runs only when the owner who approved it has stored that key.
