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.From its SKILL.md
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.
SKILL.md
0.9 KB, 148 tokens by cl100k_base, 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.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 0 of the 12 instructions most design frontend skills give in 148 tokens
Counted across 1,179 of the 2,086 authors here whose files we hold, read 2026-09-06
- Commit to a bold aesthetic directionin 31 of 1179, across 24 files
- Prefer component composition over inheritancein 28 of 1179, across 14 files
- Animate only transform and opacity propertiesin 27 of 1179, across 22 files
- Memoize expensive computations with useMemoin 26 of 1179, across 13 files
- Use semantic HTML elementsin 24 of 1179, across 23 files
- Virtualize long lists for performancein 21 of 1179, across 10 files
- Use CSS variables for design tokensin 20 of 1179, across 14 files
- Implement loading, empty, and error statesin 20 of 1179
- Lazy load heavy components with Suspensein 19 of 1179, across 8 files
- Respect prefers-reduced-motion media queriesin 18 of 1179, across 10 files
- Prioritize CSS-only animations for HTMLin 18 of 1179, across 16 files
- Use compound components for related UI elementsin 18 of 1179, across 7 files
Said here and by no other author read
- define the user job and target runtime
- start with one agent
- add team roles for routing or memory
- use a visible public agent tree
- add reusable procedures in skills folder
- add company blueprint for topology
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.