Skip to main content
ZICQ

Skills ZICQ category:Agent Workflows nemo-rl-session-memory

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.

2078 installs

Official URL:skills.sh

What this skill does

Intro in this page language first. The official description stays in its original wording; we do not rewrite SKILL.md.

What it does

Manage durable working-session memory for coding agents

When to use it

Use this skill when:

How agents load it

Per Agent Skills progressive disclosure: name and description load at startup (~100 tokens); the full SKILL.md body loads when the skill activates; scripts/, references/, and assets/ load only as needed. This file's sections: Session Memory; When To Use; Session Directory; Start Or Resume; Checkpoint Rhythm; File Templates.

File analysis

File analysis: instruction-only skill (SKILL.md). The agent loads the full body when activated.

Session MemoryWhen To UseSession DirectoryStart Or ResumeCheckpoint RhythmFile Templates`session_state.md`Session StateGoalCurrent SubtaskLoaded SkillsCurrent Status

· License:Apache-2.0

Source category:skills.sh agent-skill

SKILL.md & Agent activation

Official spec ↗
name
nemo-rl-session-memory
description
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.
License
Apache-2.0
  1. DiscoverThe client exposes names and descriptions to the agent.
  2. ActivateYour request or the task context selects the skill and loads its instructions.
  3. Load resourcesReferenced scripts, documentation and assets are used when needed.

Invocation syntax and available tools depend on your Agent client. Client integration guide ↗

Install this skill

Skills CLI ↗

Choose the target agent and installation scope, keep referenced package files, then verify the skill appears in the client's catalog.

Ask your Agent to install

Copy these instructions to a compatible agent and confirm the target directory matches your client.

Install the agent skill "nemo-rl-session-memory" into my project. The full SKILL.md and official description are at https://zicq.com/en/skills/skl-f96d99317fe45e60-Nemo-Rl-Session-Memory.html
Save it as .cursor/skills/nemo-rl-session-memory/SKILL.md or .claude/skills/nemo-rl-session-memory/SKILL.md and keep the frontmatter name and description exactly as-is.

Full package on GitHub ↗

Install from the terminal · Skills CLI

Requires Node.js and npx. First inspect the repository's skill list to confirm the name.

npx skills add 'https://github.com/nvidia/skills' --list

npx skills add 'https://github.com/nvidia/skills' --skill 'nemo-rl-session-memory'

The CLI lets you choose the agent interactively. The default scope is the project; use -g for user scope. Confirm package availability with the discovery command, then use npx skills list to inspect installed skills.

Readable layout
--- name: nemo-rl-session-memory license: Apache-2.0 description: "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." when_to_use: Preserving or recovering coding-agent context; creating checkpoints for long-running work, handoffs, disconnects, VS Code restarts, branch switches, or nontrivial edits. --- # 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/ ``` 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.md`, `timeline.md`, and `handoff.md`. 3. If no relevant session exists, create a new timestamped directory. 4. Write an initial `session_state.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. - Before final response if the session has meaningful state worth resuming. - At least every 30 minutes during active long-running work. Prefer updating the same files rather than creating many small checkpoint files. Keep the record compact and scannable. ## File Templates ### `session_state.md` ```markdown # Session State - Session: - Repo: - Branch: - Started: - Updated: ## Goal ## Current Subtask ## Loaded Skills - `` - ## Current Status ## Plan - [ ] - [ ] ## Assumptions - ## Blockers - ``` ### `timeline.md` ```markdown # Timeline ## - User asked: - Context gathered: - Decision: - Result: ``` ### `files.md` ```markdown # Files ## Inspected - `` - ## Changed - `` - ## Generated - `` - ``` ### `handoff.md` ```markdown # Handoff ## Resume From Here ## Next Actions - - ## Watch Outs - ``` ## Recovery Workflow When resuming after a disconnect: 1. Find the likely latest session directory. 2. Read `handoff.md` first, then `session_state.md`, then recent `timeline.md`. 3. Run lightweight verification such as `git status --short`, `git branch --show-current`, and targeted file reads. 4. Continue from the latest verified next action. 5. Append a timeline entry noting the recovery and any mismatches found. ## Quality Rules - Keep notes factual and terse. Future agents need state, not a transcript. - Record command outcomes that matter, especially failed tests or skipped verification. - Mention uncommitted changes and whether they were made by the current agent or pre-existing. - Do not store secrets, tokens, private credentials, or large logs in session files. - If a session file becomes large, summarize old details and keep the latest next actions near the top of `handoff.md`.

Related skills

Agent Workflows

Skill Creator

Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that exte…

Agent Workflows

Clawdhub

Use the ClawdHub CLI to search, install, update, and publish agent skills from clawdhub.com. Use when you need to fetch new skills on the fl…

Agent Workflows

Agent Team Orchestration

Orchestrate multi-agent teams with defined roles, task lifecycles, handoff protocols, and review workflows. Use when: (1) Setting up a team …

Agent Workflows

Superpowers

Spec-first, TDD, subagent-driven software development workflow. Use when: (1) building any new feature or app — triggers brainstorm → plan →…