View Transitions
thedaviddias/Front-End-Checklist
A skill your agent uses when adding page transition animations, image expand/contract effects, shared-element transitions, or improving navigation UX in a single-page or multi-page application.
Manage entity status transitions in Basic Memory: archive completed work, move notes between status folders, update frontmatter, and handle edge cases.
AGPL-3.0Auto-check passed
Install Memory Lifecycle
$ npx skills add basicmachines-co/basic-memory --skill memory-lifecycle -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install basicmachines-co/basic-memory memory-lifecycle --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/basicmachines-co/basic-memory.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/memory-lifecycle .claude/skills/memory-lifecycle && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "memory-lifecycle" agent skill from https://github.com/basicmachines-co/basic-memory/tree/main/skills/memory-lifecycle into .claude/skills/memory-lifecycle/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "memory-lifecycle", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/basicmachines-co/basic-memory/tree/main/skills/memory-lifecycleType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add basicmachines-co/basic-memory --skill memory-lifecycle -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install basicmachines-co/basic-memory memory-lifecycle --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/basicmachines-co/basic-memory.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/memory-lifecycle .agents/skills/memory-lifecycle && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "memory-lifecycle" agent skill from https://github.com/basicmachines-co/basic-memory/tree/main/skills/memory-lifecycle into .agents/skills/memory-lifecycle/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "memory-lifecycle", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add basicmachines-co/basic-memory --skill memory-lifecycle -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install basicmachines-co/basic-memory memory-lifecycle --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/basicmachines-co/basic-memory.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/memory-lifecycle .cursor/skills/memory-lifecycle && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "memory-lifecycle" agent skill from https://github.com/basicmachines-co/basic-memory/tree/main/skills/memory-lifecycle into .cursor/skills/memory-lifecycle/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "memory-lifecycle", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/basicmachines-co/basic-memory.git --path skills/memory-lifecycle--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add basicmachines-co/basic-memory --skill memory-lifecycle -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install basicmachines-co/basic-memory memory-lifecycle --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/basicmachines-co/basic-memory.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/memory-lifecycle .gemini/skills/memory-lifecycle && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "memory-lifecycle" agent skill from https://github.com/basicmachines-co/basic-memory/tree/main/skills/memory-lifecycle into .gemini/skills/memory-lifecycle/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "memory-lifecycle", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install basicmachines-co/basic-memory memory-lifecycleInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add basicmachines-co/basic-memory --skill memory-lifecycle -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/basicmachines-co/basic-memory.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/memory-lifecycle .github/skills/memory-lifecycle && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "memory-lifecycle" agent skill from https://github.com/basicmachines-co/basic-memory/tree/main/skills/memory-lifecycle into .github/skills/memory-lifecycle/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "memory-lifecycle", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add basicmachines-co/basic-memory --skill memory-lifecycle -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install basicmachines-co/basic-memory memory-lifecycle --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/basicmachines-co/basic-memory.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/memory-lifecycle .opencode/skills/memory-lifecycle && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "memory-lifecycle" agent skill from https://github.com/basicmachines-co/basic-memory/tree/main/skills/memory-lifecycle into .opencode/skills/memory-lifecycle/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "memory-lifecycle", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
memory-lifecycle- GitHub stars
- 4.1k
- Used in
- 1 other repo
- Token cost
- ~1.5k tokens
- SKILL.md length
- 618 words
- Files
- 1
- Skills in repo
- 49
- Repo updated
- First seen
- Licence
- AGPL-3.0
At a glance
Manage entity status transitions in Basic Memory: archive completed work, move notes between status folders, update frontmatter, and handle edge cases.
- Works in 4 steps: Find the Entity → Move the File → Update Frontmatter → …
- Marking items complete
- SKILL.md covers When to Use, Core Principle: Archive, Never…, Folder Conventions and Status Detection, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Memory Lifecycle is an agent skill from basicmachines-co/basic-memory. Manage entity status transitions in Basic Memory: archive completed work, move notes between status folders, update frontmatter, and handle edge cases. Use when marking items complete, archiving old entities, or managing any folder-based status workflow.
Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: AI conversations that actually remember. Never re-explain your project to your AI again. Join our Discord: https://discord.gg/tyvKNccgqN. The licence is AGPL-3.0.
When your agent uses it
- Marking items complete
- Archiving old entities
- Managing any folder-based status workflow
Example prompts
- “/memory-lifecycle”
Requirements
- Python 3
Workflow steps
4 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit cb7407f. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are python).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Memory Lifecycle loads about 1.5k tokens when it runs. Until then it costs about 68 tokens; SKILL.md has 618 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from basicmachines-co/basic-memory at commit cb7407f, republished under its AGPL-3.0 licence (© basicmachines-co). 618 words, ~1,508 tokens.
Download SKILL.mdSave it as
.claude/skills/memory-lifecycle/SKILL.md (or your agent's skills folder).- name
- memory-lifecycle
- description
- Manage entity status transitions in Basic Memory: archive completed work, move notes between status folders, update frontmatter, and handle edge cases. Use when marking items complete, archiving old entities, or managing any folder-based status workflow.
Memory Lifecycle
Manage how entities move through status stages in Basic Memory. The core principle: archive, never delete. Completed work is valuable context — move it out of the active view, but keep it in the knowledge graph.
When to Use
- User says something is "done", "finished", "completed", "submitted", "missed", or "cancelled"
- Moving entities between status folders (active → archive, pipeline → active, etc.)
- Reverting a mistaken completion
- Periodic cleanup of stale active items
Core Principle: Archive, Never Delete
Deleting a note removes it from the knowledge graph — all its observations, relations, and history disappear. Archiving preserves everything while signaling the entity is no longer active.
# Good — entity stays in the knowledge graph
move_note → active/ to archive/
# Bad — knowledge is lost
delete_noteThe only exception: notes created by mistake (typos, true duplicates) can be deleted.
Folder Conventions
Organize entities by status using folders. The exact folder names depend on your domain, but follow a consistent pattern:
entities/
active/ # Currently relevant, in-progress
archive/ # Completed, no longer active, but worth keeping
pipeline/ # Future items, not yet startedFor tasks specifically:
tasks/
active/ # Work in progress
completed/ # Finished workFor any entity type with a clear lifecycle:
[type]/
active/ # Current
[end-state]/ # Whatever "done" means for this typePick folder names that match your domain. The pattern matters more than the specific names.
Status Detection
When the user mentions completion or status change, extract the intent:
| Signal | Status | Action |
|---|---|---|
| "finished", "done", "completed", "shipped" | Complete | Move to archive/completed folder |
| "submitted", "sent", "delivered" | Complete | Move to archive/completed folder |
| "missed", "passed", "skipped", "expired" | Missed | Move to archive or missed folder |
| "cancelled", "abandoned", "killed" | Cancelled | Move to archive folder |
| "paused", "on hold", "deferred" | Paused | Update frontmatter status, keep in place |
| "restarting", "reopening", "reviving" | Reactivate | Move back to active folder |
Workflow
1. Find the Entity
Search Basic Memory with multiple variations to locate the entity:
search_notes(query="quarterly report")
search_notes(query="Q1 report")If multiple matches come back, present options and ask which one.
If no match is found, ask for clarification — don't guess.
2. Move the File
Use move_note to relocate the entity to the appropriate status folder:
move_note(
identifier="tasks/active/quarterly-report",
destination_path="tasks/completed/quarterly-report.md"
)By default the permalink stays the same after a move, so links keep resolving. Projects with update_permalinks_on_move enabled rewrite it from the new path.
3. Update Frontmatter
After moving, merge the new status (and completion date, if the type tracks one) into
frontmatter with the metadata parameter. An append with empty content changes only
the frontmatter:
edit_note(
identifier="quarterly-report",
operation="append",
content="",
metadata={"status": "completed", "completed": "2026-02-22"}
)If the note also carries a - [status] observation, update it too (for example with
find_replace on - [status] active).
4. Confirm
Report what was done concisely:
Marked complete: Quarterly Report
Moved to: tasks/completed/quarterly-report.md
Status: completedEdge Cases
Show full SKILL.md (249 more words)Show less
Already Archived
If the entity is already in an archive/completed folder, notify the user:
"Quarterly Report is already in tasks/completed/. Want me to update anything on it?"
Partial Completion
Sometimes only part of an entity is done. Don't move it — instead, update observations or status notes within the entity to reflect partial progress.
Revert / Reactivate
If something was archived by mistake, move it back:
move_note(
identifier="tasks/completed/quarterly-report",
destination_path="tasks/active/quarterly-report.md"
)
edit_note(
identifier="quarterly-report",
operation="append",
content="",
metadata={"status": "active"}
)Status Without Movement
Some status changes don't require a folder move — "paused" or "blocked" items often stay in active/ with just a frontmatter update. Reserve folder moves for terminal or major state transitions.
Relationship to Other Skills
- memory-tasks: Tasks are a specific lifecycle case. This skill covers the general pattern; memory-tasks covers task-specific fields (steps, current_step, context).
- memory-notes: Use search-before-create (from memory-notes) to find the entity before transitioning it.
- memory-defrag: Periodic defrag can identify stale active items that should be archived.
Guidelines
- Archive, never delete. The knowledge graph benefits from historical context.
- Move first, then update frontmatter. This order ensures the file is in the right place even if the edit step fails.
- Permalinks survive moves by default. Links to the entity keep working after a
move_noteunless the project enablesupdate_permalinks_on_move. - Be concise in confirmations. The user knows their system — just report what changed.
- Ask when ambiguous. If multiple entities match or the target folder isn't clear, ask rather than guess.
- Batch operations are fine. If the user says "archive all completed tasks", find them all, confirm the list, then move them in sequence.
© basicmachines-co, AGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/memory-lifecycle of basicmachines-co/basic-memory.
Open the folder on GitHubat commit cb7407f
Used in 1 other repository
We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in basicmachines-co/basic-memory, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Memory Lifecycle next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Memory Lifecycle this skillbasicmachines-co/basic-memory | 4.1k | 1 repos | ~1.5k | Automated safety check: Pass | AGPL-3.0 | |
| View Transitionsthedaviddias/Front-End-Checklist | 74k | — | ~528 | Automated safety check: Pass | MIT | |
| OpenSpec Bulk Change ArchiverFission-AI/OpenSpec | 71k | 3 repos | ~5.6k | Automated safety check: Pass | MIT | |
| Twenty Syncable Entity Cache and Transformtwentyhq/twenty | 58k | — | ~2.4k | Automated safety check: Pass | Custom licence | |
| Vercel React View Transitionssickn33/agentic-awesome-skills | 47k | 1 repos | ~3.1k | Automated safety check: Pass | MIT | |
| Verification Before Completionforyourhealth111-pixel/Vibe-Skills | 3.6k | — | ~1.1k | Automated safety check: Pass | Apache-2.0 |
Similar skills
OpenSpec Bulk Change Archiver
Fission-AI/OpenSpec
Archives several completed OpenSpec changes in one operation, checking the codebase to resolve spec conflicts rather than archiving blindly.
Twenty Syncable Entity Cache and Transform
twentyhq/twenty
Walks through step 2 of adding a syncable entity to the Twenty server: a cache service for flat entity maps and utilities that transform entities and DTOs into universal flat entities.
Vercel React View Transitions
sickn33/agentic-awesome-skills
Guide React and Next.js view transitions, shared element animations, route transitions, transition types, and reduced-motion-safe UI state animation.
Verification Before Completion
foryourhealth111-pixel/Vibe-Skills
Completion-evidence route used before claiming work is complete, fixed, passing, committed, or PR-ready.
Verification Before Completion
farm-fe/farm
A skill your agent uses when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any…
More from basicmachines-co/basic-memory
All 49 skills in this repocmux Settings Editor
basicmachines-co/basic-memory
Views, sets, unsets and validates cmux settings in ~/.config/cmux/cmux.json with a helper script that checks keys against the schema.
cmux Window and Pane Control
basicmachines-co/basic-memory
End-user control of cmux topology and routing (windows, workspaces, panes/surfaces, focus, moves, reorder, identify, trigger flash). Use when automation needs…
Cmux Markdown Viewer Panel
basicmachines-co/basic-memory
Opens markdown files in a formatted cmux panel beside the terminal that re-renders on every change, handy for plans and task lists.
cmux Workspace Scoping
basicmachines-co/basic-memory
Keeps agent actions scoped to the cmux workspace and terminal that invoked it, and lays out pane and surface commands that avoid disrupting the user's own focus.
Basic Memory Repo Images
basicmachines-co/basic-memory
Produces PR, changelog and two-week retro images for the Basic Memory repository from evidence in PR bodies, saved to fixed paths under docs/assets/infographics.
Logfire Instrumentation
basicmachines-co/basic-memory
Adds Pydantic Logfire tracing, logging and metrics to Python, JavaScript or TypeScript and Rust projects, with the correct setup order and library extras.
Questions about Memory Lifecycle
What does Memory Lifecycle do?
Manage entity status transitions in Basic Memory: archive completed work, move notes between status folders, update frontmatter, and handle edge cases. Memory Lifecycle is an agent skill from basicmachines-co/basic-memory. Manage entity status transitions in Basic Memory: archive completed work, move notes between status folders, update frontmatter, and handle edge cases.
When should I use Memory Lifecycle?
Memory Lifecycle fits situations like: marking items complete; archiving old entities; managing any folder-based status workflow.
How do I install Memory Lifecycle in Claude Code?
Run `npx skills add basicmachines-co/basic-memory --skill memory-lifecycle -a claude-code`. Or copy the skill folder (skills/memory-lifecycle in basicmachines-co/basic-memory) into .claude/skills/memory-lifecycle in your project. Claude Code loads it when a task matches its description.
How do I install Memory Lifecycle in Codex?
Run `npx skills add basicmachines-co/basic-memory --skill memory-lifecycle -a codex`. Or copy the skill folder (skills/memory-lifecycle in basicmachines-co/basic-memory) into .agents/skills/memory-lifecycle in your project. Codex loads it when a task matches its description.
Can I use Memory Lifecycle in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add basicmachines-co/basic-memory --skill memory-lifecycle -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/memory-lifecycle, .gemini/skills/memory-lifecycle, .github/skills/memory-lifecycle and .opencode/skills/memory-lifecycle in your project.
What does Memory Lifecycle need to run?
SKILL.md names no scripts, command-line tools or credentials: Memory Lifecycle is instructions for the agent only. Our summary lists: Python 3.
Does Memory Lifecycle access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Memory Lifecycle safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Memory Lifecycle use?
Memory Lifecycle is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Memory Lifecycle use?
About 1.5k tokens (SKILL.md is roughly 6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Memory Lifecycle?
Skills that share tags, products or a category with Memory Lifecycle: View Transitions (thedaviddias/Front-End-Checklist, 74k stars), OpenSpec Bulk Change Archiver (Fission-AI/OpenSpec, 71k stars), Twenty Syncable Entity Cache and Transform (twentyhq/twenty, 58k stars) and Vercel React View Transitions (sickn33/agentic-awesome-skills, 47k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Memory Lifecycle?
basicmachines-co (a GitHub organization) maintains it in basicmachines-co/basic-memory, which has 4,115 GitHub stars. The repository holds 49 skills in this directory. The repository was last updated on October 7, 2026.
Source: basicmachines-co/basic-memory on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.