SkillPublic
agent-team-design
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.
Quality
91%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Securityby
Passed
No findings from the security scan
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.mdagents/40-session-agent-builder/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.
- Repository
agentlas-ai/Agentlas-OS
- Revision
ac497f9
- Last updated
- First committed
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.