Agent skill · NVIDIA
nemo-rl-session-memory
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.
What it needs
About 3k tokens when loaded.
What this skill does
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: 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: sessionstate.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, reviewnotes.md, or copied command logs. Start Or Resume At the start of a session: 1. Check for existing session directories: 2. If the user is resuming work, read the latest relevant sessionstate.md, timeline.md, and handoff.md. 3. If no relevant session exists, create a new timestamped directory. 4. Write an initial sessionstate.md with the user's overall goal, current subtask, loaded skills, repo path, branch, and known constraints. Do not treat session notes as the only source of truth. Verify important claims against git state, files, and command output before acting. Checkpoint Rhythm Write a checkpoint: After gathering enough context to form a plan. Before and after meaningful code edits. Before long-running commands, experiments, branch switches, or anything hard to reconstruct from chat. When the user changes direction. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills NVIDIA/nemo-rl-session-memory