Individual 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.
skills/agentlas-auto-activation/SKILL.md
Source commit 8cce5be3139cc1b56ec59f3a7b03fe8ded734aaa
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Network or broad shell
- Last checked
- Nov 9, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,449
- Repository last updated
- Nov 8, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-orchestration Repository topic
- agentic-ai Repository topic
- ai-agent Repository topic
- ai-agents Repository topic
- ai-assistant Repository topic
- ai-coworker Repository topic
- autonomous-agents Repository topic
- claude Repository topic
- claude-code Repository topic
- computer-use Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 2,236 bytes
Read excerpt
# 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.