recall-sessions
Search past agent conversations to recall prior discussions, decisions, and context. Activate this skill when users ask about previous conversations, want to resume past work, or reference earlier decisions.
Best use case
recall-sessions is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Search past agent conversations to recall prior discussions, decisions, and context. Activate this skill when users ask about previous conversations, want to resume past work, or reference earlier decisions.
Teams using recall-sessions should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/recall-sessions/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How recall-sessions Compares
| Feature / Agent | recall-sessions | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Search past agent conversations to recall prior discussions, decisions, and context. Activate this skill when users ask about previous conversations, want to resume past work, or reference earlier decisions.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Recall Past Sessions Find and retrieve past agent conversations using the `recall_sessions` tool. This enables recalling prior discussions, decisions, and context from earlier sessions. ## When to Use Use this skill when the user: - Asks "what did we discuss about..." or "last time we talked about..." - Wants to resume or continue previous work - References a decision or conversation from a past session - Asks "have we worked on..." or "do you remember when..." - Needs context from a prior session about a specific file or project ## How to Use Call the `recall_sessions` tool with these parameters: - **`query`** (optional) — Search term to match against session titles (case-insensitive substring match). - **`filePath`** (optional) — Find sessions that accessed a specific file (e.g., `notes/meeting.md`). - **`project`** (optional) — Find sessions linked to a specific project name. - **`limit`** (optional) — Maximum results to return. Default is 10, maximum is 50. At least one of `query`, `filePath`, or `project` should be provided for meaningful results. ## Search Strategies - **Topic search** — Use `query` when the user asks about a discussion topic: `recall_sessions(query="refactoring")` - **File-based recall** — Use `filePath` when the user references a specific file: `recall_sessions(filePath="projects/website-redesign.md")` - **Project recall** — Use `project` when the user mentions a project: `recall_sessions(project="website-redesign")` - **Combined search** — Use multiple parameters to narrow results: `recall_sessions(query="API design", project="backend")` ## Progressive Disclosure The tool returns **session summaries only** — title, date, files accessed, project linkage, and a `historyPath`. To see the full conversation from a past session, use `read_file` on the returned `historyPath`. This two-step approach avoids loading unnecessary conversation data. ### Workflow 1. Call `recall_sessions` to find relevant sessions 2. Review the returned summaries with the user 3. Use `read_file` on the `historyPath` of the session(s) the user is interested in 4. Summarize or reference the relevant parts of the conversation ## Tips - Results are sorted by most recent first — the newest sessions appear at the top. - The current session is automatically excluded from results. - When the user asks a vague question like "what did we do last time", try a broad `query` or search by the files currently in context using `filePath`. - If no results are found, let the user know and suggest alternative search terms or parameters.
Related Skills
vault-semantic-search
Search vault notes by meaning using semantic search (RAG). Activate this skill when users want to find notes by concept or topic rather than exact keywords, or when keyword search tools return poor results.
obsidian-properties
Work with Obsidian note properties (frontmatter). Activate this skill when users want to add, modify, or organize properties, understand property types, format YAML frontmatter, or use properties with templates, search, or Bases.
obsidian-bases
Create and configure Obsidian Bases — database-like views of notes. Activate this skill when users want to create bases, write filters, formulas, or set up table/cards/list/map views.
image-generation
Generate images from text descriptions and save them to the vault. Activate this skill when users want to create illustrations, diagrams, visual content, or any AI-generated images.
gemini-scribe-help
Answer questions about Gemini Scribe plugin features, settings, and usage. Activate this skill when users ask how to use the plugin, configure settings, or troubleshoot issues.
deep-research
Conduct comprehensive, multi-source research and generate cited reports. Activate this skill when users want in-depth research on a topic, need synthesis across web and vault sources, or want a structured research report saved to their vault.
audio-transcription
Transcribe audio and video files into structured notes. Activate this skill when users want to transcribe recordings, meetings, podcasts, voice memos, or any audio/video content in their vault.
ui-ux-guidelines
UI/UX best practices for obsidian-gemini plugin development. Covers modal sizing, text overflow, message formatting, collapsible UI, animations, icons, file chips, session state, CSS containment, and theme compatibility. Use this skill when building or modifying UI components.
release-process
Full release workflow for obsidian-gemini: update release notes, run checks, bump version with npm, create a GitHub release, and verify. Use this skill when preparing a new plugin release.
obsidian-plugin-development
Build, modify, and debug Obsidian plugins using the TypeScript API. Use this skill when working with Obsidian plugin source code, the obsidian npm package, plugin UI (views, modals, settings, commands, ribbons), vault file operations, editor manipulation, workspace management, metadata cache, events, markdown rendering, or the Obsidian CLI. Covers plugin lifecycle, best practices, common patterns, and the full TypeScript API surface.
obsidian-cli
Use the Obsidian CLI to debug, inspect, and test Obsidian plugins during development. Covers plugin reloading, console inspection, runtime evaluation, and common debugging recipes for the gemini-scribe plugin.
gemini-api-dev
Use this skill when building applications with Gemini models, Gemini API, working with multimodal content (text, images, audio, video), implementing function calling, using structured outputs, or needing current model specifications. Covers SDK usage (google-genai for Python, @google/genai for JavaScript/TypeScript, com.google.genai:google-genai for Java, google.golang.org/genai for Go), model selection, and API capabilities.