Help us improve
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
By xiaolai
Mine past Claude Code conversations for decisions, mistakes, patterns, and wisdom
npx claudepluginhub xiaolai/claude-plugin-marketplace --plugin echo-sleuthAudit Claude Code memories for staleness.
Global memory overview — staleness alerts, token costs, and stats across all projects
Extract durable knowledge from a past Claude Code conversation session.
Extract lessons and wisdom from past Claude Code conversation sessions.
Interactively clean up stale Claude Code memories.
You are the Analyze Agent — the meta-agent that synthesizes wisdom, patterns, and statistics from Claude Code conversation history. You combine all insight categories (decisions, mistakes, patterns, preferences, architecture, cost) into actionable knowledge.
You are the File Historian — an expert at tracing the complete history of a file through both Claude Code conversation sessions and git commits.
You are a memory auditor for Claude Code. Your job is to verify that stored memories
You are the Recall Agent — a unified search and analysis agent for Claude Code conversation history. You handle three overlapping concerns based on what the user needs:
You are the Schema Scout — an expert at probing Claude Code's data files to discover their current structure, detect format changes, and verify that echo-sleuth's scripts remain compatible.
This skill should be used when the user asks to "learn from past sessions", "extract lessons", "find what worked", "identify patterns in my workflow", "what mistakes did I make", "what decisions were made", or wants to synthesize wisdom and actionable insights from conversation history.
This skill should be used when the user asks to "check git history", "trace code changes", "find when something was added", "correlate commits with sessions", "find hotspot files", or needs to mine git repository history for insights. Only applicable when the current project is a git repository.
This skill should be used when the user asks to "analyze conversation history", "parse JSONL files", "read past sessions", "search conversation logs", "find what happened in a session", or needs to work with Claude Code's .jsonl conversation format. It provides the canonical parsing infrastructure for echo-sleuth agents.
Use when auditing, extracting, pruning, or writing Claude Code memory files. Covers memory file format, MEMORY.md index conventions, staleness scoring, claim extraction heuristics, destination routing, mutation rules, and archive conventions.
Uses power tools
Uses Bash, Write, or Edit tools
Has parse errors
Some configuration could not be fully parsed
Share bugs, ideas, or general feedback.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Semantic search for Claude Code conversations. Remember past discussions, decisions, and patterns.
Automatic semantic memory for Claude Code — remembers what you worked on across sessions
Search across Claude Code and OpenClaw session history. Find past conversations, decisions, and code snippets instantly.
Searchable conversation memory - auto-syncs sessions to SQLite with full-text search
Continuous memory for Claude Code. Extracts, summarizes, and compresses conversations into tiered daily logs. Claude remembers what you did yesterday.
Upstash Context7 MCP server for up-to-date documentation lookup. Pull version-specific documentation and code examples directly from source repositories into your LLM context.
Natural-Language Programming Manager — scan, lint, and write NL artifacts with Claude-native quality scoring
A 260-token system prompt that overrides three structural presumptions every RLHF-trained LLM inherits from training: that you want confirmation, that old scarcity still applies, that best practices are ceilings.
English language coach for non-native speakers — auto-corrects prompts, translates non-English, refines with :: prefix, tracks improvement over time
Initialize a multi-agent workspace with shared configuration for Claude Code, Codex CLI, and Gemini CLI
Documentation quality and freshness enforcer — detect staleness, check accuracy, measure coverage, and auto-generate docs
Mine past Claude Code conversations and manage the knowledge lifecycle — search sessions, extract lessons, audit memory staleness, prune token waste.
Echo Sleuth analyzes your Claude Code session history (~/.claude/projects/) and memory files to help you:
Part of the xiaolai plugin marketplace.
Add the marketplace (once):
/plugin marketplace add xiaolai/claude-plugin-marketplace
Then install:
/plugin install echo-sleuth@xiaolai
Install fails with "Plugin not found in marketplace 'xiaolai'"? Your local marketplace clone is stale. Run
claude plugin marketplace update xiaolaiand retry —plugin installdoes not auto-refresh.
| Scope | Command | Effect |
|---|---|---|
| User (default) | /plugin install echo-sleuth@xiaolai | Available in all your projects |
| Project | /plugin install echo-sleuth@xiaolai --scope project | Shared with team via .claude/settings.json |
| Local | /plugin install echo-sleuth@xiaolai --scope local | Only you, only this repo |
When installed as a plugin, commands appear as
/echo-sleuth:<command>(e.g./echo-sleuth:recall).
/recall <topic> [--scope current|all] [--limit N] [--lite]Search past conversations for a topic, decision, or mistake.
/echo-sleuth:recall "why did we choose SQLite"
/echo-sleuth:recall "authentication bug" --scope all
/echo-sleuth:recall "CI setup" --limit 20
/echo-sleuth:recall vitepress --lite
--scope all to search across all projects.--lite skips agent dispatch and synthesis. The slash command runs recall-lite.sh and returns its raw output verbatim — minimum-tokens mode for when you hit billing limits or just want raw evidence. See Lite mode and API usage below./recap [N-sessions|duration] [--detail low|medium|high]Summarize recent sessions.
/echo-sleuth:recap
/echo-sleuth:recap 10
/echo-sleuth:recap 7d --detail high
10) or duration (3d, 1w)low (one-liners), medium (paragraph per session), high (full analysis)/timeline [--limit N] [--since YYYY-MM-DD]Chronological project history combining Claude sessions and git commits.
/echo-sleuth:timeline
/echo-sleuth:timeline --since 2026-03-01 --limit 50
/lessons [topic] [--scope current|all] [--category decisions|mistakes|patterns|all]Extract accumulated wisdom from past sessions.
/echo-sleuth:lessons
/echo-sleuth:lessons "database" --category decisions
/echo-sleuth:lessons --scope all --category mistakes
/dashboardGlobal overview of Claude Code memories across all projects.
/echo-sleuth:dashboard
Shows:
Use this as the entry point to understand your memory landscape before auditing or pruning.
/audit [project] [--deep]Audit memory staleness — quick heuristic scan or deep content verification.
/echo-sleuth:audit
/echo-sleuth:audit pixel-office
/echo-sleuth:audit --deep
/echo-sleuth:audit pixel-office --deep