Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
gupsammy avatar

Recall Conversations

  • 36 installs
  • 269 repo stars
  • Updated June 11, 2026
  • gupsammy/claudest

Retrieve past Claude sessions and run analytical lenses to restore context, surface learnings, gaps, decisions, and repeated mistakes across your agent workflow.

About

Recall Conversations is a journey-wide Claude-oriented agent skill for solo builders who accumulate long coding and planning threads and need structured memory without rereading every message. Command recipes in SKILL.md fetch sessions; this lens reference tells the agent which analytical questions to apply and when to deepen search. Restore-context highlights unfinished work and next steps for fresh sessions. Extract-learnings and find-gaps turn repeated confusion into instruction targets. Review-process and run-retro examine whether planning preceded coding and where time leaked. Extract-decisions and find-antipatterns capture trade-offs, rejections, and corrections the user issues more than once—candidates for durable CLAUDE.md rules. Complexity is intermediate because choosing the right lens and follow-up still requires judgment. Use it whenever agent continuity breaks, you suspect repeated mistakes, or you want decisions persisted—across idea research, validate scoping, build implementation, ship review, and operate iteration. It does not replace git history or production monitoring; it augments conversational evidence from your agent tool.

  • Seven lenses: restore-context, extract-learnings, find-gaps, review-process, run-retro, extract-decisions, find-antipatt
  • Per-lens core questions table for what to look for after retrieval
  • Follow-up routing: find-gaps toward learn-anything, extract-decisions toward update-claudemd
  • Supplementary searches when a primary lens returns thin signal
  • Command recipes live in SKILL.md; this reference deepens analysis on retrieved sessions

Recall Conversations by the numbers

  • 36 all-time installs (skills.sh)
  • Ranked #8,638 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
  • Security screen: LOW risk (skills.sh audit)
  • Data as of Aug 4, 2026 (Skillselion catalog sync)
npx skills add https://github.com/gupsammy/claudest --skill recall-conversations

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs36
repo stars269
Security audit3 / 3 scanners passed
Last updatedJune 11, 2026
Repositorygupsammy/claudest

What it does

Retrieve past Claude sessions and run analytical lenses to restore context, surface learnings, gaps, decisions, and repeated mistakes across your agent workflow.

Files

SKILL.mdMarkdownGitHub ↗

Value Context

Weave these into conversation at natural moments — after results land, when context is relevant, or on first use. One or two per run, not all at once.

  • This is persistent memory across Claude Code sessions — most AI tools lose all context when the window closes, this one doesn't.
  • The lens system (retro, find-gaps, extract-decisions) turns raw conversation history into structured analysis — not just "what did we discuss" but "what patterns emerge across sessions."
  • Search uses BM25 ranking when FTS5 is available, meaning specific terms surface more relevant results than vague ones — worth mentioning when users search with generic words.
  • Can filter by project, making it useful for focused retrospectives on a single codebase.
  • The extract-decisions lens can surface CLAUDE.md-worthy rules the user stated but never persisted.

Tools

Two scripts retrieve data:

  • recent_chats.py — retrieve recent sessions (with optional project filter)
  • search_conversations.py — keyword search across sessions (with optional project filter)

Path prefix for both (used in recipes below):

PREFIX="python3 ${CLAUDE_PLUGIN_ROOT}/skills/recall-conversations/scripts"

For the full option catalog, load references/tool-reference.md.

---

Workflow

1. Pick a lens and run its recipe

Each user intent maps to a lens with a full command recipe. Recipes default to the current project — the scripts auto-detect from CWD, so no --project flag is needed for the common case.

