A skill is a reusable, written-out set of instructions that tells an agent how to do a specific
kind of task well — on top of whatever it already knows. Skills attach to a team, not to an
individual agent, so any agent on that team can be told to use one.

Each skill has:

• A name (e.g. "Invoice Generator").
• A description — a one-line summary of what it does.
• A category — business, design, system, data, and so on.
• Instructions — the real substance: a concrete, step-by-step procedure the agent follows when the skill is invoked. This is what actually changes the agent's behavior, not the description.
• Optional examples of inputs and outputs.

A set of built-in skills is registered on first startup and can't be deleted. A few examples:

• Invoice Generator — turns project data or a plain-language description into a formatted Markdown invoice, with line totals and a grand total, optionally saved straight to the Brain.
• CRM Contact Manager — tracks contacts and deal stages as vault notes under CRM/Contacts/, with add/log/search/report operations.
• Proposal Writer — drafts a structured client proposal (summary, problem, solution, timeline, pricing, next steps) from a short brief.
• Client Onboarding — collects new-client info, creates a project note, and schedules a kickoff.
• Project Status Reporter — pulls from the vault and open tasks to produce a concise status report with a red/amber/green read.
• Meeting Summarizer — turns a transcript or notes into decisions, action items with owners, and open questions, saved under Meetings/.
• Sales Email Writer — drafts personalized outreach or follow-ups, tone adapted to the stage of the relationship.
• Support Ticket Handler — triages a support request by severity, checks the Brain for known answers, and drafts a reply.
• UI/UX Pro Max — a design-review mode: diagnoses an interface and produces Tailwind/CSS code matching the app's own design tokens.

There are also a few system skills — Build Agent Team, MCP Server, CLI Execute, File Management,
Database Query, Schedule Task — that back platform features rather than business tasks.

You don't call a skill directly. You tell an agent (via the coordinator) to use it:

The coordinator can also attach a skill to a team while creating it, or add one to an existing team
if you ask.

Ask the coordinator to build one:

A good skill instruction is concrete and step-numbered — write it the way you'd explain the task to
a new hire, not a one-line summary. If a task is something you (or a team) will do more than once,
it's a strong candidate for becoming a skill instead of being re-explained every time.