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.
git clone --depth 1 https://github.com/agentlas-ai/Agentlas-OS /tmp/agent-team-design && cp -r /tmp/agent-team-design/.agents/skills/agent-team-design ~/.claude/skills/agent-team-designSKILL.md
# 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. ## Output Return the role list, handoff direction, memory owner, policy owner, and eval owner.
Use when adding or auditing local runtime behavior that turns a project folder into an Agentlas-aware workspace with .agentlas memory and sitemap files.
Use the Agentlas browser hardpoint for browser-required work.
Use when the user types /agentlas-build, /agentlas build, or /hep-build to design, build, and package a single agent or multi-agent team.
Prepare explicitly named Agentlas Hub or Cloud agents.
Use when the user types /agentlas-cloud, /agentlas cloud, or /hep-cloud to staff only from the signed-in owner's private Cloud packages.
Connect Agentlas agents or teams to Telegram.
Use when creating a single Agentlas agent, creating a multi-agent team, or packaging an existing local/external agent into Agentlas architecture. Make sure to use this for /meta-agent requests.
Use when the user types /agentlas-graph, /agentlas graph, or /hep-graph to create, list, inspect, or run Agentlas automation graphs.