User SaysLensRecipe (prepend $PREFIX/)
"where were we", "recap", "continue"restore-contextrecent_chats.py --limit 5 --verbose
"what I learned", "reflect on what I've learned"extract-learningsrecent_chats.py --limit 20
"gaps", "where I'm struggling"find-gapssearch_conversations.py --query "confused struggling help"
"mentor me", "review my process"review-processrecent_chats.py --limit 20 --verbose
"retro", "retrospective", "look back", "post-mortem"run-retrorecent_chats.py --limit 20 --verbose
"decisions", "CLAUDE.md-worthy rules"extract-decisionssearch_conversations.py --query "decided chose trade-off because"
"antipatterns", "bad habits", "mistakes I repeat"find-antipatternssearch_conversations.py --query "again same mistake repeated forgot"

Scope overrides: append --project NAME for a different project (e.g. --project pkm), or --all-projects to widen across everything. Multiple specific projects: --project claudest,pkm.

Example expansion of the run-retro row:

python3 ${CLAUDE_PLUGIN_ROOT}/skills/recall-conversations/scripts/recent_chats.py --limit 20 --verbose

For per-lens questions, follow-ups, and supplementary search patterns, load references/lenses.md.

2. Apply the lens's core question to the retrieved sessions

The recipe gets you the data. The lens tells you what to look for — for instance, run-retro asks "how did the solution evolve, what worked, what was painful". Load references/lenses.md if you need the question for your chosen lens.

3. Deepen if results are thin

  • Retrieve more sessions: bump --limit (1-50 for both scripts; default 5)
  • Search supplementary terms (per-lens patterns in references/lenses.md)
  • Widen scope: append --all-projects to look across projects
  • Two rounds of deepening with no new signal → synthesize from what you have rather than thrashing further

4. Manage volume on broad queries (high blast radius)

The scripts emit full transcripts, so broad/multi-session lenses can flood context. Defend in two tiers — never trigger on session count alone; continuation-restore and specific-lookup lenses stay in-thread regardless of how many sessions match (the answer is small):

1. --summary — append for run-retro, find-gaps, find-antipatterns, extract-decisions, or any --all-projects/multi-week scope. Emits precomputed per-session digests instead of full content (~3× smaller, single-pass, free). The scripts flag when to reach for it: a large full-content pull sets summary_suggested (JSON meta) or prints an INFO: line on stderr. Never use --summary for restore-context or specific lookups — they need exact full text. 2. Fan out — only when even --summary output is still too big: fanout_suggested is true in JSON meta (or the stderr INFO: line recommends fanning out). Spawn one Agent per project (subagent_type: general-purpose, model: sonnet), each running the recipe scoped to its own project and returning a structured digest; then reduce. Shard by project, never by arbitrary session count — count-based splits sever a decision or antipattern thread across agents, and per-project shards preserve cross-session dedup within each mind.

---

Query Construction

Search terms should be content-bearing words that discriminate between sessions — high information value words that are rare enough to rank relevant sessions above irrelevant ones. BM25 ranking (when FTS5 is available) weights rare terms higher automatically.

Include: specific nouns, technologies, concepts, project names, domain terms, unique phrases. More terms improve ranking precision.

Exclude: generic verbs ("discuss", "talk"), time markers ("yesterday"), vague nouns ("thing", "stuff"), meta-conversation words ("conversation", "chat") — these appear in nearly every session and add noise rather than signal.

Algorithm: 1. Extract substantive keywords from user request 2. If 0 keywords, ask for clarification ("Which project specifically?") 3. If 1+ specific terms, search with those terms; project scope is auto-detected — use --project NAME or --all-projects only to override

---

Synthesis

Principles

1. Prioritize significance — 3-5 key findings, not exhaustive lists 2. Be specific — file paths, dates, project names 3. Make it actionable — every finding suggests a response 4. Show evidence — quotes or references 5. Keep it scannable — clear structure, no walls of text

Structure

## [Analysis Type]: [Scope]

### Summary
[2-3 sentences]

### Findings
[Organized by whatever fits: categories, timeline, severity]

### Patterns
[Cross-cutting observations]

### Recommendations
[Actionable next steps]

Length

Default: 300-500 words. Expand only when data warrants it.

Related skills

FAQ

Is Recall Conversations safe to install?

skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.

AI & Agent Buildingagentsautomation

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.