Roles & Skills
Roles and skills are different layers of agent behavior.
A role defines the operating posture for a specialist or orchestrator. It answers:
- what kind of work is this agent meant to do?
- which tools or MCP servers can it use?
- which execution environment should it run in?
- which model assignment should it inherit or override?
- what core prompt and expectations should frame its decisions?
In the dashboard, the Specialists page is where operators manage these definitions.
Skills
Section titled “Skills”Skills are reusable instruction modules attached to roles.
They let you keep a role focused while still layering in specific behaviors such as:
- review discipline
- coding workflow expectations
- security or compliance checks
- writing standards
- domain-specific operating habits
The Skills page is the shared library for those instructions.
Why The Split Exists
Section titled “Why The Split Exists”If roles and skills were collapsed together, every role would become a monolith. Separating them keeps the system easier to reuse:
- roles define identity and capability
- skills define reusable technique and guidance
That makes it easier to share one skill across many specialists, or to evolve a role without duplicating large prompt blocks everywhere.
Model And Tool Policy
Section titled “Model And Tool Policy”Model and tool policy is not hidden in the runtime. The platform resolves that policy and issues the execution contract to the runtime.
That is why the dashboard surfaces for:
- Specialists
- Skills
- Models
- Tools
- MCP Servers
all matter together. They are separate editing surfaces for one eventual task contract.