agentlas-auto-activation

$npx mdskill add agentlas-ai/Agentlas-OS/agentlas-auto-activation

Activates Agentlas workspace with memory and sitemap files.

  • Ensures a project folder becomes an Agentlas-aware workspace.
  • Depends on Agentlas Core's hephaestus command and trusted host config.
  • Decides activation based on host trust, allowed roots, and workspace markers.
  • Creates seed files and injects project memory into future agent prompts.

SKILL.md

.github/skills/agentlas-auto-activationView on GitHub ↗
---
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`.

More from agentlas-ai/Agentlas-OS

SkillDescription
agent-team-designUse 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.
agentlas-core-engine-meta-agentUse 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.
agentlas-packagingUse when converting, repairing, or packaging an existing local or external agent/team into Agentlas architecture for local install, Agentlas import, Codex plugin use, Claude adapter use, or open-source release.
agentlas-security-scanUse when an agent folder must pass the Agentlas Cloud 2-stage security scan (static rules + BYOK LLM judgment) before private sync or public publish, or when asked to run/interpret `hephaestus security scan`.
clarify-question-loopUse when a meta-agent request is too ambiguous to safely generate, package, publish, or adapt without one to five targeted questions.
hephaestus-buildUse 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.
hephaestus-cloudUse 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.
hephaestus-networkUse when the user types /hep-network, mentions @Hephaestus, or asks Agentlas to staff a task from registered Local, owner Cloud, and public Hub agents or teams. The active host LLM is the temporary orchestrator.
hephaestus-stormUse 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 work packet as a verifier-first hardened loop that does not stall, run away, or claim false success. Use it for loop-worthy work — apps, sites, agents, automations, debugging, multi-step research, data/report generation. Trivial questions are answered directly, not stormed.
install-verificationUse when verifying that a generated agent package can be installed, discovered by runtimes, and checked without private dependencies.