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.
Install
$ agentstack add skill-agentlas-ai-hephaestus-agent-team-design ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
About
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//SKILL.mdfor reusable procedures. - Add
.agentlas/company-blueprint.jsonfor topology.
Output
Return the role list, handoff direction, memory owner, policy owner, and eval owner.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: agentlas-ai
- Source: agentlas-ai/Hephaestus
- License: Apache-2.0
- Homepage: https://agentlas.cloud
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.