Recover session state from memory-keeper after context loss.
Restores session state from memory-keeper checkpoints after context loss or when starting new sessions. Automatically triggered when continuing existing work, after context exhaustion, or when users ask to recover/restore context.
/plugin marketplace add Barnhardt-Enterprises-Inc/quetrex-claude/plugin install barnhardt-enterprises-inc-quetrex-claude@Barnhardt-Enterprises-Inc/quetrex-claudeThis skill inherits all available tools. When active, it can use any tool Claude has access to.
Restore session state from memory-keeper checkpoints after context is lost or when starting a new session.
/clear or session restartcontext_get(limit: 50, sort: "created_desc")
context_summarize()
context_get(category: "progress", limit: 20)
context_get(priority: "high", limit: 10)
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 issuesPresent 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>
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.
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
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.