searching-sessionslisted

Search and explore AI/Claude/Codex conversation history stored in cortex. **Trigger when:** the user asks to "search sessions", "find conversations", "what did I work on", "session history", "past conversations", "ask history", "when did I last use X", "show recent sessions", "list AI projects", "what tools have I used"; OR when **referencing past work** like "we've done this before", "we fixed something similar", "haven't we implemented this", "this was already working", "why did we do that again", "I thought we already solved this"; OR when **questioning past decisions** like "why did we implement it this way", "what was the reasoning for", "didn't we discuss this already", "this seems familiar"; OR when the user is **under the something was done before** or wants to find context about previous implementations, fixes, or decisions. Use for session search, conversation discovery, past work retrieval, implementation history, or decision archaeology.
dinglebear-ai/cortex · ★ 2 · AI & Automation · score 68

Install: claude install-skill dinglebear-ai/cortex

# Cortex Session Search Search and explore AI/Claude/Codex conversation history stored in cortex. The skill provides full-text search over session transcripts, question-based history retrieval with system log context, project summaries, usage patterns, and investigation tools for skill/MCP/hook failures. ## Primary Actions ### `sessions` — Browse recent conversations List AI transcript sessions grouped by project, tool, session, and host. Use for discovery and overview of recent activity. ### `search_sessions` — Full-text search with relevance ranking FTS5 search over AI transcript rows. Returns grouped session results ranked by relevance. Best for targeted searches when you know what you're looking for. ### `correlate` (query-only) — Question-based history with system context Pass `query` without `reference_time` to `correlate` to derive the anchor from the top matching AI-transcript session, then correlate nearby system logs around it (severity-gated, host-grouped, same as any other `correlate` call). The matched session comes back as `matched_session`. Use for "what happened when I worked on X" or "how did we solve Y before". ### `project_context` — Full project summary Complete context for one AI project path: tools, sessions, hosts, counts, and recent representative entries. Use for getting oriented on a project's activity. ### `ai_correlate` — Session events + system logs Use AI transcript rows as timeline anchors and pull nearby non-AI syslog, Docker, OTLP, and