memory-retrieve

Retrieves facts and decisions from durable local memory using QMD-first search with provenance-aware metadata handling.

Updated Jun 23, 2026
One-click install
npx skills add https://github.com/Walliiee/agent-harness --skill memory-retrieve-walliiee
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: memory-retrieve
Source: https://github.com/Walliiee/agent-harness/tree/main/skills/memory-retrieve
Command: npx skills add https://github.com/Walliiee/agent-harness --skill memory-retrieve-walliiee

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of agents answering from stale training data or guessing when the answer already exists in local durable memory, wiki pages, or recent daily memory.

Core Features & Use Cases

  • Local knowledge lookup: Search for facts, decisions, project state, and people references stored in memory or wiki rather than searching the web.
  • Ordered retrieval strategy: Use QMD first for fast broad recall, then escalate to gbrain only when QMD returns no hits and deeper graph reasoning is needed.
  • Provenance-aware interpretation: Weigh confidence, recency, decay, and recall history when results include memory metadata so conflicting or stale items are handled carefully.
  • Use case: Ask for the latest project decision, a previously recorded invariant, or a teammate reference before improvising an answer.

Quick Start

Use the memory-retrieve skill to look up the current project decision about onboarding in durable memory before answering.

Frequently Asked Questions about memory-retrieve

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

FAQPage Schema
How do I retrieve project decisions from local memory instead of web search?

To retrieve local memory, query durable knowledge stores like wiki pages or daily notes for project state, people references, and invariants. This ensures facts are pulled from recorded memory rather than stale training data or improvised web search results.

What is the best way to look up recent notes and invariants in a wiki?

The best way to look up wiki invariants and recent notes is using an ordered retrieval strategy. It queries fast broad recall sources first, then escalates to deeper graph reasoning only when initial searches return no hits.

How does provenance-aware handling work for memory retrieval?

Provenance-aware memory retrieval weighs confidence, recency, decay, and recall history metadata. This mechanism carefully handles conflicting or stale items by evaluating their contextual metadata when interpreting retrieved knowledge.

When do I need to use gbrain fallback for knowledge lookup?

You need gbrain fallback for knowledge lookup when initial fast recall queries return no hits. It provides deeper graph reasoning capabilities to find facts and decisions that broad searches missed.

Can I use QMD-first retrieval for searching durable local memory?

Yes, you can use QMD-first retrieval for searching durable local memory. It applies to questions about project state, people, invariants, and recent notes, applying provenance-aware handling to manage confidence and recency metadata.

Why does my agent answer from stale training data instead of local memory?

Agents answer from stale training data when they lack ordered local memory retrieval. By querying durable memory stores with provenance-aware handling, agents can access recorded facts, decisions, and recent daily notes instead of improvising answers.