Why skills exist
A spoke gives the AI capability ("you can call ghl_send_message"). A skill gives the AI technique ("when sending a GHL message, first check opt-out, then thread through PHI Gateway, then log to lead-memory"). Skills are how senior practitioners teach the AI the playbook.
Two kinds of skills
| Kind | Where they live | Who sees them |
|---|---|---|
| Project skills | .claude/skills/<name>/SKILL.md | Every exec head + any agent that opts in. Shipped with Ambrose. |
| User skills | Per-user skill folder | Only that user's sessions. |
What ships
Currently ~23 project skills, including one per built-in spoke (spoke-ghl, spoke-agent-vault, spoke-marketplace-finder, …), plus a few cross-cutting ones (agent-orchestration, webhook-ghl, ambrose-api-author).
Custom & agency skills
Beyond the built-in project skills, you can add your own. Upload a SKILL.md on the Tools page (or generate one from a prompt). Agency-wide skills are available to every agent and team in the agency and show up on the Tools page where you can Preview the full playbook.
- Where you see them: the Tools page (with Preview), and the skill picker on the agent + team editors.
- How you attach them: tick them on an agent's or team's Tools tab.
- Where they run: chat, sequences/routines, the team/agent MCP endpoint (as
skill__<slug>), and the GHL webhook — the selected skill's playbook is injected into the run.
Ambrose ships a ready-made insurance content pack (9 skills for Medicare/ACA/life blogs, websites, location pages, brand kits, data, and SEO/AEO audits) available to every agency out of the box.