c-04-retrieval-strategy-router

Route retrieval context to the correct memory substrate for ambiguous source decisions.

27|4|Updated Mar 21, 2026

Search Tags:#onboarding #retrieval #memory #code-search #substrates #cgcontext

Ready to run

npx skills add https://github.com/Foxfire1st/agents-remember --skill c-04-retrieval-strategy-router

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: c-04-retrieval-strategy-router
Source: https://github.com/Foxfire1st/agents-remember/tree/main/.github-vscode/skills/c-04-retrieval-strategy-router
Command: npx skills add https://github.com/Foxfire1st/agents-remember --skill c-04-retrieval-strategy-router

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Route retrieval context to the correct memory substrate to resolve ambiguous source decisions.

Core Features & Use Cases

Semantics: use fuzzy concepts when structure or routing is unknown, guiding discovery via onboardings.
Relationship: map anchors to their surrounding code graph and dependencies when relationships are not obvious.
Intent: validate contracts and invariants by combining onboarding with bounded source confirmation.

Quick Start

Ask me to route a vague inquiry to the right substrate and chain substrates as needed to confirm a source.

Frequently Asked Questions about c-04-retrieval-strategy-router

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

FAQPage Schema

How do I route memory retrieval to find the right context in a codebase?▼

Memory retrieval routing directs vague inquiries to the correct memory substrate, resolving ambiguous source decisions by matching semantics, relationship anchors, or intent to the proper context layer.

What is the best way to map code graph relationships when anchors are known but connections are not?▼

Code graph relationship mapping targets the correct memory substrate to discover surrounding dependencies. It connects known anchors to their code graph structure when underlying relationships are not immediately obvious.

How do I validate hidden code contracts and invariants during onboarding?▼

Validating hidden contracts requires combining onboarding substrates with bounded source confirmation. This intent-based routing chains memory substrates to safely verify invariants against actual source definitions.

Can I use fuzzy semantic concepts to guide code discovery when structure is unknown?▼

Fuzzy semantics can guide code discovery by routing to the semantics substrate. This approach applies when you know the concepts but lack the structural routing knowledge, using onboardings to direct discovery.

Do I need a YAML frontmatter file to use retrieval routing workflows?▼

A YAML frontmatter containing a name and description at the root entry is required. Optional scripts, references, and assets resources can be included to support safe, provider-based routing workflows.