Individual skill

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.

skills/agent-team-design/SKILL.md

Read pinned source

Source commit e68fc35f5fcf16cc2fec2492b69290d84c9c6eb8

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: Yes
Repository scan complete: No
Skill scan complete: Yes
Observed behavior: Network or broad shell
Last checked: Nov 10, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 1,450
Repository last updated: Nov 9, 2026
License: Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

agent-orchestration Repository topic
agentic-ai Repository topic
ai-agent Repository topic
ai-agents Repository topic
ai-assistant Repository topic
ai-coworker Repository topic
autonomous-agents Repository topic
claude Repository topic
claude-code Repository topic
computer-use Repository topic
design Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 948 bytes

Read excerpt


# 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`
   - `agents/40-session-agent-builder/agent.md`
4. Add `skills/<capability>/SKILL.md` for reusable procedures.
5. Add `.agentlas/company-blueprint.json` for topology.