agent-memory-systems — Claude Code skill: agent memory with tenant
Skill for designing agent memory with per-user and per-tenant isolation. Build RAG, conversation history, and vector stores so that one client's data stays separate from another.
npx skills add sickn33/agentic-awesome-skills --skill agent-memory-systems -a claude-codeWhat agent-memory-systems does
The skill walks you through choosing record types—semantic for facts, episodic for events, procedural for reusable methods—and organizing them with verified identity binding. You start by defining the task, authenticating the tenant, confirming retention rights and limits. Then you pick a supported SDK adapter and specify record IDs, source evidence, timestamps, namespaces and conflict policy.
You must read the detailed guide before executing the skill. It contains mandatory safety procedures, prerequisites and validation requirements. Test cross-tenant rejection, stale records, bounded retrieval and failed writes using isolated fixtures. Benchmark retrieval against held-out questions before expanding storage.
The output is an architecture with evidence, a change plan listing unresolved adapters and hosting costs, and the persistence operations you actually authorize. Do not apply vendor operations without explicit approval.
What it helps with
- design memory for a multi-tenant agent without data leaks
- diagnose stale or conflicting records retrieved across tenants
- plan embedding and store migration while preserving source records
- test cross-tenant access rejection and version conflict handling
- set retention and deletion policies for old records
Example prompts for the agent
- Design memory for a support agent that forgets customer preferences between sessions. Two isolated tenants, no shared history.
- Debug why the agent retrieves records from the wrong tenant during embedding search.
- Plan a migration from PostgreSQL to a vector database, keeping source records and verifying tenant isolation.
How to install agent-memory-systems
1Skills CLI (Vercel)
npx skills add sickn33/agentic-awesome-skills --skill agent-memory-systems -a claude-code2Manually: put the files in place
~/.claude/skills/agent-memory-systems/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/agent-memory-systems/
1Skills CLI (Vercel)
npx skills add sickn33/agentic-awesome-skills --skill agent-memory-systems -a codex2Manually: put the files in place
.agents/skills/agent-memory-systems/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add sickn33/agentic-awesome-skills --skill agent-memory-systems -a cursor2Manually: put the files in place
.cursor/skills/agent-memory-systems/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install sickn33/agentic-awesome-skills agent-memory-systems2Manually: put the files in place
.github/skills/agent-memory-systems/SKILL.md1Skills CLI (Vercel)
npx skills add sickn33/agentic-awesome-skills --skill agent-memory-systems -a gemini-cli2Platform CLI
gemini skills install https://github.com/sickn33/agentic-awesome-skills --path skills/agent-memory-systemsManually: put the files in place
.devin/skills/agent-memory-systems/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add sickn33/agentic-awesome-skills --skill agent-memory-systems -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
From the same set80
The whole set →Similar
Questions about agent-memory-systems
How do I install agent-memory-systems in Claude Code?
Run npx skills add sickn33/agentic-awesome-skills --skill agent-memory-systems -a claude-code. The skill will appear in ~/.claude/skills/agent-memory-systems/SKILL.md.
What does agent-memory-systems do?
It guides you through designing agent memory with per-user and per-tenant data isolation. Covers record types, storage adapters, isolation testing, and zero-loss migration.
Do I need to read the entire guide before using the skill?
Yes. The detailed guide contains mandatory safety procedures, prerequisites and validation steps. For narrow tasks, load the relevant section; for end-to-end work, read the full guide.
Source text
SKILL.md · MIT
--- name: agent-memory-systems description: "Design tenant-scoped memory, retrieval and retention for agents. Use when planning RAG, conversation history, vector stores or remembering across sessions." risk: safe source: vibeship-spawner-skills (Apache 2.0) date_added: 2026-02-27 --- # Agent Memory Systems Choose semantic records for facts/preferences, episodic records for events, and procedural records for reusable methods. Keep retrieval quality separate from storage volume and bind persistent access to verified identity. ## Procedure 1. Establish the actual task, authenticated tenant/user, permission to retain content, retention limits and existing store/model versions. 2. Read the guide's tenant-scoped contract and relevant storage/chunking sections. Select an adapter supported by the installed SDK; the guide's historical sketches are not deployable integrations. 3. Specify record IDs, source evidence, timestamps, namespace, retrieval limits and conflict/version policy. Preserve originals and propose consolidation without deletion. 4. Test cross-identity rejection, stale/conflicting records, bounded retrieval and failed writes with isolated fixtures. Benchmark retrieval against held-out questions before expanding storage. 5. Deliver the architecture and evidence-backed change plan, listing unresolved adapters and hosted cost/data destinations. Apply only the persistence or provider operations actually authorized. ## Detailed Guide Read [the detailed guide](references/detailed-guide.md) before executing this skill. It retains the complete procedure and reference material. Treat its safety, prerequisites, and validation requirements as mandatory. For focused work, load the relevant sections; for end-to-end work, read the guide completely. ## When to Use - Design memory namespaces and retention for an agent serving distinct tenants or users. - Diagnose retrieval of stale, conflicting or unauthorized conversation records. - Plan an embedding/store migration while preserving source records and verifying isolation. ## Example **Request:** “Our support agent forgets preferences between sessions. Design memory for two customer tenants without sharing their history.” **Output:** Load the tenant-scoped contract and background-extraction sections. Propose a semantic namespace per verified tenant/user, records with source IDs and revisions, and bounded retrieval. Retain conflicting preferences until the owner resolves them; include tests that tenant B cannot retrieve or consolidate tenant A records. Identify the existing persistent adapter and consent/retention evidence before any write. ## Limitations - Use this skill only when the task clearly matches the scope described above. - Do not treat the output as a substitute for environment-specific validation, testing, or expert review. - Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
© sickn33 · MIT · sickn33/agentic-awesome-skills