memory-ticketing
Use when adding Memory Events, Memory Tickets, memory-map.json, vault-references.json, PM Soul memory ownership, or Memory Curator routing to an agent repo.
git clone --depth 1 https://github.com/agentlas-ai/Agentlas-OS /tmp/memory-ticketing && cp -r /tmp/memory-ticketing/.agents/skills/memory-ticketing ~/.claude/skills/memory-ticketingSKILL.md
# Memory Ticketing ## Required Files - `.agentlas/memory-map.json` - `.agentlas/memory-tickets.jsonl` - `.agentlas/vault-references.json` ## Flow 1. Workers emit `## Memory Events`. 2. Runtime or orchestrator wraps events into tickets. 3. Memory Curator validates, redacts, deduplicates, and routes. 4. PM Soul owns project memory and open loops. 5. Policy Gate approves shared team-memory promotion. ## Never Store Secrets, credentials, private keys, tokens, service-account JSON, raw logs, or full transcripts.
Use 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.
Use when adding or auditing local runtime behavior that turns a project folder into an Agentlas-aware workspace with .agentlas memory and sitemap files.
Use the Agentlas browser hardpoint for browser-required work.
Use when the user types /agentlas-build, /agentlas build, or /hep-build to design, build, and package a single agent or multi-agent team.
Prepare explicitly named Agentlas Hub or Cloud agents.
Use when the user types /agentlas-cloud, /agentlas cloud, or /hep-cloud to staff only from the signed-in owner's private Cloud packages.
Connect Agentlas agents or teams to Telegram.
Use 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.