Skills

Where they live

Skills have their own section in the nav, under AI → Skills. That list is company-wide: every skill, every employee, one page — your whole playbook library. Filter it by the AI Employee that knows a skill, or search by name.

Clicking a skill opens its detail page: Playbook — the markdown editor, ⌘S to save — and Settings, where you rename or delete it. Each AI employee still links to their own slice of that list — same page, filtered to them.

How they work

When the runner runs the agent, it surfaces the Soul plus every Skill body into the model's context. The model picks the right playbook for the task at hand the same way a human would skim a runbook: by the title and the first paragraph.

Skills are not tools. Tools live in Integrations. A Skill is the prose around the tool: when to reach for it, how to use it, and what good output looks like.

Anatomy of a good Skill

• Title. A verb-first slug — write-weekly-digest, reconcile-stripe-payouts, page-oncall-for-checkout-p99. Searchable by what it does.
• Trigger. One sentence on when this skill fires. Either it's called explicitly by a Routine, or the model decides based on context — make that easy.
• Inputs. What the skill expects: a date range, a customer id, a markdown brief. Be explicit.
• Steps. The procedure. Number them. Reference the exact integration tools the employee will call.
• Definition of done. What the output looks like. A markdown report? A new Todo? A Slack message? Spell it out so the model has something to check itself against.

Example

# reconcile-stripe-payouts

## Trigger
Daily Routine "Reconcile Stripe", or when a teammate asks "what landed yesterday?"

## Inputs
- Date range (default: yesterday in company timezone)
- Account: the Stripe Connection named "Live"

## Steps
1. Call `stripe.list_charges` for the date range.
2. Group by payout id.
3. Cross-check totals against the bank Connection's deposits.
4. Flag any payout where the totals diverge by more than $0.01.

## Definition of done
A markdown report posted to #finance with three sections:
- Totals (count, gross, net, fees)
- Payouts (one row per payout, with link)
- Discrepancies (empty section is fine — say "none")

Composition

Skills compose by reference. A bigger skill can say "then run reconcile-stripe-payouts" and the model will follow that link. This keeps individual skills small and reusable across employees.

Sharing skills between employees

Today, copying is manual, but the company-wide list makes it quick: open the source skill, copy its playbook, hit New skill, pick the target employee, paste. The future Marketplace milestone (M17) will let you export an employee — soul + skills + routines + grants — as a bundle that imports into another company.