aii-session-search

Ask in recall-shaped language, such as "which session did we decide X in" or "find the chat where we built Y." The Skill runs a ranked full-text search over distilled session summaries, keywords, and titles, returning matches with snippets and a route back to the original chat.

Ask a status question like "which legs of the migration track are done?" The Skill reads the status column directly from each session record for that track and lists the legs in order, marking each as done or active.

No. Only the distilled summary, keywords, and title written by the session handoff are stored and searched. Raw transcripts are never persisted, which is the privacy floor by design.

The Skill first checks for a live initiatives-board connector. If none answers, it stops and plainly says the session records cannot be reached on this seat, rather than returning a misleading empty result.

The design deliberately uses PostgreSQL full-text search with a GIN index because it answers the real recall need without extra infrastructure. Embedding-based search is explicitly deferred as a separate later decision.

Skip it for any forward-looking task with no look-back, such as building, drafting, or answering a fresh question. It only fires on recall-shaped language about past sessions.