recover-context
Reviews session history and worklogs to help developers resume tasks and identify previously modified files.
Install
mkdir -p .claude/skills/recover-context && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/3503" && unzip -o skill.zip -d .claude/skills/recover-context && rm skill.zipInstalls to .claude/skills/recover-context
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Extract full context of the last task from the most recent parent sessionKey capabilities
- →Session lineage traversal
- →Task status extraction from sub-agents
- →Documentation and worklog cross-referencing
- →Last-session decision summary generation
How it works
Delegates analysis to a sub-agent to parse the session history file and identify relevant work artifacts without loading full history into context.
Inputs & outputs
When to use recover-context
- →Resume a blocked task
- →Identify pending items from last session
- →Extract key decisions from session history
About this skill
recover-context
Use this skill to extract context from a parent session when a session lineage is present (shown in the first user message of this conversation).
Instructions
-
Identify the most recent parent session from the lineage chain (the last file in the chronological list).
-
Use sub-agents to explore (to avoid bloating your own context):
- If you have the Task tool with subagent support, use the
session-searchersubagent (subagent_type:session-searcher) to analyze the most recent session - If sub-agents are NOT available, use the
aichat:session-searchskill instead
- If you have the Task tool with subagent support, use the
-
Extract the following from the most recent session:
- What was the last task being worked on?
- What was the current state of that task (completed, in-progress, blocked)?
- Any pending items or next steps mentioned?
- Key decisions made or approaches chosen
-
Also check for associated documents:
- Issue specs or task descriptions referenced in the session
- Any markdown files created during that session (check WORKLOG/, issues/, etc.)
- Code files that were being modified
-
Report back concisely:
- State your understanding of the task context
- List any files you found that are relevant
- Ask the user how they'd like to proceed
Example Sub-agent Prompt
If using the Task tool with session-searcher subagent:
Analyze the session file at [path from lineage] and extract:
1. The last task being worked on (look at the final 20-30 messages)
2. Current state of that task
3. Any referenced markdown files (issue specs, work logs, etc.)
4. Pending next steps or blockers
Return a concise summary.
Constraints
- Do NOT read large session files directly into your own context
- ALWAYS delegate to sub-agents or the session-search skill
- Keep your summary concise - the user knows what they were working on
- Focus on the LAST task, not the entire session history
When not to use it
- →Current session tasks
- →General repository exploration
- →New project bootstrapping
Limitations
- →Requires valid session lineage metadata
- →Relies on accuracy of sub-agent parsing
- →Cannot recover deleted task context
How it compares
Uses targeted sub-agent retrieval instead of bloating the current agent memory with historical files.
Compared to similar skills
recover-context side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| recover-context (this skill) | 1 | 7mo | No flags | Intermediate |
| linear | 10 | 2mo | No flags | Beginner |
| zapier-workflows | 11 | 8mo | Review | Beginner |
| attio-skill-generator | 7 | 7mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by pchalasani
View all by pchalasani →You might also like
linear
lobehub
Linear issue management guide. Use when working with Linear issues, creating issues, updating status, or adding comments. Triggers on Linear issue references (LOBE-xxx), issue tracking, or project management tasks. Requires Linear MCP tools to be available.
zapier-workflows
davila7
Manage and trigger pre-built Zapier workflows and MCP tool orchestration. Use when user mentions workflows, Zaps, automations, daily digest, research, search, lead tracking, expenses, or asks to "run" any process. Also handles Perplexity-based research and Google Sheets data tracking.
attio-skill-generator
kesslerio
Generate use-case-specific Attio workflow skills from templates. Use when creating new skills for lead qualification, deal management, customer onboarding, or custom Attio workflows.
automation-brainstorm
MacroMan5
Interactive workflow design advisor for Power Automate, n8n, Make, Zapier and other platforms. Guides users through planning automation workflows with smart questions about triggers, actions, data flow, and error handling. Uses research sub-agent to find best practices and generates detailed implementation plan. Triggers when user mentions "create workflow", "build flow", "design automation", "need ideas for", or describes workflow requirements without having a complete design.
daily-briefing
anthropics
Start your day with a prioritized sales briefing. Works standalone when you tell me your meetings and priorities, supercharged when you connect your calendar, CRM, and email. Trigger with "morning briefing", "daily brief", "what's on my plate today", "prep my day", or "start my day".
jira
davila7
Use when the user mentions Jira issues (e.g., "PROJ-123"), asks about tickets, wants to create/view/update issues, check sprint status, or manage their Jira workflow. Triggers on keywords like "jira", "issue", "ticket", "sprint", "backlog", or issue key patterns.