recall

Retrieve relevant prior context from layered session memory and archived transcripts.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill enables agents to load relevant prior context from layered session memory and archived transcripts, ensuring consistency and reducing redundant work.

Core Features & Use Cases

  • Context Loading: Fetches prior session artifacts and layered memories to inform current tasks.
  • Scenario Assistance: Helps maintain continuity for ongoing projects, issue follow-ups, and knowledge retention.
  • Use Case: Imagine restarting a project after a pause; this Skill quickly loads previous decisions, logs, and summaries to resume seamlessly.

Quick Start

Load previous session context related to your current project or issue by specifying the repository and relevant keywords.

Frequently Asked Questions about recall

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

FAQPage Schema
How do I retrieve prior session context to maintain consistency across ongoing projects?

Layered session memory works by applying retrieval mechanisms to fetch prior session artifacts and archived transcripts based on specified repositories and keywords. This mechanism helps agents maintain consistent decisions and knowledge retention across multiple sessions.

What's the best way to load previous decisions and logs when restarting a paused project?

Accessing archived session transcripts requires connecting the Skill to layered storage files and optional transcript archives. You specify the repository and relevant keywords to fetch prior session artifacts, enabling knowledge retention and continuity for ongoing tasks.

Do I need layered storage files to maintain session history and context?

Layered session memory differs from standard context loading by specifically retrieving relevant prior context from layered storage files and archived transcripts. Unlike basic loading, it ensures consistent decisions across sessions and reduces redundant work in issue resolution workflows.

Why does context loading fail when resuming a project after a pause?

Layered session memory works by applying retrieval mechanisms to fetch prior session artifacts and archived transcripts based on specified repositories and keywords. This mechanism helps agents maintain consistent decisions and knowledge retention across multiple sessions.