Nemo Rl Session Memory
NVIDIAOfficialPublished by NVIDIA
- Skill
- Meta (authoring, orchestration, planning, memory)
- Agent tooling
- Apache-2.0
- Medium risk
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
The nemo-rl-session-memory skill provides a standardized framework for coding agents to persist their working context. By creating a dedicated session directory containing state, timeline, file, and handoff documentation, agents can effectively resume complex tasks after interruptions, VS Code restarts, or branch switches. This skill ensures that critical information—such as current goals, subtasks, and recent decisions—is preserved in a machine-scannable format, reducing context loss and improving handoff efficiency between agent sessions.
What it does
- Establishes a structured directory for storing session-specific context files.
- Provides templates for tracking session state, action timelines, file modifications, and handoff instructions.
- Defines a recovery workflow to verify current repository state against saved session records.
- Sets a rhythm for periodic checkpointing during long-running development tasks.
- Ensures that future agents can quickly understand the current progress and pending actions.
When to use it
- When working on long-running or experimental coding tasks that span multiple sessions.
- Before performing nontrivial code edits or executing complex, multi-step operations.
- When a user explicitly requests to save progress or checkpoint the current agent state.
- When resuming work in a repository that contains existing session documentation.
- Before switching branches or pausing work for an extended period.
Advantages
- Minimizes context loss during agent disconnects or environment restarts.
- Provides a clear, human-readable audit trail of decisions and actions taken.
- Facilitates seamless handoffs between different agent instances.
- Standardizes the documentation of project goals and constraints.
- Encourages proactive verification of repository state during recovery.
Usage examples
- “Save our current progress so I can resume this task later.”
- The agent creates a new directory in the session folder, populates session_state.md, timeline.md, files.md, and handoff.md with the current project status, and confirms the checkpoint is saved.
- “I am back, please recover the context from my last session.”
- The agent identifies the most recent session directory, reads the handoff and state files, verifies the current git status, and provides a summary of the last known subtask and next steps.
Install
Download the skill as a ZIP:
https://autogineer.com/agent-skills/nvidia/nemo-rl-session-memory/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip nemo-rl-session-memory.zip -d .agents/skills
Documentation by NVIDIA
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:
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:
Check for existing session directories:
ls -dt session/* 2>/dev/null | headIf the user is resuming work, read the latest relevant
session_state.md,timeline.md, andhandoff.md.If no relevant session exists, create a new timestamped directory.
Write an initial
session_state.mdwith 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
# Session State
- Session: <session_date_time>
- Repo: <absolute repo path>
- Branch: <branch name>
- Started: <local timestamp>
- Updated: <local timestamp>
## Goal
<Stable overall user goal in one or two sentences. Preserve this across follow-up steering unless the user explicitly changes it.>
## Current Subtask
<Immediate task or steering request currently being handled.>
## Loaded Skills
- `<skill-name>` - <why it was loaded and any important instructions to preserve.>
## Current Status
<What is true now. Include completed work and verification status.>
## Plan
- [ ] <Next concrete step>
- [ ] <Next concrete step>
## Assumptions
- <Assumption and how to verify it if needed.>
## Blockers
- <Blocker or "None known".>timeline.md
# Timeline
## <local timestamp>
- User asked: <brief request>
- Context gathered: <files/commands and key result>
- Decision: <important choice and rationale>
- Result: <edits/tests/outcome>files.md
# Files
## Inspected
- `<path>` - <why it mattered>
## Changed
- `<path>` - <what changed and why>
## Generated
- `<path>` - <purpose>handoff.md
# Handoff
## Resume From Here
<One paragraph summary of the current state.>
## Next Actions
- <Most important next action>
- <Verification or cleanup still needed>
## Watch Outs
- <Risks, user preferences, or repo constraints the next agent must preserve.>Recovery Workflow
When resuming after a disconnect:
Find the likely latest session directory.
Read
handoff.mdfirst, thensession_state.md, then recenttimeline.md.Run lightweight verification such as
git status --short,git branch --show-current, and targeted file reads.Continue from the latest verified next action.
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.
Files
- ATTRIBUTION.mdAdded by AutoGineer843 B
- BENCHMARK.md4.2 KiB
- LICENSELicence file added by AutoGineer11.2 KiB
- SKILL.md5.3 KiB
- evals/evals.json2.8 KiB
- skill-card.md3.7 KiB
- skill.oms.sig4.5 KiB
LICENSE
Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved.
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction,
and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by
the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all
other entities that control, are controlled by, or are under common
control with that entity. For the purposes of this definition,
"control" means (i) the power, direct or indirect, to cause the
direction or management of such entity, whether by contract or
otherwise, or (ii) ownership of fifty percent (50%) or more of the
outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity
exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation
source, and configuration files.
"Object" form shall mean any form resulting from mechanical
transformation or translation of a Source form, including but
not limited to compiled object code, generated documentation,
and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or
Object form, made available under the License, as indicated by a
copyright notice that is included in or attached to the work
(an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object
form, that is based on (or derived from) the Work and for which the
editorial revisions, annotations, elaborations, or other modifications
represent, as a whole, an original work of authorship. For the purposes
of this License, Derivative Works shall not include works that remain
separable from, or merely link (or bind by name) to the interfaces of,
the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including
the original version of the Work and any modifications or additions
to that Work or Derivative Works thereof, that is intentionally
submitted to Licensor for inclusion in the Work by the copyright owner
or by an individual or Legal Entity authorized to submit on behalf of
the copyright owner. For the purposes of this definition, "submitted"
means any form of electronic, verbal, or written communication sent
to the Licensor or its representatives, including but not limited to
communication on electronic mailing lists, source code control systems,
and issue tracking systems that are managed by, or on behalf of, the
Licensor for the purpose of discussing and improving the Work, but
excluding communication that is conspicuously marked or otherwise
designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity
on behalf of whom a Contribution has been received by Licensor and
subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the
Work and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have made,
use, offer to sell, sell, import, and otherwise transfer the Work,
where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s)
with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Work
or a Contribution incorporated within the Work constitutes direct
or contributory patent infringement, then any patent licenses
granted to You under this License for that Work shall terminate
as of the date such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the
Work or Derivative Works thereof in any medium, with or without
modifications, and in Source or Object form, provided that You
meet the following conditions:
(a) You must give any other recipients of the Work or
Derivative Works a copy of this License; and
(b) You must cause any modified files to carry prominent notices
stating that You changed the files; and
(c) You must retain, in the Source form of any Derivative Works
that You distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of
the Derivative Works; and
(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file, excluding those notices that do not
pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and
do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed
as modifying the License.
You may add Your own copyright statement to Your modifications and
may provide additional or different license terms and conditions
for use, reproduction, or distribution of Your modifications, or
for any such Derivative Works as a whole, provided Your use,
reproduction, and distribution of the Work otherwise complies with
the conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade
names, trademarks, service marks, or product names of the Licensor,
except as required for reasonable and customary use in describing the
origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or
agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for determining the
appropriateness of using or redistributing the Work and assume any
risks associated with Your exercise of permissions under this License.
8. Limitation of Liability. In no event and under no legal theory,
whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly
negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special,
incidental, or consequential damages of any character arising as a
result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill,
work stoppage, computer failure or malfunction, or any and all
other commercial damages or losses), even if such Contributor
has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability. While redistributing
the Work or Derivative Works thereof, You may choose to offer,
and charge a fee for, acceptance of support, warranty, indemnity,
or other liability obligations and/or rights consistent with this
License. However, in accepting such obligations, You may act only
on Your own behalf and on Your sole responsibility, not on behalf
of any other Contributor, and only if You agree to indemnify,
defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason
of your accepting any such warranty or additional liability.
END OF TERMS AND CONDITIONS
APPENDIX: How to apply the Apache License to your work.
To apply the Apache License to your work, attach the following
boilerplate notice, with the fields enclosed by brackets "[]"
replaced with your own identifying information. (Don't include
the brackets!) The text should be enclosed in the appropriate
comment syntax for the file format. We also recommend that a
file or class name and description of purpose be included on the
same "printed page" as the copyright notice for easier
identification within third-party archives.
Copyright [yyyy] [name of copyright owner]
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
Requirements and compatibility
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
Security
What our scanner noticed· Medium risk
- Large base64-encoded blobs
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- Published by
- NVIDIA
- Publisher
- NVIDIA (Official)
- Source
- NVIDIA/skills · skills/nemo-rl-session-memory · commit fce3cca
- Licence
- Apache License 2.0 (redistribution allowed)
- LICENSE (added by AutoGineer from LICENSE-APACHE)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
AutoGineer is not affiliated with or endorsed by NVIDIA or NVIDIA.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download nemo-rl-session-memory.zip