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…
Use when adding or auditing local runtime behavior that turns a project folder into an Agentlas-aware workspace with .agentlas memory and sitemap files.
$ npx -y skills add agentlas-ai/Agentlas-OS --skill agentlas-auto-activation --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/agentlas-auto-activationContext preview
The summary Claude sees to decide when to auto-load this skill.
Use when adding or auditing local runtime behavior that turns a project folder into an Agentlas-aware workspace with .agentlas memory and sitemap files.
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.
1. For explicit activation, call `hephaestus project ensure --project <folder>` from Agentlas Core. 2. For automatic activation, require a trusted writable host, an allowed root, a workspace marker, and host-side opt-in. Passive search, read-only work, and MCP requests do not imply write consent. 3. Never create project state in the user's home directory, filesystem root, or outside the host's allowed project roots. 4. Install the managed privacy `.gitignore` block before local memory/indexes. 5. Add missing seed files, ontology/career indexes, and the bounded code map without overwriting existing user content. 6. Inject relevant project memory into future agent prompts. 7. Ask workers to emit `## Memory Events` only for durable facts. 8. Route Memory Events through Memory Tickets and Memory Curator. 9. Use sitemap/task-bias state to avoid stale or unvalidated surfaces.
Never 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`.
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…