agentlas-core-engine-m…
Use when creating a single Agentlas agent, creating a multi-agent team, or packaging an existing local/external agent into…
@agentlas-aiInstall SkillAgent Orchestration
Skill
/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.
Claude Code
$ npx -y skills add agentlas-ai/Agentlas-OS --skill agentlas-auto-activation --agent claude-code
Codex
$ npx skills add agentlas-ai/Agentlas-OS --skill agentlas-auto-activation -a codex -y
Cursor
$ npx skills add agentlas-ai/Agentlas-OS --skill agentlas-auto-activation -a cursor -y
Gemini CLI
$ npx skills add agentlas-ai/Agentlas-OS --skill agentlas-auto-activation -a gemini-cli -y
GitHub Copilot
$ npx skills add agentlas-ai/Agentlas-OS --skill agentlas-auto-activation -a github-copilot -y
OpenCode
$ npx skills add agentlas-ai/Agentlas-OS --skill agentlas-auto-activation -a opencode -y
Windsurf
$ npx skills add agentlas-ai/Agentlas-OS --skill agentlas-auto-activation -a windsurf -y
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`.
Ships withagentlas-os
An open-source AI agent OS inspired by OpenAI Dots, Meta Muse, Claude Duet, Nous Hermes, and Mem0. Built to lead entire projects rather than isolated prompts. Model-agnostic (BYOM) and native to Claude Code, Codex, Cursor, Antigravity, and Agentlas Desktop.
1.5k47 skills6 agents2 MCP
Stars on GitHub
Momentum
- stars in total
- 1.5k
Other skills on agentlas-os.
@agentlas-aiInstall Skillagentlas-packaging
Use when converting, repairing, or packaging an existing local or external agent/team into Agentlas architecture for local…
@agentlas-aiInstall Skillself-evolving-single-a…
Use when generating a single installable agent that should keep learning, track sources, refresh research, propose repairs, or…
@agentlas-aiInstall Skillsession-agent-builder
Turn the current interactive conversation into an owner-reviewed reusable Agentlas agent; accept JSON or JSONL only for explicit…
@agentlas-aiInstall Skillteam-builder-packaging
Use when generating or auditing a multi-role agent team package with orchestrator, PM Soul, Memory Curator, Policy Gate, workers,…
@agentlas-aiInstall Skillagentlas-operations
Agentlas 시스템 운용 절차 — hep-network 편성, cargo/Agent Cloud·marketplace 활용, workforce 로스터 재사용, 메모리 계약. One(개인 에이전트)이 Agentlas를 조작할 때 이…
@agentlas-aiInstall SkillMore skills from other plugins.
agentmail
Use your assigned AgentMail inbox to read email tasks, explicitly send or reply, and check delivery. Provided automatically by…
@paperclipaiInstall Skilladr-create
Create a new Architecture Decision Record with sequential numbering and AgentDB registration
@ruvnetInstall SkillQuestions about agentlas-auto-activation.
- Which coding agents can use agentlas-auto-activation?
- agentlas-auto-activation installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.