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.From its SKILL.md
npx -y skills add agentlas-ai/Agentlas-OS --skill memory-ticketingAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
SKILL.md
0.7 KB, 124 tokens by cl100k_base, as published. Nobody here has run it
Memory Ticketing
Required Files
.agentlas/memory-map.json.agentlas/memory-tickets.jsonl.agentlas/vault-references.json
Flow
- Workers emit
## Memory Events. - Runtime or orchestrator wraps events into tickets.
- Memory Curator validates, redacts, deduplicates, and routes.
- PM Soul owns project memory and open loops.
- Policy Gate approves shared team-memory promotion.
Never Store
Secrets, credentials, private keys, tokens, service-account JSON, raw logs, or full transcripts.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 0 of the 12 instructions most memory context skills give in 124 tokens
Counted across 754 of the 1,056 authors here whose files we hold, read 2026-09-06
- Preserve existing content structurein 15 of 754, across 9 files
- Front-load the leading wordin 14 of 754, across 10 files
- Update existing entries instead of duplicatingin 14 of 754, across 7 files
- Keep CLAUDE.md under one hundred linesin 14 of 754, across 12 files
- Read CLAUDE.md at the project rootin 14 of 754
- Keep each meaning in a single source of truthin 12 of 754, across 8 files
- Redact sensitive information before committingin 11 of 754, across 4 files
- Scan for all CLAUDE.md filesin 11 of 754, across 7 files
- Use frontmatter for metadata on filesin 10 of 754, across 3 files
- Repeat user interactions 10 timesin 10 of 754, across 4 files
- Write the CLAUDE.md file into the target folderin 10 of 754, across 8 files
- Use memlab to process snapshotsin 9 of 754, across 3 files
Said here and by no other author read
- Emit Memory Events as a worker
- Wrap events into tickets via runtime
- Validate and route tickets via Curator
- Own project memory via PM Soul
- Approve team memory via Policy Gate
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.