Browse Skills

Moai Meta Harness is a deprecated legacy 7-phase meta-harness that redirects to the v4 harness Builder (/moai:harness) for new harness creation. Use it only for backward-compatible invocation paths that reference the old 7-phase workflow.

LSEL Curator drains the .moai/lessons-inbox.jsonl, filters Bash timeout/sandbox noise, clusters remaining failures by event key, and stages high-signal candidates for the Local Self-Evolution Loop. Use it to turn raw tool failure stubs into curated proposal candidates.

Moai ADK Domain Patterns is a reference for the four harness specialists working on the moai-adk-go Go codebase and templates. It covers the CLI/template/config/hook/spec subsystem architecture, key source paths, specialist delegation map, template-first build cycle, namespace separation contract, and common add-a-template/add-a-hook/add-an-agent/add-a-SPEC workflows.

Agent Team Design defines agent teams, role boundaries, handoffs, memory owners, policy owners, and evaluation roles for multi-agent systems. Use it when creating a new team, a meta-agent, or an agent operating system repository.

Agentlas provides a single entry point for all Agentlas commands, including staffing federated workforces, building agent teams, running DAG graphs, browser automation, and searching agent catalogues. Use it when orchestrating multi-agent systems.

Agentlas Auto-Activation turns a project folder into an Agentlas-aware workspace with .agentlas memory and sitemap files. Use it when adding or auditing local runtime behavior that activates project continuity.

Agentlas Build designs, assembles, and packages installable single agents or multi-agent teams. Use it after /agentlas-build, /agentlas build, or /hep-build to classify mode, interview requirements, author routing card and soul, generate runtime adapters, and verify the package.

Agentlas Call invokes named Agentlas Hub or Cloud agents attached to the current project. Use it when you type /agentlas-call <agents> <context>, /agentlas call, or /hep-call to borrow and execute those agents.

Agentlas Cloud Workforce staffs specialist roles from the owner's private Agentlas Cloud packages. It is triggered by the /agentlas-cloud, /agentlas cloud, or /hep-cloud commands.

Agentlas Hub staffs specialist roles from the public Agentlas Hub marketplace when a user invokes /agentlas-hub, /agentlas hub, or /hep-hub. Use it to assemble teams from the public workforce instead of local or private agents.

Agentlas Local Workforce staffs specialist roles from locally registered packages in ~/.agentlas/workforce/local. Use it when the user types /agentlas-local, /agentlas local, or /hep-local to restrict staffing to Local packages.

Agentlas Network staffs durable goals from registered Local, Cloud, and public Hub agents or teams via federated workforce orchestration. Use when the user types /agentlas-network, /agentlas network, $hephaestus-network, or /hep-network.