Skills
Teach it once. It does it your way every time.
A skill is your procedure, written in plain language and published. Call it by name and it runs the same way every time, rather than depending on how the question was phrased.
The problem
The same prompt, retyped slightly differently every week
Anything you ask an assistant to do repeatedly ends up worded a little differently each time, and the output drifts with it. The knowledge of how your company actually does the thing stays in one person's head.
knowledge.search3 sources citedRefund policy, escalation ownershubspot.query_records2 sources citedOpen deals flagged at riskslack.read_thread1 source cited#support escalation from Tuesdayhubspot.update_recordSet stage to Closed Lost
What it does
Written, not configured
Plain markdown describing the steps, the sources to use, and what the result should look like.
Frozen when published
Publishing locks the version, so a skill cannot quietly change under the people relying on it. Editing starts the next draft.
Invoked by name
Call it in chat, hand it to a task on a schedule, or run it from the AI client you already use.
Seventy-two ship with the product
Every account starts with a published library rather than an empty one.
- Skills are scoped: personal, a department, or the whole organisation
- A skill only gets tool access if it names the tools it needs
- Every run is kept as a record, with the sources it cited
- Import and export as a file, so a skill can move between accounts
The rest of it
Give your AI a company to work for
Connect your tools, and every agent you already use starts the day knowing how your company actually works.