agentlas-build
Use when the user types /agentlas-build, /agentlas build, or /hep-build to design, build, and package a single agent or multi-agent team.
git clone --depth 1 https://github.com/agentlas-ai/Agentlas-OS /tmp/agentlas-build && cp -r /tmp/agentlas-build/codex/plugins/agentlas-core-engine-meta-agent/skills/agentlas-build ~/.claude/skills/agentlas-buildSKILL.md
# Agentlas Build (/agentlas-build, /hep-build) Design, assemble, and package installable single agents or multi-agent teams. Alias for `/agentlas build` and `/hep-build`. Guides the workflow through: 1. Mode classification (`single-agent-creator`, `team-builder`, `agentlas-packager`, `session-agent-builder`) 2. Interview/research gate 3. Routing card and soul authoring 4. Runtime adapter generation (Codex, Claude, Gemini, Antigravity) 5. Package verification
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.
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.
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.