mcpbeat

Agent Team Design

agentlas-ai/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.

225 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
1165
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/agentlas-ai/Agentlas-OS --skill agent-team-design

The instruction itself

3 sections, as written by the author

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.md
  • agents/20-multi-agent-team-builder/agent.md
  • agents/30-agentlas-packager/agent.md
  • Add skills/<capability>/SKILL.md for reusable procedures.
  • Add .agentlas/company-blueprint.json for topology.

Output

Return the role list, handoff direction, memory owner, policy owner, and eval

owner.

How to use it

Copy the folder

Take agentlas-ai/agent-team-design from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.