agentlas-storm
Use when the user types /agentlas-storm, /agentlas storm, /hep-storm, or says @Hephaestus storm <goal> to drive a goal through the force-robust Stormbreaker loop with real Agentlas specialists.
git clone --depth 1 https://github.com/agentlas-ai/Agentlas-OS /tmp/agentlas-storm && cp -r /tmp/agentlas-storm/codex/plugins/agentlas-core-engine-meta-agent/skills/agentlas-storm ~/.claude/skills/agentlas-stormSKILL.md
# Agentlas Stormbreaker Loop (/agentlas-storm, /hep-storm) Drive a goal through the **Stormbreaker Loop** — Hephaestus' force-robust, verifier-first execution loop. Alias for `hephaestus-storm` and `/agentlas storm`. See [hephaestus-storm](hephaestus-storm/SKILL.md) for full execution protocol.
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.
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.