[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79FG80ZPBDH7TR1K70RXFSB":3,"skill-same:01M79FG80ZPBDH7TR1K70RXFSB":65},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":14,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M79FG80ZPBDH7TR1K70RXFSB","nemo-rl-session-memory",null,"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.","Elogic360\u002Fsoftware-factory","Elogic360","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F156535519?v=4","01M74NH3F0RB13PWB7JZDE2V80","elogic360","01M74NH3FPC65082MDZVMFHDM3",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Fnemo-rl-session-memory\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: nemo-rl-session-memory\nlicense: Apache-2.0\ndescription: \"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.\"\nwhen_to_use: Preserving or recovering coding-agent context; creating checkpoints for long-running work, handoffs, disconnects, VS Code restarts, branch switches, or nontrivial edits.\n---\n\n# Session Memory\n\nKeep a durable, human-readable record of the current working session so another agent can resume after a disconnect with minimal context loss.\n\n## When To Use\n\nUse this skill when:\n- The user asks to preserve, recover, checkpoint, or manage agent memory.\n- Work is long-running, experimental, or likely to span disconnects.\n- You are about to make nontrivial edits, run long jobs, switch branches, or pause for user input.\n- You resume in a repo that already has `.\u002Fsession\u002F` directories.\n\n## Session Directory\n\nCreate one directory per working session:\n\n```bash\nmkdir -p session\ndate +%Y%m%d_%H%M%S\nmkdir -p session\u002F\u003Csession_date_time>\n```\n\nUse 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.\n\nExpected files:\n- `session_state.md` - overall goal, current subtask, loaded skills, status, plan, assumptions, blockers, and next actions.\n- `timeline.md` - append-only log of major actions, commands, results, and decisions.\n- `files.md` - files inspected, files changed, and why they matter.\n- `handoff.md` - concise resume instructions for the next agent.\n\nAdd other files only when useful, such as `experiments.tsv`, `review_notes.md`, or copied command logs.\n\n## Start Or Resume\n\nAt the start of a session:\n1. Check for existing session directories:\n\n```bash\nls -dt session\u002F* 2>\u002Fdev\u002Fnull | head\n```\n\n2. If the user is resuming work, read the latest relevant `session_state.md`, `timeline.md`, and `handoff.md`.\n3. If no relevant session exists, create a new timestamped directory.\n4. Write an initial `session_state.md` with the user's overall goal, current subtask, loaded skills, repo path, branch, and known constraints.\n\nDo not treat session notes as the only source of truth. Verify important claims against git state, files, and command output before acting.\n\n## Checkpoint Rhythm\n\nWrite a checkpoint:\n- After gathering enough context to form a plan.\n- Before and after meaningful code edits.\n- Before long-running commands, experiments, branch switches, or anything hard to reconstruct from chat.\n- When the user changes direction.\n- Before final response if the session has meaningful state worth resuming.\n- At least every 30 minutes during active long-running work.\n\nPrefer updating the same files rather than creating many small checkpoint files. Keep the record compact and scannable.\n\n## File Templates\n\n### `session_state.md`\n\n```markdown\n# Session State\n\n- Session: \u003Csession_date_time>\n- Repo: \u003Cabsolute repo path>\n- Branch: \u003Cbranch name>\n- Started: \u003Clocal timestamp>\n- Updated: \u003Clocal timestamp>\n\n## Goal\n\u003CStable overall user goal in one or two sentences. Preserve this across follow-up steering unless the user explicitly changes it.>\n\n## Current Subtask\n\u003CImmediate task or steering request currently being handled.>\n\n## Loaded Skills\n- `\u003Cskill-name>` - \u003Cwhy it was loaded and any important instructions to preserve.>\n\n## Current Status\n\u003CWhat is true now. Include completed work and verification status.>\n\n## Plan\n- [ ] \u003CNext concrete step>\n- [ ] \u003CNext concrete step>\n\n## Assumptions\n- \u003CAssumption and how to verify it if needed.>\n\n## Blockers\n- \u003CBlocker or \"None known\".>\n```\n\n### `timeline.md`\n\n```markdown\n# Timeline\n\n## \u003Clocal timestamp>\n- User asked: \u003Cbrief request>\n- Context gathered: \u003Cfiles\u002Fcommands and key result>\n- Decision: \u003Cimportant choice and rationale>\n- Result: \u003Cedits\u002Ftests\u002Foutcome>\n```\n\n### `files.md`\n\n```markdown\n# Files\n\n## Inspected\n- `\u003Cpath>` - \u003Cwhy it mattered>\n\n## Changed\n- `\u003Cpath>` - \u003Cwhat changed and why>\n\n## Generated\n- `\u003Cpath>` - \u003Cpurpose>\n```\n\n### `handoff.md`\n\n```markdown\n# Handoff\n\n## Resume From Here\n\u003COne paragraph summary of the current state.>\n\n## Next Actions\n- \u003CMost important next action>\n- \u003CVerification or cleanup still needed>\n\n## Watch Outs\n- \u003CRisks, user preferences, or repo constraints the next agent must preserve.>\n```\n\n## Recovery Workflow\n\nWhen resuming after a disconnect:\n1. Find the likely latest session directory.\n2. Read `handoff.md` first, then `session_state.md`, then recent `timeline.md`.\n3. Run lightweight verification such as `git status --short`, `git branch --show-current`, and targeted file reads.\n4. Continue from the latest verified next action.\n5. Append a timeline entry noting the recovery and any mismatches found.\n\n## Quality Rules\n\n- Keep notes factual and terse. Future agents need state, not a transcript.\n- Record command outcomes that matter, especially failed tests or skipped verification.\n- Mention uncommitted changes and whether they were made by the current agent or pre-existing.\n- Do not store secrets, tokens, private credentials, or large logs in session files.\n- If a session file becomes large, summarize old details and keep the latest next actions near the top of `handoff.md`.\n","# Session Memory\n\nKeep a durable, human-readable record of the current working session so another agent can resume after a disconnect with minimal context loss.\n\n## When To Use\n\nUse this skill when:\n- The user asks to preserve, recover, checkpoint, or manage agent memory.\n- Work is long-running, experimental, or likely to span disconnects.\n- You are about to make nontrivial edits, run long jobs, switch branches, or pause for user input.\n- You resume in a repo that already has `.\u002Fsession\u002F` directories.\n\n## Session Directory\n\nCreate one directory per working session:\n\n```bash\nmkdir -p session\ndate +%Y%m%d_%H%M%S\nmkdir -p session\u002F\u003Csession_date_time>\n```\n\nUse 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.\n\nExpected files:\n- `session_state.md` - overall goal, current subtask, loaded skills, status, plan, assumptions, blockers, and next actions.\n- `timeline.md` - append-only log of major actions, commands, results, and decisions.\n- `files.md` - files inspected, files changed, and why they matter.\n- `handoff.md` - concise resume instructions for the next agent.\n\nAdd other files only when useful, such as `experiments.tsv`, `review_notes.md`, or copied command logs.\n\n## Start Or Resume\n\nAt the start of a session:\n1. Check for existing session directories:\n\n```bash\nls -dt session\u002F* 2>\u002Fdev\u002Fnull | head\n```\n\n2. If the user is resuming work, read the latest relevant `session_state.md`, `timeline.md`, and `handoff.md`.\n3. If no relevant session exists, create a new timestamped directory.\n4. Write an initial `session_state.md` with the user's overall goal, current subtask, loaded skills, repo path, branch, and known constraints.\n\nDo not treat session notes as the only source of truth. Verify important claims against git state, files, and command output before acting.\n\n## Checkpoint Rhythm\n\nWrite a checkpoint:\n- After gathering enough context to form a plan.\n- Before and after meaningful code edits.\n- Before long-running commands, experiments, branch switches, or anything hard to reconstruct from chat.\n- When the user changes direction.\n- Before final response if the session has meaningful state worth resuming.\n- At least every 30 minutes during active long-running work.\n\nPrefer updating the same files rather than creating many small checkpoint files. Keep the record compact and scannable.\n\n## File Templates\n\n### `session_state.md`\n\n```markdown\n# Session State\n\n- Session: \u003Csession_date_time>\n- Repo: \u003Cabsolute repo path>\n- Branch: \u003Cbranch name>\n- Started: \u003Clocal timestamp>\n- Updated: \u003Clocal timestamp>\n\n## Goal\n\u003CStable overall user goal in one or two sentences. Preserve this across follow-up steering unless the user explicitly changes it.>\n\n## Current Subtask\n\u003CImmediate task or steering request currently being handled.>\n\n## Loaded Skills\n- `\u003Cskill-name>` - \u003Cwhy it was loaded and any important instructions to preserve.>\n\n## Current Status\n\u003CWhat is true now. Include completed work and verification status.>\n\n## Plan\n- [ ] \u003CNext concrete step>\n- [ ] \u003CNext concrete step>\n\n## Assumptions\n- \u003CAssumption and how to verify it if needed.>\n\n## Blockers\n- \u003CBlocker or \"None known\".>\n```\n\n### `timeline.md`\n\n```markdown\n# Timeline\n\n## \u003Clocal timestamp>\n- User asked: \u003Cbrief request>\n- Context gathered: \u003Cfiles\u002Fcommands and key result>\n- Decision: \u003Cimportant choice and rationale>\n- Result: \u003Cedits\u002Ftests\u002Foutcome>\n```\n\n### `files.md`\n\n```markdown\n# Files\n\n## Inspected\n- `\u003Cpath>` - \u003Cwhy it mattered>\n\n## Changed\n- `\u003Cpath>` - \u003Cwhat changed and why>\n\n## Generated\n- `\u003Cpath>` - \u003Cpurpose>\n```\n\n### `handoff.md`\n\n```markdown\n# Handoff\n\n## Resume From Here\n\u003COne paragraph summary of the current state.>\n\n## Next Actions\n- \u003CMost important next action>\n- \u003CVerification or cleanup still needed>\n\n## Watch Outs\n- \u003CRisks, user preferences, or repo constraints the next agent must preserve.>\n```\n\n## Recovery Workflow\n\nWhen resuming after a disconnect:\n1. Find the likely latest session directory.\n2. Read `handoff.md` first, then `session_state.md`, then recent `timeline.md`.\n3. Run lightweight verification such as `git status --short`, `git branch --show-current`, and targeted file reads.\n4. Continue from the latest verified next action.\n5. Append a timeline entry noting the recovery and any mismatches found.\n\n## Quality Rules\n\n- Keep notes factual and terse. Future agents need state, not a transcript.\n- Record command outcomes that matter, especially failed tests or skipped verification.\n- Mention uncommitted changes and whether they were made by the current agent or pre-existing.\n- Do not store secrets, tokens, private credentials, or large logs in session files.\n- If a session file becomes large, summarize old details and keep the latest next actions near the top of `handoff.md`.\n",{"name":5,"license":15,"description":7,"when_to_use":24},"Preserving or recovering coding-agent context; creating checkpoints for long-running work, handoffs, disconnects, VS Code restarts, branch switches, or nontrivial edits.","main","c475fc64e94e803b50d14a791dfee8853fbb2c5c","skills\u002Fnvidia\u002Fnemo-rl-session-memory","https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory","https:\u002F\u002Fgithub.com\u002FElogic360","2026-11-08 22:21:22",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add Elogic360\u002Fsoftware-factory --skill nemo-rl-session-memory",{"tool":37,"command":38},"bunx","bunx skills add Elogic360\u002Fsoftware-factory --skill nemo-rl-session-memory",{"tool":40,"command":41},"pnpm","pnpm dlx skills add Elogic360\u002Fsoftware-factory --skill nemo-rl-session-memory","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Fnemo-rl-session-memory\u002FSKILL.md",true,[45,51,55,59],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"BENCHMARK.md","REFERENCE","参考文档",4259,"https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Fnemo-rl-session-memory\u002FBENCHMARK.md",{"path":52,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":53,"sourceHtmlUrl":54},"evals\u002Fevals.json",2843,"https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Fnemo-rl-session-memory\u002Fevals\u002Fevals.json",{"path":56,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":57,"sourceHtmlUrl":58},"skill-card.md",3798,"https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Fnemo-rl-session-memory\u002Fskill-card.md",{"path":60,"resourceType":61,"resourceTypeDesc":62,"sizeBytes":63,"sourceHtmlUrl":64},"skill.oms.sig","OTHER","其他",4597,"https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Fnemo-rl-session-memory\u002Fskill.oms.sig",[66,73,80,87,94,101],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M79G206MT3J6S0GY3C45P2KV","vss-summarize-video","Use to summarize a recorded video via the LVS summarization microservice (HITL-gated) with a VLM fallback. Not for report generation or live RTSP captioning.","https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Fvss-summarize-video\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M79G1WN63PGRE8CKD47WEBQ5","vss-setup-video-analytics-api","Use to deploy the vss-video-analytics-api REST service standalone (config-source, data-log bind, Elasticsearch, optional Kafka). Not for full warehouse deploy.","https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Fvss-setup-video-analytics-api\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M79G1S9F7VY3EF6H53PRP5AN","vss-setup-behavior-analytics","Use to deploy the vss-behavior-analytics service standalone (entrypoint, config-source, optional calibration). Not for the full warehouse deploy.","https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Fvss-setup-behavior-analytics\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M79G1N1S1Y27PFZPYMNK1MTQ","vss-search-archive","Use this skill to run top-level VSS fusion search on archived video, or to ingest video files \u002F RTSP streams for search. Do NOT use for ad-hoc visual Q&A (use vss-ask-video), live captioning (use vss-deploy-dense-captioning), or video summarization and reports (use vss-summarize-video).","https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Fvss-search-archive\u002FSKILL.md",[],[],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":19},"01M79G1H6WN0Q6C0VCAXCZX6B7","vss-query-analytics","Use this skill when reading video-analytics metrics, incidents, alerts, and sensor data via the VA-MCP server (port 9901). Not for live VLM or incident-range narrative reports.","https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Fvss-query-analytics\u002FSKILL.md",[],[],{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":19},"01M79G1DYPNXQS7QHZ0AAF5FX5","vss-manage-video-io-storage","Use to call the VIOS REST API (sensor list, timelines, clip extraction, snapshots, add\u002Fdelete sensors and streams). Not for VLM inference or search.","https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Fvss-manage-video-io-storage\u002FSKILL.md",[],[]]