memory-retrieve

Name: memory-retrieve
Availability: InStock
Author: petrsimonidesxart

Load minimal relevant memory using progressive disclosure with index scans.

Updated Mar 8, 2026

Search Tags:#retrieval #memory #cross-domain #progressive-disclosure #context-building #decision-registry #durable-memory

Ready to run

npx skills add https://github.com/petrSimonidesXart/xPmGateway --skill memory-retrieve-petrsimonidesxart

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: memory-retrieve
Source: https://github.com/petrSimonidesXart/xPmGateway/tree/main/.gaai/core/skills/cross/memory-retrieve
Command: npx skills add https://github.com/petrSimonidesXart/xPmGateway --skill memory-retrieve-petrsimonidesxart

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Loads only the minimal relevant memory for a task to avoid large, costly memory dumps and reduce latency.

Core Features & Use Cases

Progressive memory loading with an index-driven filter to load only relevant decisions.
Durable memory preserved by loading only DEC-{ID}.md files and related materials, avoiding full dumps.
Use Case: During complex reasoning or multi-task projects, retrieve contextually relevant decisions for quick, accurate reasoning.

Quick Start

Activate memory-retrieve before context-building to ensure only relevant memories are loaded.

Frequently Asked Questions about memory-retrieve

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

FAQPage Schema

How do I load only the relevant memory for a task without dumping the entire context?▼

Progressive memory loading uses an index-driven filter to scan memory and load only relevant decisions, avoiding large costly memory dumps and reducing latency. It retrieves targeted files on demand during context-building.

What is progressive disclosure for durable memory and when do I need it?▼

Progressive disclosure is a three-level memory loading workflow for durable memory: an index scan, targeted file loading, and optional cross-domain consistency checks. You need it for complex reasoning or multi-task projects requiring historical context.

How do I retrieve cross-domain context for complex reasoning tasks?▼

Cross-domain context retrieval applies optional consistency checks after loading targeted durable-memory files, ensuring contextually relevant decisions are gathered for quick, accurate multi-domain reasoning without full memory dumps.

Can I use memory-retrieve for decision tracking in multi-task projects?▼

Yes, memory-retrieve is designed for multi-task projects requiring decision tracking. It loads only relevant DEC-{ID}.md files and related materials on demand, preserving durable memory while providing historical context for accurate reasoning.

What's the best way to avoid large memory dumps when building task context?▼

The best way to avoid large memory dumps is activating memory-retrieve before context-building. It applies an index-driven filter to load only minimal relevant decisions, reducing latency and preserving durable memory during complex reasoning.

Why does loading full memory history increase latency in cross-domain reasoning?▼

Loading full memory history increases latency because it processes unnecessary data instead of filtering for relevant decisions. Progressive disclosure solves this by scanning an index first, then loading only targeted durable-memory files for the task.