Recover lost context after session compaction or when information from previous sessions is needed. Use when: user mentions "what were we working on", "I lost context", "before the compact", "previous session", or asks about decisions/implementations/discussions that aren't in current context. Also use proactively when you notice references to prior work you lack context for.
Recovers lost context from previous sessions or compaction by searching past conversations. Activates when users ask about prior work, decisions, or implementations that aren't in current context.
/plugin marketplace add omgpointless/aspy/plugin install aspy@aspyThis skill is limited to using the following tools:
advanced-strategies.mdYou've been activated to recover context that was lost to compaction or exists in a previous session.
Identify the topic - What specific context is needed?
Use aspy_recall (primary tool):
aspy_recall(query="<keywords>", limit=10)
This combines semantic search (if embeddings enabled) with keyword matching. Searches thinking blocks, user prompts, AND assistant responses simultaneously. Handles both exact queries and fuzzy queries like "that golf thing?"
Synthesize, don't dump - Summarize findings:
Offer continuity - "Would you like me to continue where we left off?"
aspy_recall_thinking - Claude's reasoning and analysis (WHY decisions were made)aspy_recall_prompts - What the user askedaspy_recall_responses - Claude's answers and codeGood synthesis:
"On Dec 2nd, we implemented mouse scroll support for the detail modal. The fix was in
src/tui/mod.rs:299-322- checking if modal is open before dispatching scroll events. You mentioned wanting to test it before merging."
Bad synthesis:
"Found 5 results mentioning 'scroll'. Here they are: [dumps raw results]"
| User Says | Search For |
|---|---|
| "that bug we fixed" | error keywords, "fix", file names |
| "the refactor" | "refactor", component names |
| "what we decided" | "decided", "approach", "pattern" |
| "before compact" | recent topics from today |
| "something about golf?" | just search it - semantic will handle fuzzy |
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.