Skills your team shares

Someone on your team works out how to do a job properly — how you write a launch brief, how you check a supplier, how you handle an incident. Today that stays in their head, or in a document nobody opens. A skill is that know-how written down once, so everyone’s assistant can follow it instead of guessing.

Two things make it worth doing here rather than passing a file around:

Somebody decides what gets in. A skill is only used once someone in your organization has read it and published it.
You can pull it back. Withdraw a skill and every assistant stops being served it, immediately. No hunting down who copied what.

Using one: you don’t, your assistant does

There’s nothing to install and no list to browse. Ask for the job in your own words — “write the launch brief for the new offer” — and your assistant finds the skill your organization published for exactly that, and follows it.

That’s why the words matter when a skill is proposed: they’re what your colleagues will say when they need it.

Proposing one

Anyone in the organization can propose a skill. Publishing it is someone else’s call — that’s the whole point.

Have your assistant prepare the skill. A skill is a folder of files with a SKILL.md inside that explains the job. Say “I want to share how we do this” — your assistant writes it down, saves the folder for you, and hands you the link to the proposal page.
Open Skills → Propose a skill, and drop the folder there. The page reads what the SKILL.md says and fills in the name, what it’s for, and the phrases people would say to ask for it. Check those words — they’re how your colleagues will find it. Nothing is sent yet.
Answer what it actually does. Does it run a program on someone’s computer? Does it reach the internet? Does it create anything outside Bailey, like a pull request or an email? These questions are never pre-filled, on purpose: you answer them yourself. It’s what the person reviewing it reads, and what your colleagues are told before they use it.
Propose it. That click is what sends everything. Nobody sees it yet, not even your colleagues’ assistants. That wait is the point, not a delay.

To correct a skill that’s already published, open it and choose Send a new version: same gesture — drop the updated folder, and the form starts from what the current version declared.

Publishing one

Owners, admins and anyone with the governance role see a Waiting for your review list on the Skills page. Each proposal says, in plain sentences, what it will do on your colleagues’ side. You publish it, or you turn it down with a reason.

Withdrawing one

Open the skill and choose Withdraw this skill. You’ll be asked why — that sentence isn’t paperwork: it’s what assistants repeat to whoever asks for the skill afterwards. Withdrawal takes effect immediately and can’t be undone; a corrected version has to be proposed and published like any other.