history-recall

Retrieve and interpret prior session history, decisions, and unfinished work.

6|Updated Jun 25, 2026
One-click install
npx skills add https://github.com/tribgames/mixdog --skill history-recall-tribgames
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: history-recall
Source: https://github.com/tribgames/mixdog/tree/main/src/defaults/skills/history-recall
Command: npx skills add https://github.com/tribgames/mixdog --skill history-recall-tribgames

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When working across multiple AI sessions, context about past decisions, prior measurements, and unfinished work gets lost. This Skill retrieves stored session history so you can answer historical questions and resume work without guessing or redoing completed analysis. ## Core Features & Use Cases - Semantic History Search: Query stored session history semantically rather than with regex, scoped by project and time window, with batched independent questions. - Grounded Interpretation: Distinguish historical evidence from current repository state, avoiding the mistake of treating past decisions or measurements as proof of today's state. - Cursor-Based Paging: Page through recent sessions using returned cursors and follow up with returned IDs instead of invented ones. - Use Case: You return to a project after a week and need to know why a specific architecture decision was made and what tasks were left incomplete. Use this Skill to search prior sessions, retrieve the relevant decision records, and resume the unfinished work with full context. ## Quick Start Ask the assistant to recall what was decided and left unfinished in this project during last week's sessions.

Frequently Asked Questions about history-recall

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I search past AI session history?▼

Use the recall tool with semantic search rather than regex, selecting the relevant project and time window. Batch independent questions through the supported query array to retrieve stored session evidence efficiently.

How to resume unfinished work from a previous session?▼

Query stored session history for the relevant project and time window, then read only the missing context needed to decide the next action. Use returned IDs for follow-up questions instead of inventing identifiers.

Can session history tell me the current state of my repository?▼

No. Historical retrieval covers past sessions and decisions, not current repository state, which belongs to repository tools. A past measurement or plan is not proof of today's state.

Why does a history search miss something that happened?▼

A miss is not proof that an event never happened; retrieval depends on the query, project selection, and time window. Broaden the semantic query or adjust the time range before concluding the event is absent.

Does recalling history save my standing preferences?▼

No. Retrieval does not save standing preferences; use the memory-management skill for that. Automatic summaries remain searchable history, not standing instructions.