← ClaudeAtlas

nemo-rl-session-memorylisted

Manage durable working-session memory for coding agents. Use when a user asks to preserve or recover agent context across disconnects, VS Code restarts, long-running work, handoffs, or any session where important state should be written periodically under the repo's session directory. Do NOT use for: simple questions, short tasks, one-off commands, linting, or code review.
yangwhale/CloseCrab · ★ 4 · AI & Automation · score 80
Install: claude install-skill yangwhale/CloseCrab
# Session Memory Keep a durable, human-readable record of the current working session so another agent can resume after a disconnect with minimal context loss. ## When To Use Use this skill when: - The user asks to preserve, recover, checkpoint, or manage agent memory. - Work is long-running, experimental, or likely to span disconnects. - You are about to make nontrivial edits, run long jobs, switch branches, or pause for user input. - You resume in a repo that already has `./session/` directories. ## Session Directory Create one directory per working session: ```bash mkdir -p session date +%Y%m%d_%H%M%S mkdir -p session/<session_date_time> ``` Use local time from the machine. Reuse the same session directory for all checkpoints in the same conversation unless the user explicitly starts a new session. Expected files: - `session_state.md` - overall goal, current subtask, loaded skills, status, plan, assumptions, blockers, and next actions. - `timeline.md` - append-only log of major actions, commands, results, and decisions. - `files.md` - files inspected, files changed, and why they matter. - `handoff.md` - concise resume instructions for the next agent. Add other files only when useful, such as `experiments.tsv`, `review_notes.md`, or copied command logs. ## Start Or Resume At the start of a session: 1. Check for existing session directories: ```bash ls -dt session/* 2>/dev/null | head ``` 2. If the user is resuming work, read the latest relevant `session_state.m