Agent definitions live inDocumentation Index
Fetch the complete documentation index at: https://curia.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
agents/<name>.yaml. Each file defines an agent’s identity, model configuration, system prompt, and skill access.
Schema reference
Field details
name
Unique identifier used for routing, delegation, and logging. Must be unique across all agent definitions. Convention: lowercase kebab-case.
role
| Value | Meaning |
|---|---|
coordinator | Receives all inbound messages. Only one coordinator should exist. |
specialist | Receives tasks only via delegation from the coordinator or other agents. |
model
The LLM provider and model used for this agent’s reasoning. Currently supported providers:
| Provider | Example models |
|---|---|
anthropic | claude-sonnet-4-6, claude-haiku-4-5-20251001 |
openai | gpt-4o, gpt-4o-mini |
ollama | Any locally-hosted model |
system_prompt
The prompt injected at the start of every task. Supports runtime variable interpolation using ${variable} syntax:
| Variable | Value |
|---|---|
${office_identity_block} | Agent persona (name, title, signature) from office identity config |
${executive_voice_block} | CEO’s writing voice profile |
${agent_contact_id} | The agent’s own contact UUID |
${available_specialists} | List of specialist agents available for delegation |
pinned_skills
Array of skill names this agent can always invoke. Skills must be registered in the skill registry. If a skill in this list doesn’t exist at startup, a warning is logged but the agent still starts.
allow_discovery
When true, the agent can use the skill-registry skill to search for and invoke skills not in its pinned_skills list. The coordinator typically has this enabled; specialists typically do not (they operate with a fixed, auditable skill set).
memory.scopes
Memory scopes isolate an agent’s working memory. Each scope is an independent namespace — facts stored in one scope are not visible to agents using a different scope. The coordinator uses no explicit scope (it shares the default scope). Specialists like email-triage and research-analyst use their own scopes to prevent cross-contamination.
Built-in agents
The agents Curia ships with and how they work together.
Building custom agents
Step-by-step guide to creating a new agent.