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.
Profile →npx skills add agentlas-ai/Agentlas-OS --skill agent-team-design --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Agent Team Design ## Procedure 1. Define the user job and target runtime. 2. Start with one agent. Add team roles only when routing, memory, review, policy, or parallel ownership is useful. 3. Use a visible public tree: - `agents/10-single-agent-builder/agent.md` - `agents/20-multi-agent-team-builder/agent.md` - `agents/30-agentlas-packager/agent.md` 4. Add `skills/<capability>/SKILL.md` for reusable procedures. 5. Add `.agentlas/company-blueprint.json` for topology. ## Output Return the role list, handoff direction, memory owner, policy owner, and eval owner.
- Procedure
- Output
What does the agent-team-design skill do?
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.
How do I install it?
Run `npx skills add agentlas-ai/Agentlas-OS --skill agent-team-design --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From agentlas-ai/Agentlas-OS, a repository with 1,165 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.