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

Session Search

  • 163 installs
  • 339 repo stars
  • Updated August 4, 2026
  • glebis/claude-skills

Full-text search across past agent transcripts to recover decisions, error messages, or code snippets mentioned only inside a long session thread.

About

The session-search skill enables Claude Code to query full-text content inside archived agent sessions so teams can retrieve earlier explanations, stack traces, and implementation notes during ongoing operation and iterative maintenance work.

  • Searches message content across stored sessions
  • Surfaces prior fixes, errors, and design decisions
  • Complements session-finder with deep text retrieval
  • Cuts time spent re-explaining solved problems

Session Search by the numbers

  • 163 all-time installs (skills.sh)
  • Ranked #3,210 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/glebis/claude-skills --skill session-search

Add your badge

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

Listed on Skillselion
Installs163
repo stars339
Last updatedAugust 4, 2026
Repositoryglebis/claude-skills

What it does

Full-text search across past agent transcripts to recover decisions, error messages, or code snippets mentioned only inside a long session thread.

Files

SKILL.mdMarkdownGitHub ↗

Session Search

Search Claude Code session transcripts by combining keyword pre-filtering with semantic evaluation. Finds previous sessions about specific topics, debugging conversations, research tasks, or any past work.

Workflow

Step 1: Run the search script

Execute scripts/search.py with the user's query:

python3 scripts/search.py "<query>" [max_results] [max_age_days]
  • query (required): Natural language search query
  • max_results (optional, default 10): Maximum results to return
  • max_age_days (optional, default 90): How far back to search

The script performs keyword pre-filtering across all sessions, then extracts meaningful excerpts from top candidates. Output contains a SESSIONS_DATA JSON block.

Step 2: Evaluate results semantically

After receiving the script output, evaluate each session's relevance to the query. Consider:

  • Synonym matching: "bug" matches "error", "issue", "problem", "fix"
  • Related concepts: "debugging" matches sessions with test failures or error messages
  • Tool patterns: "refactoring" matches Edit-heavy sessions
  • Domain context: "obsidian" matches vault-related work

Assign a relevance score (0-10) to each session based on excerpt content and query intent.

Step 3: Present results

Display the top results (up to max_results) sorted by relevance, formatted as:

### [Relevance: N/10] Project — Date
Summary of what the session was about (1-2 sentences based on excerpts)
`claude --resume <session-id>`

If no relevant results are found, report that and suggest alternative queries.

Session Storage

Sessions are stored as JSONL files in ~/.claude/projects/. Each file contains events with user/assistant messages and tool calls. The search script handles file discovery and text extraction automatically.

Customization

To search older sessions or get more results:

/session-search "query" 20 180

(20 results, 180 days lookback)

Related skills

AI & Agent Buildingworkflownotes

This week in AI coding

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

unsubscribe anytime.