agentleFS
Sign inStart free
apappascsapappascs/claude-code-sessions/skills/session-search/SKILL.md

session-search

Skill2 starsChanged 26 days agoMITView on GitHub

Searches Claude Code sessions across all projects by keyword, topic, or content. Use when the user wants to find a previous session, locate past work, search for something they discussed before, or cannot remember which project a conversation was in. Also use when the user says "find that session where" or "search sessions".

14 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use ml-training-recipe, replication and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • getcompanion-aiSkill

    ml-training-recipe

    Find implementable ML training recipes from papers, datasets, docs, and code. Use when the user wants to fine-tune, train, reproduce, or choose a practical ML method, dataset, hyperparameter setup, or benchmark recipe.

    Also in 3 projects that use this

  • getcompanion-aiSkill

    replication

    Plan a replication of a paper, claim, or benchmark, and execute only after an explicit environment choice. Use when the user asks to replicate results, reproduce an experiment, verify a claim empirically, or build a replication package.

    Also in 3 projects that use this

  • brainbytes-devSkill

    alpha-research

    Also in 3 projects that use this

  • JaimeParkerSkill

    paper-code-audit

    Perform three-way cross-validation of a research paper by comparing the original paper text (via Zotero), official code implementation (via Git), and personal Obsidian notes. Use this skill whenever the user wants to "audit a paper", "verify paper claims against code", "cross-check notes with implementation", "triangulate paper + code + notes", "find discrepancies between paper and code", or mentions wanting a deep, structured comparison of a paper's claims against its implementation and their own notes. Also trigger when the user asks to "analyze this paper thoroughly" with code available, or when they want to systematically reconcile what the paper says, what the code does, and what their notes claim.

    Also in 3 projects that use this

  • JimLiuSkill

    pdf-explore

    Use this skill when the user has attached a PDF, paper, report, or other document and the answer needs content from more than one place in it: summarize the methods or any other section, compare sections, find where a topic is discussed, read a value or label off a figure or chart, or find/list/extract every instance of something across the whole document (datasets, benchmarks, citations, figures, table rows, accession numbers — including appendices). Skip it only for a single lookup of 1–4 pages quoted in your very next response — `read_file(pages=[...])` attaches pages as images that are dropped from context after one turn, so multi-section answers end up re-reading the same ranges repeatedly. Parses the PDF once in the Python kernel: `pdf_pages` (pages as persistent text), `pdf_outline` (TOC), `pdf_scan` (rank pages by relevance), `pdf_map`/`pdf_extract` (per-page summary / structured fields via parallel haiku calls). For PDF creation/manipulation, use reportlab/pypdf directly.

    Also in 3 projects that use this

  • composio-communitySkill

    weekly-digest

    Generate a weekly support digest and post it to [Slack](https://composio.dev/toolkits/slack)

    Also in 3 projects that use this

  • +1 more from getcompanion-ai

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 10 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Search across all Claude Code sessions by keyword.

    line 12
  2. Distinctive:

    If no results, suggest broadening the search or trying different keywords.

    line 54

“Common” is measured: kept by at least 6 in 10 of the 10 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Session Search

Search across all Claude Code sessions by keyword. The query is matched (case-insensitive, literal) against message text and session titles: the user-set name (customTitle, e.g. from /rename) and the auto-generated name (aiTitle). Searching a session's name therefore finds it. Earlier names also match: every distinct title the session ever had is searched, so an old /rename name or the auto title still finds a renamed session. The row then shows the current title (title) alongside the title that matched (match).

Title matches are listed first (custom-title matches, then ai-title matches), followed by message matches in scan order. --limit applies after that ordering, so a session found by name is never cut off by message hits elsewhere.

Step 1: Run the search

bun run ${CLAUDE_PLUGIN_ROOT}/lib/session-store.ts search "<query>" --limit 20 --context 1 --format json

To filter by project:

bun run ${CLAUDE_PLUGIN_ROOT}/lib/session-store.ts search "<query>" --project "<filter>" --limit 20 --context 1 --format json

To filter by date:

bun run ${CLAUDE_PLUGIN_ROOT}/lib/session-store.ts search "<query>" --since "2026-04-01" --limit 20 --format json

Date filters (--since/--until): title rows are kept when the session's first-to-last timestamp span overlaps the window (unlike list, which uses last activity); as in list, sessions with no parseable timestamp are dropped when a date filter is set. Message rows without a timestamp are not filtered.

Step 2: Present results

The script outputs newline-delimited JSON (one match per line, title matches first). Group results by session and present:

  • Session ID, project, and title (title: custom title if set, else auto title; may be null) as headers
  • Matching text with timestamp. Rows with "match_type": "title" are title matches: type is custom-title or ai-title and match is the title value that matched (a custom-title match is preferred over an ai-title match). If match differs from title, say the session was found by an earlier or auto name and show the current title alongside. Flag these as "matched session title". timestamp on a title row is the session's last activity. Rows with "match_type": "message" are message text.
  • Context (lines before/after) if available
  • Resume command: claude --resume <session-id>

If no results, suggest broadening the search or trying different keywords.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free