retrieval-reflex
When/what to retrieve — open the brain page for a salient entity before answering from memory.
Skill by singhvedant
Install
Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.
npx agentmarket install skill/singhvedant-retrieval-reflex
Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.
Get the weekly diff
The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.
About
Reviews
Write a reviewNo reviews yet. Installed it? Reviews come from verified installers only. How reviews work
Permissions: not checked yet.
What's inside
- Skill name
retrieval-reflex- Description
- When/what to retrieve — open the brain page for a salient entity before answering from memory.
- License
- MIT
- Instructions
- 47 lines in SKILL.md · view on GitHub
Files (1)
- SKILL.md
SKILL.md (first lines)
# Retrieval Reflex — retrieve on demand, when an entity is salient A person doesn't bulk-load their whole address book into working memory. They retrieve **on demand**, when an entity becomes **salient**, use it, and drop it. Encode that reflex. The brain probably has the data — if a name is salient and you haven't opened its page, open it before you answer. ## Trigger policy — WHEN to retrieve Retrieve when ANY of these holds AND the page isn't already loaded in context: - An entity (person / company / project / deal / place) is the **subject** of the message, or a decision/judgment about it is being made, or the exchange is substantive / relational / emotional about it. - A **brain-page pointer** appeared in context this turn (the deterministic layer told you the page exists) — open it before relying on details. - A name or term appears that you **don't recognize** and that looks notable → do a quick resolve (the human reflex). - You're about to **assert a non-trivial detail** about an entity (attribution, status, history) → verify against the brain first. Say "let me check", not a guess. **Skip** trivial passing mentions, logistics pings, and anything already loaded. Judgment first — retrieve when it changes the quality of the reply, not reflexively. ## Retrieval spec — WHAT to pull, and when to stop Escalate only as far as the task needs: 1. **Pointer / metadata.** If a pointer is already in context (slug + one-line summary), and the task only needs identity, stop there. 2. **Full page.** When the entity is the subject or details matter, open it: `get_page <slug>` (MCP) — read the page before relying on specifics. 3. **Linked neighbors.** Only when relationship context is needed, pull `graph` / `backlinks` for the slug. **Resolve only the name(s) the current task needs, use them, drop them.** No bulk-loading the inner circle. ## The failure this prevents If you've discussed a named person for more than a message without opening their page, open it now. The write side captures everything; the read side only helps if you actually look. See also: `skills/query/SKILL.md` (search the brain), `skills/brain-ops/SKILL.md`.
From singhvedant/tbrain, MIT.
Signals
- Stars
- 0
- Forks
- 0
- Open issues
- 0
- Last commit (this folder)
- Jun 23, 2026 (4 months ago)
From GitHub (fetched Oct 24, 2026).
Details
- License
- MIT
- Repository
- github.com/singhvedant/tbrain
- First seen
- Oct 24, 2026
- Last checked
- Oct 24, 2026
- Source
- GitHubgithub-graphql
Same skill elsewhere
Copies of this SKILL.md published by others; search shows only one of them.
More from singhvedant
Cite this page
retrieval-reflex skill. Agent Mart. https://agentmart.dev/skills/singhvedant-retrieval-reflex (last updated 2026-10-24)