A four-destination routing skill for clean Claude assistant continuity across sessions, built on Notion as the persistence layer.
Assistants fail continuity in three ways: they forget too much, save too much junk, or collapse sessions, recurring duties, and reference knowledge into one unmanageable pile. This skill solves that.
| Destination | Purpose | Hard Limits |
|---|---|---|
| Claude Sessions | Session summaries, decisions, next actions, open loops | Under 300 words per entry |
| Standing Orders | Recurring duties, scheduled reports, watch tasks | Must have cadence + expected output |
| Category Pages | Research, plans, SOPs, long-form knowledge | No word limit — use pages |
| Durable Memory | Stable preferences, constraints, operating rules | ≤20 bullets total |
| Say this | What happens |
|---|---|
"log this session" |
Writes session summary now |
"summarize what we did" |
Writes session summary now |
"create a handoff" |
Writes handoff-focused session log |
"what did we decide?" |
Surfaces decisions from this session |
"what are my next actions?" |
Lists next actions from session log |
"what's still open?" |
Lists open loops |
"end of session" |
Triggers full end-of-session routine |
| (3+ meaningful exchanges) | Writes session log automatically — no prompt needed |
| Say this | What happens |
|---|---|
"remember this for future sessions" |
Saves to Durable Memory |
"always do X" |
Saves operating rule |
"never do X" |
Saves constraint |
"my preference is X" |
Saves preference |
"this is a standing rule" |
Saves to Durable Memory |
"update my memory" |
Reviews and updates Durable Memory |
| Say this | What happens |
|---|---|
"track this weekly" |
Creates Standing Order (weekly cadence) |
"watch for X" |
Creates Standing Order (monitoring) |
"check this every Monday" |
Creates Standing Order (scheduled) |
"report on X daily" |
Creates Standing Order (scheduled report) |
"add this to my recurring duties" |
Creates Standing Order |
"remind me to do X every week" |
Creates Standing Order |
"monitor X and alert me when..." |
Creates Standing Order (conditional) |
| Say this | What happens |
|---|---|
"save this research" |
Saves to Research category page |
"document this process" |
Saves to SOPs category page |
"save this plan" |
Saves to relevant category page |
"log today's work" |
Saves to Daily Logs category page |
"this is a guide / SOP / audit" |
Saves to appropriate category page |
| Say this | What happens |
|---|---|
"clean up my Durable Memory" |
Reads page, removes bloat, reports count |
"audit my Standing Orders" |
Lists all orders, flags stale ones |
"archive old sessions" |
Identifies closed sessions 90+ days old |
"run quarterly review" |
Steps through full maintenance checklist |
"check my memory count" |
Reports current bullet count in Durable Memory |
- Clone or download this repo
- Copy the
assistant-memory-osfolder into your Claude Code skills directory:~/.claude/skills/assistant-memory-os/ - Restart Claude Code — the skill activates on trigger phrases automatically
Paste the contents of SKILL.md into your system prompt or Claude project instructions. Reference the other files as needed.
See references/quick-start.md for step-by-step Notion setup.
The short version:
- Create a Claude Sessions database in Notion
- Create a Standing Orders database in Notion
- Create a Durable Memory page in Notion
- Create Category Pages (Research, Ops, Ideas — add more as needed)
- Tell Claude your database names: "I've set up my assistant memory OS. Claude Sessions is [name], Standing Orders is [name]..."
- Claude saves routing rules to Durable Memory and starts routing automatically
| File | Purpose |
|---|---|
SKILL.md |
Core skill — routing model, triggers, operating rules |
references/routing-rules.md |
Decision tree, trigger phrases, ambiguous case resolution |
references/schemas.md |
Notion database schemas for all four destinations |
references/anti-bloat.md |
What not to save, warning signs, cleanup rules |
references/notion-layouts.md |
4 workspace layouts: minimal, standard, hybrid, team |
references/examples.md |
Good and bad examples for every layer |
references/quick-start.md |
30-minute first-time setup guide |
references/notion-mcp-calls.md |
MCP call templates for all Notion write operations |
references/maintenance.md |
Quarterly review checklist, cleanup commands, benchmarks |
Notion-First — all four layers live in Notion databases and pages.
Hybrid (recommended for developers) — Durable Memory stays local (MEMORY.md or Claude Code's memory system); Session Logs, Standing Orders, and Category Pages live in Notion.
Minimal — Claude Sessions DB + one Durable Memory page + Standing Orders DB + three category folders (Research, Ops, Ideas).
- Session logs: under 300 words. Summaries, not transcripts.
- Durable Memory: ≤20 bullets. Rules that change behavior, not a diary.
- Standing Orders: every order must have a cadence and expected output.
- Category Pages: link from session logs, never duplicate content.
- No "Recommendations" or "Misc" buckets — route everything specifically.
MIT