agentlas-core-engine-m…
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…
Staff a task only from Agentlas agents registered on this machine.
$ npx -y skills add agentlas-ai/Agentlas-OS --skill hep-local --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/hep-localContext preview
The summary Claude sees to decide when to auto-load this skill.
Staff a task only from Agentlas agents registered on this machine.
name: hep-local description: Staff a task only from Agentlas agents registered on this machine.
Update fallback: 자동 업데이트가 안 되면 `hephaestus update`를 한 번 실행하세요. 업데이트하지 않아도 현재 버전 명령은 그대로 동작합니다.
Raw request: `$ARGUMENTS`
Act as the temporary top-level workforce orchestrator. Use the local Agentlas OS MCP server `hephaestus-network` and call the Workforce tools with exact `sourceScope: "local"`. Before every unpinned discovery, Core refreshes the current safe snapshot for each active registered Local source, creating a new release when the source folder changed. This command searches only that registered Local inventory; it must not add owner Cloud or public Hub candidates. A prepared or goal-bound selection remains pinned to its exact release. `network reindex` rebuilds the card cache but is not the release refresh mechanism, and a new source still requires explicit registration.
1. Author a redacted `agentlas.workforce-work-order.v1`; private project grounding stays on-host. 2. Call `workforce.search_candidates` with `{workOrder, sourceScope: "local"}` and keep the complete response as `federationResult`, including its local registry receipt and the projected menu's `selectionSessionId`. Do not echo the projected menu back as `federationResult` — Core resolves the complete federation state locally from that session. 3. Author the final `agentlas.workforce-selection.v1` as the active host LLM, then call `workforce.validate_selection` with `{workOrder, selection}` and keep the response as `federatedSelection`. Revise on rejection; do not accept a deterministic picker or unrelated fallback. 4. Call `workforce.prepare_execution` with `{workOrder, selection, federatedSelection, projectDir}`. Require every selected row to remain pinned to source `local`, exact package/content identity, runtime bundle, permission policy, and context digest. 5. Execute distinct planner/manager, worker, synthesis, and verifier calls with explicit artifact handoffs. Preserve packaged Team graphs.
If the local Core MCP or registered inventory is unavailable, report `source_unavailable`; do not silently search Cloud or Hub. A prepared roster is not proof of execution.
For a `partial` or `failed` result, report each source receipt's exact `failureCode`. Never collapse several receipts into one, substitute a different code, or relabel the outcome.
Agent OS: keep specialist agents in a hub, spin up a temporary orchestrator per task. Local-first, works with any model.
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 when the user types /agentlas-build, /agentlas build, or /hep-build to design, build, and package a single agent or multi-agent team.
Use when the user types /agentlas-cloud, /agentlas cloud, or /hep-cloud to staff only from the signed-in owner's private Cloud packages.
Use when the user types /agentlas-graph, /agentlas graph, or /hep-graph to create, list, inspect, or run Agentlas automation graphs.
Use when the user types /agentlas-network, /agentlas network, $hephaestus-network, or /hep-network to staff a durable goal from registered Local, owner Cloud,…
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…