Install
$ agentstack add skill-awrshift-claude-memory-kit-claude-memory-kit ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Claude Memory Kit v4
Persistent memory for Claude Code agents. Layered memory, agent-driven promotion, zero manual file editing.
Two core invariants
- User only talks. Agent captures, proposes, writes. Every architectural decision passes this test.
- Every memory entry carries a
[YYYY-MM-DD]date tag. This is what lets/close-daydetect cross-session repetition and propose promotions.
What's different from v3.2
- Agent-driven promotion ritual via
/close-day(was: backgroundpromote-patterns.pydetection +flush.pyauto-flush, both killed as unreliable and invariant-violating) - Multi-project isolation via
projects//— shared layers load always, per-project scope on demand experiments/-YYYYMMDD/sandbox layer next toprojects/— different lifecycle, no direct promotion to rules- Date-tagging promoted to a documented load-bearing invariant (was implicit machinery, now stated)
- Killed:
experiences/staging layer,promote-patterns.py+flush.pybackground scripts,playbooks/and-guidance/reference-skill seeds, the/memory-auditand/memory-compileoperators, and theknowledge/connections/+knowledge/meetings/subdirs. The role-guidance pattern still works if you add it per-project (see.kit/ARCHITECTURE.md§ "Adding role-guidance yourself"); the kit just doesn't ship templates. - Default surface trimmed to two operators (
/close-day+/tour). The wiki-maintenance commands (/memory-lint,/memory-query) plus a usage-telemetry tool (/memory-usage) moved to opt-in.kit/advanced/— see its README to enable.
See [.kit/CHANGELOG.md](.kit/CHANGELOG.md) for full migration notes.
Quick start
git clone https://github.com/awrshift/claude-memory-kit.git my-project
cd my-project
claude
First session: agent greets you, asks 2-3 setup questions, loads you in. Type /tour for a guided walkthrough.
Daily workflow
- Open a session — hooks auto-load NSP + MEMORY + knowledge index
- Work normally — agent captures patterns in MEMORY.md as you speak
/close-daywhen done — agent synthesizes today, audits for promotions, proposes verbally, writes on your verbal "yes"
Tomorrow starts where today left off.
Included skills
Default — the whole daily loop:
| Skill | Description | |---|---| | /close-day | End-of-day audit ritual: synthesis + promotion proposals. Auto-backfills missed working days from git history. | | /tour | Interactive guided walkthrough on your own files |
Opt-in (.kit/advanced/, copy into .claude/ to enable):
| Skill | Description | |---|---| | /memory-usage | Read-only telemetry: hot files vs cold archival candidates | | /memory-lint | Structural hygiene (broken links, sparse articles, orphans) | | /memory-query | Natural-language search across the knowledge base |
Architecture
Memory lives in layers, each answering a different question:
| Layer | Answers | Written by | |---|---|---| | daily/YYYY-MM-DD.md | «what happened today» | agent via /close-day | | .claude/memory/MEMORY.md | «what patterns repeat across sessions» | agent as you speak | | knowledge/concepts/*.md | «facts and rationale by topic» | agent after your "yes" on /close-day | | .claude/rules/*.md | «what must always / never happen» | agent after a long-stable pattern |
Promotion runs liquid → amber → crystal: an observation in daily/ becomes a date-tagged pattern in MEMORY.md, which /close-day may promote to a knowledge/concepts/ article or a .claude/rules/ constraint — always agent-written, always on your verbal confirmation.
See [.kit/ARCHITECTURE.md](.kit/ARCHITECTURE.md) for full details and [CLAUDE.md](CLAUDE.md) for the agent's session workflow.
Built from production use
Iteration on 700+ real sessions across 7+ projects. Every component earns its place; experiences/, background-detection scripts, and generic role-guidance seeds didn't survive review.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: awrshift
- Source: awrshift/claude-memory-kit
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.