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.
Profile →npx skills add agentlas-ai/Agentlas-OS --skill memory-ticketing --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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.
- Required Files
- Flow
- Never Store
What does the memory-ticketing skill do?
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.
How do I install it?
Run `npx skills add agentlas-ai/Agentlas-OS --skill memory-ticketing --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From agentlas-ai/Agentlas-OS, a repository with 1,165 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.