メニュー
Use when adding or auditing local runtime behavior that turns a project folder into an Agentlas-aware workspace with .agentlas memory and sitemap files.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when the user types /hep-cloud or asks to staff from THEIR OWN Agentlas cloud packages only. Cloud is one exact source scope; Network means Local + owner Cloud + public Hub.
Use when the user types /hep-network, mentions @Hephaestus, or asks Agentlas to staff a task from registered Local, owner Cloud, and public Hub agents or teams. The active host LLM is the temporary orchestrator.
Use when the user asks OpenClaw to staff a task from Agentlas Hub agents or teams. The active host LLM chooses from the Agent Workforce Ontology.
Use when the user types /prompts:hep-build, mentions @Hephaestus for build work, asks to create a single Agentlas agent, create a multi-agent team, or package an existing local/external agent into Agentlas architecture.
Use when the user types /hep-storm, says @Hephaestus storm <goal>, or asks to drive a goal to verified completion through a force-robust Stormbreaker loop. Stormbreaker routes the goal to real Agentlas specialists, materializes a dependency-ordered pipeline fabric, and runs each work packet as a verifier-first hardened loop that does not stall, run away, or claim false success. Use it for loop-worthy work — apps, sites, agents, automations, debugging, multi-step research, data/report generation. Trivial questions are answered directly, not stormed.
Use when the user types /hep-storm, mentions @Hephaestus storm, or asks to force-robustly drive a loop-worthy goal (apps, sites, agents, automations, debugging, multi-step research, data/report generation) to a verified finish. Stormbreaker routes the goal to real Agentlas specialists, materializes a dependency-ordered pipeline fabric, and runs a verifier-first loop that does not stall, run away, or claim false success. Trivial questions are answered directly, not stormed.
| name | agentlas-auto-activation |
| description | 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 this skill when a local runtime should activate Agentlas project continuity for a folder.
hephaestus project ensure --project <folder>
from Agentlas Core..gitignore block before local memory/indexes.## Memory Events only for durable facts..agentlas/project-soul-memory.md.agentlas/sitemap.json.agentlas/memory-map.json.agentlas/memory-tickets.jsonl.agentlas/vault-references.json.agentlas/skill-registry.json.agentlas/skill-trials.jsonl.agentlas/curator-decisions.jsonl.agentlas/activation.json.agentlas/code-map/project-map.json.agentlas/ontology-runtime.json.agentlas/ontology-runtime.sqlite.agentlas/career-graph.json.agentlas/career-graph.sqliteNever store secrets, raw logs, full transcripts, cookies, private keys, service
accounts, or payment material in .agentlas.
Keep MCP auto-bootstrap disabled unless the host separately opts in. Automatic receipts must not expose absolute project paths or raw filesystem errors.
If private files were already tracked before activation, report them as
trackedSensitivePaths; never mutate the user's Git index automatically.
See docs/agentlas-auto-activation.md.