install-verification
Use when verifying that a generated agent package can be installed, discovered by runtimes, and checked without private dependencies.
git clone --depth 1 https://github.com/agentlas-ai/Agentlas-OS /tmp/install-verification && cp -r /tmp/install-verification/.agents/skills/install-verification ~/.claude/skills/install-verificationSKILL.md
# Install Verification Run: ```bash scripts/verify-package.sh scripts/public_safety_check.sh ``` Then inspect: - root `AGENTS.md`, `CLAUDE.md`, `GEMINI.md`; - `.agents/`; - `.agentlas/`; - `.claude/`; - `codex/`; - `scripts/install.sh`. Do not claim completion if any required file is missing.
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.