Exploring sessions

Strategy for searching and reading the user's stored AI coding sessions efficiently. Use when the user asks broad questions about their history ("what have I been working on", "how did I solve X", "find sessions about Y") or when you need to triage many possible matches.

Overview

Visibility
public
Updated
17h ago
Built from
0 sessions

Install

An Agent Skill is a SKILL.md plus its files, zipped as .skill. Pick an agent — it activates when its description matches your request.

Download exploring-sessions.skillexploring-sessions/SKILL.md

User-level (~/.claude/skills/)

unzip ~/Downloads/exploring-sessions.skill -d ~/.claude/skills/

Project-level (.claude/skills/, run from repo root)

unzip ~/Downloads/exploring-sessions.skill -d .claude/skills/
SKILL.md

Exploring sessions

The user's session archive can be hundreds or thousands of conversations. Strategy matters.

Strategy: cast wide, narrow fast

  1. Start with search_threads on the most specific keyword from the user's question. Don't search vague terms like "code" or "function".
  2. If the first search returns nothing, try synonyms or related tech (e.g. "auth" → "login", "signin", "oauth", "jwt"). Spend 2-3 query variations before giving up.
  3. Use list_threads only when you need to browse by metadata (agent, model, project_path) — it does NOT filter on message text.
  4. Use get_thread to read a specific session in full. Each call is expensive on tokens — pick a few candidates from search results, don't read all of them.

What's in scope

Tools see: the user's own sessions, sessions explicitly shared with them, and sessions in every workspace they belong to (with that workspace's visibility rules). Not "all sessions on the platform."

Linking results

Always cite with markdown links: [Title](/t/slug). To cite a specific message or range, append #m5 or #m3-m7. Never output a raw slug. The title comes from each result's title field; if null, use a short paraphrase of the first message.

When the answer isn't in the corpus

If thorough searching turns up nothing relevant, say so plainly: "I don't see any sessions about X in your history." Don't speculate or invent content.