recovery
Recover session state from memory-keeper after context loss.
Best use case
recovery is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Recover session state from memory-keeper after context loss.
Teams using recovery should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/recovery/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How recovery Compares
| Feature / Agent | recovery | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Recover session state from memory-keeper after context loss.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Recovery Skill Restore session state from memory-keeper checkpoints after context is lost or when starting a new session. ## When to Use - Starting a new session on existing work - After context was exhausted - When asked "what was I working on?" - When asked to "recover" or "restore" context - After `/clear` or session restart ## Recovery Actions ### 1. Load Recent Context ``` context_get(limit: 50, sort: "created_desc") ``` ### 2. Get Context Summary ``` context_summarize() ``` ### 3. Find Progress Items ``` context_get(category: "progress", limit: 20) ``` ### 4. Find High Priority Items ``` context_get(priority: "high", limit: 10) ``` ### 5. Reconstruct State From the retrieved context, extract: - `current-task`: What was being worked on - `files-modified`: Files that were changed - `implementation-progress`: How far along - `next-action`: What needs to happen next - `blockers`: Any known issues ## Recovery Output Format Present the recovered state clearly: ```markdown ## Session Recovered ### Previous Task <current-task value> ### Progress <implementation-progress value> ### Files Modified <list of files-modified> ### Blockers/Issues <any blockers found> ### Recommended Next Action <next-action value> ### Recent Checkpoints 1. <checkpoint 1 name>: <description> 2. <checkpoint 2 name>: <description> --- Ready to continue. Confirm to proceed with: <next-action> ``` ## Recovery Checklist - [ ] Load all recent context items - [ ] Identify the current/last task - [ ] Find all files that were modified - [ ] Determine progress percentage/phase - [ ] Locate the next action to take - [ ] Check for any blockers - [ ] Verify todo list state if available - [ ] Present summary to user - [ ] Get confirmation before proceeding ## If No Context Found If memory-keeper has no relevant context: ```markdown ## No Previous Context Found No checkpoints or progress items found in memory-keeper. Possible reasons: - This is a new session with no prior work - Previous session did not checkpoint (work may be lost) - Memory was cleared To start fresh, describe what you'd like to work on. ``` ## Partial Recovery If only some context is found: ```markdown ## Partial Recovery Found limited context from previous session: ### Available Information <whatever was found> ### Missing Information - [ ] Current task (not found) - [ ] Files modified (not found) - etc. Would you like to: 1. Continue with available context 2. Start fresh 3. Provide additional context manually ```
Related Skills
planning-disaster-recovery
Execute use when you need to work with backup and recovery. This skill provides backup automation and disaster recovery with comprehensive guidance and automation. Trigger with phrases like "create backups", "automate backups", or "implement disaster recovery".
managing-database-recovery
Process use when you need to work with database operations. This skill provides database management and optimization with comprehensive guidance and automation. Trigger with phrases like "manage database", "optimize database", or "configure database".
github-wayback-recovery
Recover deleted GitHub content using the Wayback Machine and Archive.org APIs. Use when repositories, files, issues, PRs, or wiki pages have been deleted from GitHub but may persist in web archives. Covers CDX API queries, URL patterns, and systematic recovery workflows.
github-commit-recovery
Recover deleted commits from GitHub using REST API, web interface, and git fetch. Use when you have commit SHAs and need to retrieve actual commit content, diffs, or patches. Includes techniques for accessing "deleted" commits that remain on GitHub servers.
cicd-intelligent-recovery
Loop 3 of the Three-Loop Integrated Development System. CI/CD automation with intelligent failure recovery, root cause analysis, and comprehensive quality validation. Receives implementation from Loop 2, feeds failure patterns back to Loop 1. Achieves 100% test success through automated repair and theater validation. v2.0.0 with explicit agent SOPs.
disaster-recovery
Implement disaster recovery and backup strategies for Proxmox. Create and manage backups, test recovery procedures, and ensure business continuity for your infrastructure.
error-recovery
Strategies for handling subagent failures with retry logic and escalation patterns.
Azure Site Recovery Skill
This skill provides expert guidance for Azure Site Recovery. Covers troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, integrations & coding patterns, and deployment. It combines local quick-reference content with remote documentation fetching capabilities.
Daily Logs
Record the user's daily activities, progress, decisions, and learnings in a structured, chronological format.
Socratic Method: The Dialectic Engine
This skill transforms Claude into a Socratic agent — a cognitive partner who guides
Sokratische Methode: Die Dialektik-Maschine
Dieser Skill verwandelt Claude in einen sokratischen Agenten — einen kognitiven Partner, der Nutzende durch systematisches Fragen zur Wissensentdeckung führt, anstatt direkt zu instruieren.
College Football Data (CFB)
Before writing queries, consult `references/api-reference.md` for endpoints, conference IDs, team IDs, and data shapes.