Agent team design
Agent OS: keep specialist agents in a hub, spin up a temporary orchestrator per task. Local-first, works with any model.
npx -y skills add agentlas-ai/Agentlas-OS --skill agent-team-designAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
What its author says it does
Copied from the file, not written here
Use when designing a new multi-agent team, visible agents folder, role boundaries, handoff flow, PM Soul, Memory Curator, Policy Gate, or evaluation role. Use for agent-team repo creation even when the user only says they want a meta-agent or agent operating system.
SKILL.md
0.9 KB, as published. Nobody here has run it
Agent Team Design
Procedure
- Define the user job and target runtime.
- Start with one agent. Add team roles only when routing, memory, review, policy, or parallel ownership is useful.
- Use a visible public tree:
agents/10-single-agent-builder/agent.mdagents/20-multi-agent-team-builder/agent.mdagents/30-agentlas-packager/agent.md
- Add
skills/<capability>/SKILL.mdfor reusable procedures. - Add
.agentlas/company-blueprint.jsonfor topology.
Output
Return the role list, handoff direction, memory owner, policy owner, and eval owner.