メニュー
Session management skill — checkpoint/restore, context compression, progress tracking, and recovery for maintaining continuity across agent sessions.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/lukemcqueen/hermes-cortex --skill session-managerコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SOC 職業分類に基づく
SKILL.md を表示中
| name | session-manager |
| description | Session management skill — checkpoint/restore, context compression, progress tracking, and recovery for maintaining continuity across agent sessions. |
| version | 1.1.0 |
| category | software-development |
| source | hermes-cortex |
| author | Hermes Agent |
| license | MIT |
| platforms | ["linux","macos","windows"] |
| metadata | {"hermes":{"tags":["session","checkpoint","restore","context","progress","tracking","recovery","continuity","state","resume"],"related_skills":["agent-flow","memory-architecture","subagent-driven-development","writing-plans"]}} |
Use this skill to manage long-running or interrupted agent sessions. It provides structured patterns for saving progress, compressing context when approaching token limits, tracking what's been done, and recovering gracefully after interruptions.
Save a compact snapshot of session state at key milestones. Each checkpoint captures what was accomplished, what's pending, and any critical decisions or blockers.
Write a checkpoint to one of these locations (prefer first):
.hermes-cortex/sessions/current.md (repo root, committed to git) — for ongoing work tracked in a shared repo. Update the Session Notes section.session-checkpoint-{timestamp}.md file — for private or long-running work.## Session Checkpoint — YYYY-MM-DD HH:MM UTC
### Objective
What the session was hired to do (one sentence).
### Completed
- [x] Task or sub-task description (file, path, or artifact)
- [x] Another completed item
### In Progress
- [ ] Current active work item
[ ] Next step after current item
Description of blocker (link to error, decision needed, dependency)
Decision / rationale (e.g., "Chose SQLite over PostgreSQL for local dev simplicity")
Another decision
Files modified or created: [list paths]
Commands run with relevant output: [one-liner each]
Tools used: [checkpoint, search, write, patch, etc.]
When starting a new session that follows a previous one:
session-checkpoint-* or look in MEMORY.md.git status, diff on key files).When approaching token limits (typically >70% of your context window), proactively compress before you lose the ability to reason.
Maintain a running, visible list of session progress. Update it after every meaningful action.
### Session Progress
#### ✅ Completed
1. Understood the problem space — identified key requirements
2. Designed the solution architecture — chose library X, decided on pattern Y
3. Implemented core module — wrote `src/core.py`
4. All unit tests pass — 24/24 passed
#### 🔄 In Progress
- Writing integration tests for the API layer (3 of 8 done)
#### ❌ Blocked
- Can't test against staging — no staging environment running; user needs to deploy first
#### 📋 Next Up
- Complete integration tests
- Write documentation
- Logging and error handling pass
If a session is interrupted (timeout, crash, manual stop, user walks away), the next session must be able to resume with minimal friction.
Write a SESSION_RECOVERY.md in the working directory or append to MEMORY.md with:
session-checkpoint-{timestamp}.md (or latest inline checkpoint)main / feature/xyzpython -m pytest tests/src/core.py — was adding error handlingtests/test_core.py — was writing test casesSteps to reproduce any failure or blocker the session was investigating:
git checkout feature/xyzdocker compose up -dpython -m pytest tests/test_core.py::test_foo — expects PASS, got FAILWhat the very next action should be:
Run the failing test again, inspect the traceback, then fix
src/core.pyline 47–55.
# git diff summary — key changes not yet committed
If no recovery file was written before interruption, reconstruct context by:
git reflog or git log --oneline -5 for recent commits.find . -mmin -60).history | tail -50) for the most recent commands.| Situation | Action |
|---|---|
| Task just completed | Write a checkpoint |
| About to do something risky | Write a checkpoint |
| Approaching token limit | Compress → checkpoint → refresh |
| User says "save progress" | Write a checkpoint |
| Session interrupted | Write a recovery file (or reconstruct) |
| New session, need to resume | Find latest checkpoint → load → verify → continue |
| Progress feels muddled | Update progress list before next action |
| Multiple items in flight | Prioritise → move blocked to 📋 Next Up |