$ loading_
Search past Claude Code chats to recover facts, decisions, and context.
The material indicates an open-source, prompt/document-oriented skill with no declared secrets, remote endpoints, or extra system privileges, so overall risk appears low. Caution is only warranted in verifying how any accompanying local search script accesses archived conversation data.
The material explicitly states there are no required secrets or environment variables, and the README does not request API tokens, account credentials, or external authentication; no clear credential exposure or abuse risk is evident.
The objective checks mark it as prompt-only, and no remote endpoints are declared; the README only describes searching archived conversations and does not indicate sending user data to third-party services.
As a skill, the material is primarily usage guidance and command examples, with no indication that it installs itself, launches background processes, or requests elevated privileges; the local `search-conversations` binary is only referenced as a manual tool entry point.
Its stated purpose is to search archived conversations and return project, date, summary, matched excerpts, and file paths, which implies ordinary access to local archived conversation data; the material does not specify exact directory scope or minimization controls, so users should verify it does not read unrelated content.
Positive factors include being open-source on GitHub and auditable; however, the repository has no declared license, 0 stars, and unknown maintenance status, so trust is only moderate and the repo contents and recent commit activity should be reviewed before use.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "Remembering Conversations" skill from askskill: 1. Download https://raw.githubusercontent.com/obra/clank/main/skills/collaboration/remembering-conversations/SKILL.md 2. Save it as ~/.claude/skills/remembering-conversations/SKILL.md 3. Reload skills and tell me it's ready
Search my previous Claude Code conversations and find why we decided to switch authentication from sessions to JWT. Summarize the background, tradeoffs, and final conclusion.
Relevant conversation excerpts plus a clear summary of the decision, rationale, tradeoffs, and outcome.
Use semantic search across my past Claude Code conversations to find recurring build failure patterns from the last month and rank them by frequency.
A ranked list of common issues, typical symptoms, frequency, and useful troubleshooting context.
Search all previous Claude Code conversations about the payments module and extract key requirements, open items, confirmed constraints, and recommended next steps.
A structured project context summary that helps resume development or discussion quickly.
Search archived conversations using semantic similarity or exact text matching.
Core principle: Search before reinventing.
Announce: "I'm searching previous conversations for [topic]."
Setup: See INDEXING.md
Search when:
Don't search when:
Always use subagents (50-100x context savings). See skills/getting-started for workflow.
Manual/CLI use: Direct search (below) for humans outside Claude Code sessions.
Tool: ~/.claude/skills/collaboration/remembering-conversations/tool/search-conversations
Modes:
search-conversations "query" # Vector similarity (default)
search-conversations --text "exact" # Exact string match
search-conversations --both "query" # Both modes
Flags:
--after YYYY-MM-DD # Filter by date
--before YYYY-MM-DD # Filter by date
--limit N # Max results (default: 10)
--help # Full usage
Examples:
# Semantic search
search-conversations "React Router authentication errors"
# Find git SHA
search-conversations --text "a1b2c3d4"
# Time range
search-conversations --after 2025-09-01 "refactoring"
Returns: project, date, conversation summary, matched exchange, similarity %, file path.
For details: Run search-conversations --help
Write evergreen comments focused on what and why, not historical context.
Name code by domain meaning to improve clarity and team alignment.
Plan with pseudocode first, refine approaches, then translate into working code.
Design systems by hiding implementation details behind domain-level interfaces.
Compare 2-3 approaches before execution to choose a stronger solution.
Helps developers keep class abstractions cohesive and free of unrelated responsibilities.
Search and filter Claude Code memory files to retrieve relevant context fast.
Persist, search, and reinject context across Claude Code sessions.
Search Claude Code history to recover past conversations and project context.
Search Claude Code transcript history semantically to recover relevant past context.
Search Claude chat and coding session memory to recover past context fast.
Search local Markdown notes offline with hybrid semantic and keyword retrieval.