Session index

Skill Jeremyx000/claude-session-index/skills/session-index

Search, analyze, and synthesize across all your Claude Code sessions. Ask "what did I try last time?" and get answers with resume links.From its SKILL.md

Install

npx -y skills add Jeremyx000/claude-session-index --skill session-index

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

3.3 KB, 696 tokens by cl100k_base, as published. Nobody here has run it

Session index skill

You have access to a session index — a SQLite database with FTS5 full-text search across all Claude Code sessions. Use it whenever the user asks about past sessions, previous conversations, or wants to know what they've tried before.

The user's interface is this conversation. They ask naturally ("Didn't we discuss browser control recently?"), you translate to CLI commands, and present results conversationally. They should never need to know the CLI syntax.

How to handle session queries

1. Extract keywords from the question

The user says: "Didn't we discuss browser control recently?" You search: sessions "browser control"

The user says: "What approaches have I tried for form automation?" You search: sessions "form automation"

The user says: "How much time did I spend on Acme this week?" You run: sessions analytics --client "Acme" --week

2. Run the right command via Bash

Search — find sessions by topic:

sessions "relevant keywords"
sessions "relevant keywords" --context    # includes conversation excerpts

Context — read the actual conversation from a session:

sessions context <session_id> "search term"   # exchanges matching a term
sessions context <session_id>                 # all exchanges

Analytics — effort, time, tool usage:

sessions analytics                    # overall
sessions analytics --client "Acme"    # per client
sessions analytics --week             # this week
sessions analytics --month            # this month

Filter — find sessions by metadata:

sessions find --client "Acme"              # by client
sessions find --tool Task --week           # by tool + date
sessions find --project myapp              # by project
sessions recent 20                         # last N sessions

3. For synthesis ("what worked?", "what have I tried?")

This is the most valuable capability. When the user asks a question that spans multiple sessions:

Search: sessions "topic" -n 10
For the top 3-5 results, extract context: sessions context <id> "topic" -n 3
Spawn a Task with model="haiku" to synthesize:
- What approaches were tried?
- What worked / what failed?
- Recurring patterns?
- Current state?
Present the synthesis conversationally with claude --resume <id> links for each source session

This uses an in-session Haiku subagent — no external API key needed.

4. Present results conversationally

Don't dump raw CLI output. Summarize:

"You discussed browser control in 3 sessions last week..."
"The main approach that worked was..."
Include claude --resume <session_id> links so they can jump back in
If context is relevant, quote key exchanges

Installation

pip install claude-session-index

First run of any command auto-indexes all existing sessions.

Data location

Database: ~/.session-index/sessions.db
Topics: ~/.claude/session-topics/
Config: ~/.session-index/config.json (optional)

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most memory context skills give in 696 tokens

Counted across 674 of the 847 authors here whose files we hold, read 2026-08-07

Inform the user when setup is completein 21 of 674, across 6 files
Confirm the draft with the user before writingin 21 of 674, across 7 files
Update the agent skills block in place if it existsin 21 of 674, across 6 files
Present findings to the userin 20 of 674, across 5 files
Ask the user about each decision one at a timein 20 of 674, across 5 files
Write the three docs files from seed templatesin 20 of 674, across 5 files
Edit CLAUDE.md if it existsin 18 of 674, across 3 files
Explore current repo statein 18 of 674, across 3 files
Do not overwrite user edits to surrounding sectionsin 18 of 674, across 3 files
Keep the memory index under 200 linesin 18 of 674
Back up the original file before overwritingin 16 of 674, across 8 files
Provide actionable steps and verificationin 13 of 674, across 2 files

Said here and by no other author read

use the session index for questions about past sessions
translate natural questions into search commands
extract relevant keywords from the user question
run search commands via the bash tool
search top results for multi-session synthesis questions
extract context for top results

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.