AugmentClaude

Agentlas Auto-Activation

Set up Agentlas project continuity files in a workspace folder.

Installation

  1. Make sure Claude is on your device and in your terminal.

    Skills load from ~/.claude/skills/ when Claude Code starts up — so you need it on your machine first. If you don't have it yet, install it once with the command below, then run claude in any terminal to verify.

    One-time setup
    npm i -g @anthropic-ai/claude-code

    Already have it? Skip ahead.

  2. Paste into Claude Code or into your terminal.

    This copies the whole skill folder into ~/.claude/skills/agentlas-auto-activation-agentlas-ai/ — the SKILL.md plus any scripts, reference docs, or templates the skill ships with. Safe default: works for every skill.

    Faster alternative (instruction-only skills)

    Skips the clone and grabs only the SKILL.md file. Don't use this if the skill ships Python scripts, reference markdowns, or asset templates — they won't be downloaded and the skill will fail when it tries to load them.

    Quick install (SKILL.md only)
    Sign up to copy
  3. Restart Claude Code.

    Quit and reopen Claude Code (or any other agent that loads from ~/.claude/skills/). New skills are picked up on startup.

  4. Just ask Claude.

    Skills auto-activate when your request matches the skill's description — no slash command needed. Trigger phrases live in the skill's own frontmatter; you can read them in the “What this skill does” section above.

Prefer to read the source first? Open on GitHub.

When Claude uses it

Use when adding or auditing local runtime behavior that turns a project folder into an Agentlas-aware workspace with .agentlas memory and sitemap files.

What this skill does

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.

Related skills