| Term | What it is | Where it lives |
|---|---|---|
| Agent | An AI persona — identity + voice + memory. Speaks for itself. Holds a relationship with a user or a system. | agents/<slug>/ + agents table |
| Team | A role config — bundle of prompt + tool access + routines + GHL webhook. An agent plays a team to do a job. | teams/<slug>/ + teams table |
| Spoke | A capability — one MCP server with a set of tools. Spokes are the things the AI can do. Agents reach them through allowed_spokes. | spokes/<slug>/ |
| Skill | A markdown brief (SKILL.md) that teaches the AI how to use a specific spoke or workflow well. The Claude Agent SDK auto-attaches them to every exec head. | .claude/skills/<name>/SKILL.md |
| MCP | Model Context Protocol — the standard for plugging external tools into an AI. Ambrose speaks MCP both ways: every spoke is an MCP server, and you can mount external MCP servers as tools. | MCP page |
Example chain
Morgan (an exec-team agent) plays the Marketing team which has access to the search-audit and channel-bridge spokes. Each spoke exposes a few MCP tools. Morgan also has access to every skill in .claude/skills/, which teaches him how to chain those tools well.
What about a Routine?
A routine is a scheduled prompt attached to an agent or a team. "Run prompt X on cron Y." It is not a different kind of entity — it is a row in agent_cron_jobs pointing at an agent or team. See Routines.
What about a Workflow?
A workflow is a multi-step pipeline that chains several runs together — output of step 1 becomes input to step 2, with branches and conditions. Think of it as a recipe; a routine is a single scheduled call. See Workflows in the top nav.