Skip to content
cccskills
FreePublished on GitHub

hep-local

Staff a task only from Agentlas agents registered on this machine.

The English summary is being prepared. Showing the original description.

See how to install

Files included (1)

  • SKILL.md3.4 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Update fallback: 자동 업데이트가 안 되면 hephaestus update를 한 번 실행하세요. 업데이트하지 않아도 현재 버전 명령은 그대로 동작합니다.

/hep-local

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.

If workforce.prepare_execution refuses with a repair object, the agent is broken, not absent. Say in plain words what repair.meaning says, offer the first available action in repair.repair, and run its command only after the user agrees. When a repair reports reselectionRequired: true, select again (workforce.validate_selection, then workforce.prepare_execution); never swap in a different agent without a new selection. A refusal that carries alternates lists other callable agents from the same search: present them as candidates and let the user or the selection step choose.

A package the builder wrote to the global agent folder is registered automatically at the next local search once it passes contract verify; one that does not pass is not registered and is named with its first blockers. hephaestus workforce local-autoregister does it now and prints contractFailing and refused rows, which is where to look when an agent you built is missing from the menu.

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.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

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.

The English summary is being prepared. Showing the original description.

agentlas-ai/Agentlas-OS1.6KUpdated Oct 17, 2026

Single entry point for every Agentlas command: /agentlas network, /agentlas build, /agentlas storm, /agentlas graph, /agentlas one, /agentlas upload, /agentlas cloud, /agentlas hub, /agentlas local, /agentlas browser, /agentlas call, /agentlas search, /agentlas connect.

The English summary is being prepared. Showing the original description.

agentlas-ai/Agentlas-OS1.6KUpdated Oct 17, 2026

Single entry point for every Agentlas command: /agentlas network, /agentlas build, /agentlas storm, /agentlas graph, /agentlas one, /agentlas upload, /agentlas cloud, /agentlas hub, /agentlas local, /agentlas browser, /agentlas call, /agentlas search, /agentlas connect, /agentlas login, /agentlas orch, /agentlas update.

The English summary is being prepared. Showing the original description.

agentlas-ai/Agentlas-OS1.6KUpdated Oct 17, 2026

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

The English summary is being prepared. Showing the original description.

agentlas-ai/Agentlas-OS1.6KUpdated Oct 17, 2026

Use when the user types /agentlas-browser <url-or-query>, /agentlas browser, or /hep-browser for browser-required tasks, rendering pages, form flows, or visual evidence.

The English summary is being prepared. Showing the original description.

agentlas-ai/Agentlas-OS1.6KUpdated Oct 17, 2026

Use the Agentlas browser hardpoint for browser-required work.

The English summary is being prepared. Showing the original description.

agentlas-ai/Agentlas-OS1.6KUpdated Oct 17, 2026

See all skills by agentlas-ai

Report a problem with this skill