NeMo RL Session Memory

Manage durable working-session memory for coding agents, preserving and recovering context across disconnects, restarts, handoffs and…

You say
Buy it · $59 Read it before you buy $59 Written by NVIDIA · unverified publisher
Context cost
4.1k tokensestimated from the bundle, loaded when it triggers
Bundle
4 files · 16.4 kBtext throughout, nothing executable
Licence
Apache-2.0paid listing
Last change
no release on file
Servers it uses
Noneruns standalone

What it does

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.

Installed, it changes the agent in these ways.

What this skill changes about the agent is not written down here yet. The listing was collected from its source, and the description is in its own SKILL.md.

Workflow

Runs a procedure end to end.

memorysessioncheckpointcontext

The skill itself

This is the whole product. A skill is instructions the model reads, so there is nothing behind the listing you cannot see first — the front matter loads with every session, and the body below it loads when the skill triggers.

SKILL.md5.5 kB · 162 lines
--- 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. ---
8# Session Memory
9
10Keep a durable, human-readable record of the current working session so another agent can resume after a disconnect with minimal context loss.
11
12## When To Use
13
14Use this skill when:
15- The user asks to preserve, recover, checkpoint, or manage agent memory.
16- Work is long-running, experimental, or likely to span disconnects.
17- You are about to make nontrivial edits, run long jobs, switch branches, or pause for user input.
18- You resume in a repo that already has ./session/ directories.
19
20## Session Directory
21
22Create one directory per working session:
23
24```bash
25mkdir -p session
26date +%Y%m%d_%H%M%S
27mkdir -p session/<session_date_time>
28```
29
30Use 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.
31
32Expected files:
33- session_state.md - overall goal, current subtask, loaded skills, status, plan, assumptions, blockers, and next actions.
34- timeline.md - append-only log of major actions, commands, results, and decisions.
35- files.md - files inspected, files changed, and why they matter.
36- handoff.md - concise resume instructions for the next agent.
37
38Add other files only when useful, such as experiments.tsv, review_notes.md, or copied command logs.
39
40## Start Or Resume
41
42At the start of a session:
431. Check for existing session directories:
44
45```bash
46ls -dt session/* 2>/dev/null | head
47```
48
492. If the user is resuming work, read the latest relevant session_state.md, timeline.md, and handoff.md.
503. If no relevant session exists, create a new timestamped directory.
514. Write an initial session_state.md with the user's overall goal, current subtask, loaded skills, repo path, branch, and known constraints.
52
53Do not treat session notes as the only source of truth. Verify important claims against git state, files, and command output before acting.
54
55## Checkpoint Rhythm
56
57Write a checkpoint:
58- After gathering enough context to form a plan.
59- Before and after meaningful code edits.
60- Before long-running commands, experiments, branch switches, or anything hard to reconstruct from chat.
61- When the user changes direction.
62- Before final response if the session has meaningful state worth resuming.
63- At least every 30 minutes during active long-running work.
64
65Prefer updating the same files rather than creating many small checkpoint files. Keep the record compact and scannable.
66
67## File Templates
68
69### session_state.md
70
71```markdown
72# Session State
73
74- Session: <session_date_time>
75- Repo: <absolute repo path>
76- Branch: <branch name>
77- Started: <local timestamp>
78- Updated: <local timestamp>
79
80## Goal
81<Stable overall user goal in one or two sentences. Preserve this across follow-up steering unless the user explicitly changes it.>
82
83## Current Subtask
84<Immediate task or steering request currently being handled.>
85
86## Loaded Skills
87- <skill-name> - <why it was loaded and any important instructions to preserve.>
88
89## Current Status
90<What is true now. Include completed work and verification status.>
91
92## Plan
93- [ ] <Next concrete step>
94- [ ] <Next concrete step>
95
96## Assumptions
97- <Assumption and how to verify it if needed.>
98
99## Blockers
100- <Blocker or "None known".>
101```
102
103### timeline.md
104
105```markdown
106# Timeline
107
108## <local timestamp>
109- User asked: <brief request>
110- Context gathered: <files/commands and key result>
111- Decision: <important choice and rationale>
112- Result: <edits/tests/outcome>
113```
114
115### files.md
116
117```markdown
118# Files
119
120## Inspected
121- <path> - <why it mattered>
122
123## Changed
124- <path> - <what changed and why>
125
126## Generated
127- <path> - <purpose>
128```
129
130### handoff.md
131
132```markdown
133# Handoff
134
135## Resume From Here
136<One paragraph summary of the current state.>
137
138## Next Actions
139- <Most important next action>
140- <Verification or cleanup still needed>
141
142## Watch Outs
143- <Risks, user preferences, or repo constraints the next agent must preserve.>
144```
145
146## Recovery Workflow
147
148When resuming after a disconnect:
1491. Find the likely latest session directory.
1502. Read handoff.md first, then session_state.md, then recent timeline.md.
1513. Run lightweight verification such as git status --short, git branch --show-current, and targeted file reads.
1524. Continue from the latest verified next action.
1535. Append a timeline entry noting the recovery and any mismatches found.
154
155## Quality Rules
156
157- Keep notes factual and terse. Future agents need state, not a transcript.
158- Record command outcomes that matter, especially failed tests or skipped verification.
159- Mention uncommitted changes and whether they were made by the current agent or pre-existing.
160- Do not store secrets, tokens, private credentials, or large logs in session files.
161- If a session file becomes large, summarize old details and keep the latest next actions near the top of handoff.md.
162
In the file
SKILL.md819 words
Files4
LicenceApache-2.0
Why you can read it

