memory-lifecycle · basicmachines-co — Claude Code skill: what it does, how to install
Automates note status transitions in Basic Memory. It archives completed work into appropriate folders and updates frontmatter without deleting records.
npx skills add basicmachines-co/basic-memory --skill memory-lifecycle -a claude-codeWhat memory-lifecycle does
The skill handles status changes for entities in Basic Memory when you mark work as finished, cancelled, or reopened. Its core approach relies on archiving rather than deleting. Deleting a note via bm_delete destroys observations and turns incoming references into broken links. Instead, the workflow locates the target file with bm_search and moves it to the appropriate folder using bm_move.
Once relocated, the note receives updated frontmatter fields via bm_edit using the set_metadata command. The main body text stays untouched. If a file contains locked: true in its frontmatter, it moves to the destination path, but metadata edits are refused. You must unlock such files manually. Permalinks survive directory changes by default unless the project sets update_permalinks_on_move.
What it helps with
- archive completed tasks and entities without breaking links
- update frontmatter status and completion timestamps safely
- reactivate previously archived notes back into active directories
- keep historical context and observations inside the knowledge graph
Example prompts for the agent
- Mark the quarterly report task as completed and archive it
- We cancelled the migration ticket, move it out of active
- Reopen the client onboarding note and restore it to active
How to install memory-lifecycle
1Skills CLI (Vercel)
npx skills add basicmachines-co/basic-memory --skill memory-lifecycle -a claude-code2Manually: put the files in place
~/.claude/skills/memory-lifecycle/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/memory-lifecycle/
1Skills CLI (Vercel)
npx skills add basicmachines-co/basic-memory --skill memory-lifecycle -a codex2Manually: put the files in place
.agents/skills/memory-lifecycle/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add basicmachines-co/basic-memory --skill memory-lifecycle -a cursor2Manually: put the files in place
.cursor/skills/memory-lifecycle/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install basicmachines-co/basic-memory memory-lifecycle2Manually: put the files in place
.github/skills/memory-lifecycle/SKILL.md1Skills CLI (Vercel)
npx skills add basicmachines-co/basic-memory --skill memory-lifecycle -a gemini-cli2Platform CLI
gemini skills install https://github.com/basicmachines-co/basic-memory --path skills/memory-lifecycleManually: put the files in place
.devin/skills/memory-lifecycle/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add basicmachines-co/basic-memory --skill memory-lifecycle -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about memory-lifecycle
How to install memory-lifecycle in Claude Code?
Run npx skills add basicmachines-co/basic-memory --skill memory-lifecycle -a claude-code in your terminal.
Why does memory-lifecycle archive notes instead of deleting them?
Deleting removes observations and breaks links from other notes in the knowledge graph. Moving items to an archive keeps the graph intact while clearing the active view.
How does the skill handle notes with locked frontmatter?
A note with locked: true still moves to the target folder, but the metadata update step is rejected. You will need to edit the file manually to change its status.
Similar skills
All skills for Notes, tasks and projects →memory-lifecycle by other authors comes first.