Recovery
全球最大的 Claude Code 技能聚合库 · 收录 3900+ 来自 12+ 来源的技能,提供在线搜索与趋势分析看板 / The world's largest Claude Code skill aggregation hub — 3900+ skills from 12+ sources with online search and trend dashboard
npx -y skills add bg-szy/TOP-SKILLS --skill recoveryAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Recover session state from memory-keeper after context loss.
SKILL.md
2.6 KB, as published. Nobody here has run it
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
/clearor 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 onfiles-modified: Files that were changedimplementation-progress: How far alongnext-action: What needs to happen nextblockers: Any known issues
Recovery Output Format
Present the recovered state clearly:
## 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:
## 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:
## 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