Nothing in a skill executes. The client loads the text and the model follows it, so a skill can be audited the way a runbook is — by reading it.

What it costs in context

Skills are not billed by the call. They are paid for in context: every token the instructions occupy is a token your code, your diff and your conversation cannot use. Here is what this one takes and when it takes it.

≈160
always loaded
The name and description, so the model knows the skill exists and when to reach for it.
3,940
on trigger
The instruction body and 3 supporting files, read only when the skill fires.
2.1%
of a 200k window
Ten skills this size would take about 21% of the window before you open a file.
050k100k150k200k context window

4.1k tokens, estimated from the bundle at four bytes to the token, held for the rest of the session once it triggers. Heavy. Teams tend to install this one per project rather than globally, and load it only when the job comes up.

Servers bill, skills cost

A server charges by the month. A skill charges once per session, in context, and then keeps charging it for as long as the session lives.

Before and after

The same question, put to the same model twice: once as it comes, and once with these instructions loaded.

No worked example has been published for this skill yet.

Adoption
Installsnone yet
Ratingno reviews yet

The procedure it runs

The procedure has not been published here. It is in the skill’s own SKILL.md, which its author has not sent to the marketplace yet.

Prose, not code

These steps are written for a model to follow, not executed by a runtime. It can still be told to skip one, and it will say so when it does.

Servers it uses

None. This skill calls no MCP servers at all.

Everything it needs is in the instructions, so it works in a project with nothing connected — the model reads the file and changes how it works with what it can already reach.

It writes no files and reaches no network. All it changes is how the model reasons and writes.

What it asks for
Writes filesno
Network accessno

Read from the allowed-tools line of this skill’s own SKILL.md. A skill grants no permissions of its own — it can only ask for tools your client already has.

What it will not do

Every skill is narrow, and the useful ones say where they stop. These are the jobs this one is the wrong tool for.

What this skill is not for has not been published here. Nothing is implied by that: it is a section the author has not filled in.

What is in the bundle

4 files, 16.4 kB on disk. A bundle is text throughout: the instructions the model reads, plus the templates it fills in.

  • BENCHMARK.md4.3 kB
  • SKILL.md5.5 kB
  • skill-card.md3.8 kB
  • evals/evals.json2.8 kB
What is not in it

No dependencies and nothing executable: a skill is text the agent reads, so the bundle is 4 files you can review in full before installing. The Apache-2.0 licence covers the templates and examples as well as the instructions.

Install

Installing copies the bundle into your project. Nothing runs at install time — the files sit on disk until the model reads them.

$59 once
NeMo RL Session Memory · Apache-2.0 · NVIDIA
one-time
Price$59 once
LicenceApache-2.0 — the author’s, unchanged by this purchase
Paid throughStripe, once, on the card you add at the checkout
Keeps workingfor good — the files are yours once they are on disk
Updatesevery update its author ships, delivered through this account

You can read the whole bundle before paying — the SKILL.md above is the product, not a preview of it. What the money buys is the delivery: the folder packaged and handed to your machine by key, every update its author ships, and our support if it does not do what this listing says. The terms of use are Apache-2.0, set by the author and unchanged by buying it here.

Payment runs through Stripe, on a page like this one rather than a redirect. Once there is an account it joins the same mcprush invoice as everything else you run, so there is never a second card to enter.

Which clients pick it up on their own

A skill is a folder of text. A client with a skills folder reads it without being told; everywhere else the same text works, it is just handed to the model rather than found.

Claude Code.claude/skills/
Claude Desktop
ChatGPT
Cursor.cursor/skills/
VS Code.github/skills/
Codex CLI.agents/skills/
Gemini CLI.gemini/skills/
Grok.grok/skills/
Zed.agents/skills/
Windsurf.windsurf/skills/
Agent SDK.claude/skills/
HTTP / API
This release
Versionnot versioned
Publishedno release date on file
Price$59
Referencenvidia/nemo-rl-session-memory

Versions

Its author publishes no version number, so there is nothing here to pin to: what you install is the folder as it stands today. Instructions change more often than APIs do — a skill can be rewritten entirely without anything it depends on moving.

v
  • No earlier releases have been published to the marketplace.
Pinning

Nothing to pin to: this skill carries no version number of its own. What you install is what the folder holds on the day you install it.

Reviews

no reviews yet · no installs yet

Nobody has reviewed this skill yet. The rating is the mean of the reviews written here, so there is none until somebody writes the first.

Who can post

Only accounts that have had the skill installed for fourteen days, so a review is written after living with it rather than after reading it. Publishers may reply once.

Publisher
Servers0