recall

Aggregate cross-source project memory into a single recall report.

1|Updated May 18, 2026
One-click install
npx skills add https://github.com/linenoize/topia --skill recall-linenoize
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: recall
Source: https://github.com/linenoize/topia/tree/main/skills/recall
Command: npx skills add https://github.com/linenoize/topia --skill recall-linenoize

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill solves the problem of starting with missing context by gathering scattered project memory into one dependable Recall Report. It helps you resume work, make architecture decisions, and preserve continuity across sessions without manually hunting through old notes.

Core Features & Use Cases

  • Unified memory aggregation: Combines file-based project state, session notes, and optional semantic memory backends into a single view.
  • Read-only safety: Never writes to memory stores, making it safe to run at session start or before planning.
  • Graceful fallback behavior: Works even when some sources or MCP servers are unavailable, so you still get partial but useful context.
  • Use case: Before refactoring a complex feature, use this Skill to recover prior decisions, active checkpoints, and relevant learnings in one report.

Quick Start

Ask the assistant to run recall for your project so it can gather available memory sources and return a concise Recall Report.

Frequently Asked Questions about recall

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

FAQPage Schema
How do I recover session context and project memory across multiple stores?

Recovering session context involves aggregating scattered project memory from file-based stores and optional MCP backends into a single read-only Recall Report. This unified view helps you resume work and make architecture decisions without manually hunting through old notes.

What is the best way to aggregate scattered architecture decisions for resuming work?

Aggregating architecture decisions is best handled by gathering cross-source project state and session notes into a single report. The process applies source tagging and precedence rules to consolidate prior decisions and active checkpoints in a read-only format.

How do I gather project state when some MCP servers or memory sources are unavailable?

Gathering project state with missing sources relies on graceful degradation behavior to return partial but useful context. The read-only aggregation still compiles available file-based memory when optional semantic memory backends or MCP queries are unavailable.

Does the recall Skill write to memory stores during session-start recovery?

Recall does not write to memory stores during session-start recovery. It operates with strict read-only file gathering safety, ensuring your existing project memory across neural-memory and agora-memory stores remains completely unmodified.

Can I use MCP queries to pull semantic memory into my project state report?

You can use optional MCP queries to pull semantic memory into your project state report. The aggregation process combines these optional backends with local file-based sources, applying source tagging to deliver a unified recall view.