agentlas-auto-activation
Use when adding or auditing local runtime behavior that turns a project folder into an Agentlas-aware workspace with .agentlas memory and sitemap files.
git clone --depth 1 https://github.com/agentlas-ai/Agentlas-OS /tmp/agentlas-auto-activation && cp -r /tmp/agentlas-auto-activation/.agents/skills/agentlas-auto-activation ~/.claude/skills/agentlas-auto-activationSKILL.md
# Agentlas Auto-Activation Use this skill when a local runtime should activate Agentlas project continuity for a folder. ## Procedure 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. ## Minimum Files - `.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.sqlite` ## Safety 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. ## Reference See `docs/agentlas-auto-activation.md`.
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.
Use the Agentlas browser hardpoint for browser-required work.
Use when the user types /agentlas-build, /agentlas build, or /hep-build to design, build, and package a single agent or multi-agent team.
Prepare explicitly named Agentlas Hub or Cloud agents.
Use when the user types /agentlas-cloud, /agentlas cloud, or /hep-cloud to staff only from the signed-in owner's private Cloud packages.
Connect Agentlas agents or teams to Telegram.
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 this for /meta-agent requests.
Use when the user types /agentlas-graph, /agentlas graph, or /hep-graph to create, list, inspect, or run Agentlas automation graphs.