Memory
Session management and project memory for multi-session Claude Code projects.
npx -y skills add torarnv/claude-project-manager --skill memoryAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Record a decision, lesson, tool note, or any project knowledge mid-session.
SKILL.md
1.8 KB, 425 tokens by cl100k_base, as published. Nobody here has run it
Memory Skill
Ad-hoc project memory management. Use to record something mid-session without
running a full /end.
Trigger phrases: "remember this", "note that", "record a decision", /cpr:memory.
Memory file semantics
| Content type | File |
|---|---|
| Architectural or design decision | decisions.md |
| Workflow friction or process lesson | lessons.md |
| CLI syntax, missing tool, flag trap, argument quirk | tools.md |
| Update to project goal or scope | spec.md |
| New phase, task, or open question | plan.md |
| Current state update | status.md |
Workflow
Step 1: Identify the target file
Determine where the content belongs using the table above. If ambiguous, ask the user which file is appropriate.
Step 2: Check workspace scope (workspace mode only)
If .memory/tasks/ exists, this is a workspace. Determine whether the content is:
- Cross-task — relevant to future tasks in general → write to root-level file
- Task-specific — relevant only to the current task → write to the task file or task directory
If unclear, ask the user.
Step 3: Write the content
Append to the appropriate file. If the file doesn't exist, create it with frontmatter:
---
name: {{Name}}
description: {{one-liner for MEMORY.md index}}
type: {{decisions|lessons|tools|spec|plan|status}}
---
For lessons.md, include this note at the top if creating for the first time:
_For tool-specific knowledge (CLI syntax, missing tools, flag traps), see [tools.md](tools.md)._
Step 4: Sync index
If a new file was created, add it to .memory/MEMORY.md with a one-line entry:
- [Title](file.md) — one-liner description
Gives 0 of the 12 instructions most memory context skills give in 425 tokens
Counted across 674 of the 847 authors here whose files we hold, read 2026-08-06
- inform the user when setup is completein 21 of 674, across 6 files
- confirm the draft with the user before writingin 21 of 674, across 6 files
- update the agent skills block in place if it existsin 21 of 674, across 6 files
- present findings to the userin 20 of 674, across 5 files
- write the three docs files from seed templatesin 20 of 674, across 5 files
- ask the user about each decision one at a timein 19 of 674, across 4 files
- edit CLAUDE.md if it existsin 18 of 674, across 3 files
- explore current repo statein 18 of 674, across 3 files
- do not overwrite user edits to surrounding sectionsin 18 of 674, across 3 files
- back up the original file before overwritingin 16 of 674, across 8 files
- keep the memory index under 200 linesin 15 of 674
- Provide actionable steps and verificationin 13 of 674, across 2 files
Said here and by no other author read
- determine target file by content type
- check for workspace task directory
- ask user if task scope is unclear
- create file with frontmatter if missing
- add tool note to new lessons file
- append content to appropriate file
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.