session-search
Search the session-brain graph for a past agent session by topic and load the winning transcript into the current conversation. Use for finding which session handled X, when Y was last worked on, or whether this was done before. Read-only; requires a session-brain graph.
Install / Use
npx skills add Ar9av/obsidian-wiki --skill session-searchInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Development & EngineeringSupported Platforms
Tags
Our assessment of session-search
session-search scores 89/100 on our quality scale, 1555th of 4,698 Development & Engineering skills we index (top 34%).
Its SKILL.md is 3.7 KB long, well organised into 8 sections with 3 code examples: a solid amount of guidance for an agent.
With 3,485 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so session-search is actively maintained.
- Our last check on 2026-10-31 found the source still online.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
session-search compared with similar skills
All 4 of these similar skills score higher than session-search; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| session-search (this skill)by Ar9av | 89 | 3.5k | 54d ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 116.8k | 8d ago | CLAUDE.md |
| ai-job-searchby ai-job-search-dev | 100 | 72.1k | today | CLAUDE.md |
| claude-howtoby luongnv89 | 100 | 47.3k | 2d ago | CLAUDE.md |
| lobehubby lobehub | 100 | 85.6k | today | MCP Server |
Frequently asked questions
- How do I install session-search?
- Run
npx skills add Ar9av/obsidian-wiki --skill session-search. The install tabs above show the steps for each supported agent. - Which AI agents does session-search work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is session-search safe to use?
- It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is session-search still maintained?
- The repository was last updated about 2 months ago, so session-search is actively maintained.
Skill content
View source on GitHubname: session-search description: > Search the session-brain graph for a past agent session by topic and load the winning transcript into the current conversation. Use for finding which session handled X, when Y was last worked on, or whether this was done before. Read-only; requires a session-brain graph.
Session Search
Answers "which of my past sessions was about X" and then pulls that session's context in.
Step 1: Check the graph exists and is fresh
obsidian-wiki sessions-query "<topic>" --json
If this exits 1 with "run sessions-build first", tell the user and offer /session-brain. If
graph.json is more than ~7 days old, mention it and offer a rebuild — but do not silently
rebuild, since that is a multi-second operation the user did not ask for.
Step 2: Rank
The scoring already combines four signals, so take the ordering as given rather than re-ranking:
- similarity — TF-IDF cosine against the session's text
- cluster lift — a session inside the best-matching topic scores higher even if its own words never matched. This is why a session that never said "telemetry" can still surface for it.
- bookmark boost — a human already flagged this session as worth keeping
- time decay — 90-day half-life, applied with a floor so an old exact match still outranks a fresh weak one
Useful filters: --project NAME, --cluster N, --since DATE, --top N.
Step 3: Present
Show the top ~5 as a compact table — title, project, date, topic, and the why string, which
already explains the match. Do not dump the raw JSON at the user.
Two things must be stated honestly rather than glossed over:
- Entries with
loadable: falseare history-only: the transcript has been pruned from disk and only the prompts survive. They are listed inunloadablewith a reason. Say the transcript is gone; do not imply it can be retrieved. - If everything relevant is unloadable, answer from the prompt text that is there and say that is all that remains.
Step 4: Load — hand off, do not reimplement
should_load holds at most 3 session ids worth opening, already filtered to ones with
transcripts.
Prefer an existing loader skill if the user has one installed:
claude-session-load— loads a Claude session by idbookmark-load— use when the hit is bookmarked
⚠️ Those skills live in the user's personal skills directory (~/.claude/skills/), not in this
repo. They may not exist. Do not assume them and do not error if they are absent — fall back to
reading the transcript directly:
# the path is in the query result as `transcript`
obsidian-wiki sessions-show <session-id> --pretty
The transcript is JSONL and can be tens of MB. Never read one whole. Filter to the human turns first:
grep -c '' <transcript> # size check before anything else
python3 -c "
import json,sys
for line in open(sys.argv[1], errors='replace'):
try: r = json.loads(line)
except ValueError: continue
if r.get('type')=='user' and not r.get('isSidechain') and not r.get('isMeta'):
c = (r.get('message') or {}).get('content')
if isinstance(c,str) and not c.lstrip().startswith('<'): print('>', c[:400])
" <transcript>
Step 5: Answer
Synthesise from what you loaded and cite the session ids you used. If the answer came from a history-only session's prompts rather than a real transcript, say so — the user needs to know how much of the context you actually have.
Related
/session-brain— build or refresh the graph, survey and name topicswiki-query— search compiled vault knowledge; this skill searches raw session history insteadwiki-agent— pull a topic out of another agent's history and distil it into the vault
Related Skills
taste-skill
116.8kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
ai-job-search
72.1kThe job search that runs on your machine. AI job application framework built on Claude Code: evaluate postings, tailor CVs, write cover letters, prep interviews. Fork it and own it.
claude-howto
47.3kA visual, example-driven guide to Claude Code — from basic concepts to advanced agents, with copy-paste templates that bring immediate value.
lobehub
85.6k🤯 LobeHub - Super-Agents on Your Team. Add super-agents to the chats your team already uses.They take on work by themselves and get better every week.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
