session-search is a read-only lookup over the graph that session-brain builds. You give it a topic, it queries the graph through the obsidian-wiki command line tool and presents the top matches in a compact table with the reason each one matched.
It then hands the best session ids to a loader, or reads the human turns of the transcript directly, and answers from what it loaded while citing the session ids it used.
What You Get
- A short table of matching past sessions with title, project, date, topic and match reason
- Filters for project, cluster, start date and result count
- The best transcript loaded into the current conversation, read only through its human turns
- A warning when the graph is older than about a week, with an offer to rebuild
- An answer that cites the session ids it drew on and says when only prompts survive
Common Use Cases
- Finding the session where a bug was fixed months ago
- Checking whether a task was already done before starting it again
- Pulling the context of a bookmarked session back into a new chat
What Makes It Unique
Ranking uses the cluster a session belongs to, so a session that never used your exact word can still surface for the topic. It separates sessions whose transcripts are gone from loadable ones and tells you how much context is really available. It hands loading to an installed loader skill when there is one and has a built-in fallback that filters a transcript to the human turns, so a huge file is never read whole.
Under The Hood
The skill is instructions that run the obsidian-wiki command line tool through the shell for sessions-query and sessions-show. As a fallback it runs grep to size a transcript and an inline Python snippet that reads the JSONL file and prints the first part of each user message. It reads session files and the graph on disk. It does not write files, fetch web pages or call remote APIs, and it never rebuilds the graph without asking.