/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.
$ 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.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/agentlas-auto-activation
Context 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.
SKILL.md
agentlas-auto-activation.SKILL.mdname: 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."
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`.
Read more
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."
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`.
Agent OS: keep specialist agents in a hub, spin up a temporary orchestrator per task. Local-first, works with any model.
Other skills on agentlas-os.
- /agentlas-core-engine-meta-agent
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.
Open skill - /hephaestus-build
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.
Open skill - /hephaestus-cloud
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.
Open skill - /hephaestus-network
Use when the user types $hephaestus-network or /hep-network, mentions @Hephaestus, or asks Agentlas to staff a durable goal from registered Local, owner Cloud, and public Hub agents or teams. The active host LLM staffs each turn; the exact roster remains goal-bound until
Open skill - /hephaestus-storm
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
Open skill - /hephaestus-upload
Use when the user types $hephaestus-upload or /hep-upload, or asks to upload, publish, or list an Agentlas agent or team. Ask Cloud (private) vs Agentlas Hub (public) FIRST, then publish through the bundled Hephaestus gate.
Open skill