How do I install the Agentlas Auto Activation skill?

Run npx skillmds@latest add agentlas-ai/agentlas-auto-activation in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Agentlas Auto Activation safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Agentlas Auto Activation?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Agentlas Auto Activation free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Agentlas Auto Activation?

agentlas-ai (@agentlas-ai) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Agentlas Auto Activation by agentlas-ai

Name: Agentlas Auto Activation
Rating: 4.666666666666667 (3 reviews)
Author: agentlas-ai

File contents

Agentlas Auto-Activation

Use this skill when a local runtime should activate Agentlas project continuity for a folder.

Procedure

For explicit activation, call hephaestus project ensure --project <folder> from Agentlas Core.
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.
Never create project state in the user's home directory, filesystem root, or outside the host's allowed project roots.
Install the managed privacy .gitignore block before local memory/indexes.
Add missing seed files, ontology/career indexes, and the bounded code map without overwriting existing user content.
Inject relevant project memory into future agent prompts.
Ask workers to emit ## Memory Events only for durable facts.
Route Memory Events through Memory Tickets and Memory Curator.
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.

---name: agentlas-auto-activationdescription: 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`.

Frequently asked questions

Agentlas Auto Activation