name	retrieval-reflex
version	0.1.0
description	When/what to retrieve — open the brain page for a salient entity before answering from memory.
triggers	["who is","what do we know about","tell me about"]
mutating	false
writes_pages	false
writes_to	[]
tools	["get_page","query","graph","backlinks"]

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:

Pointer / metadata. If a pointer is already in context (slug + one-line summary), and the task only needs identity, stop there.
Full page. When the entity is the subject or details matter, open it: get_page <slug> (MCP) — read the page before relying on specifics.
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.

이 저장소의 다른 Skills

같은 저장소

gbrain-advisor

garrytan/gbrain

Proactive "make the most of gbrain" coaching. Runs `gbrain advisor` on a cadence and pings the user with the top high-leverage actions for their brain: version drift, pending migrations, stalled jobs, low embed coverage, setup smells, and uninstalled brain skills. Read-only; always asks before fixing.

2026-06-1723.1k

frontmatter-guard

garrytan/gbrain

Validate and auto-repair YAML frontmatter on brain pages. Catches malformed pages before they enter the brain (missing closing

2026-06-0923.1k

concept-synthesis

garrytan/gbrain

Deduplicate and synthesize raw concept stubs into a tiered intellectual map (T1 Canon to T4 Riff), tracing idea evolution across sources over time. Transforms thousands of raw concept pages into a curated intellectual fingerprint.

2026-06-0823.1k

idea-lineage

garrytan/gbrain

Trace one idea's evolution through the brain: first mention, best articulation, related concepts, reversals, contradictions, abandoned branches, and the current live version. Use for single-idea conceptual lineage, not broad concept-map synthesis or structured entity metrics.

2026-06-0823.1k

voice-persona-mars

garrytan/gbrain

Route to Mars (introspective thought partner / demo showman voice persona). Used when the operator wants depth, meaning, or impressive social demos rather than logistics. Mars handles SOLO mode (philosophy, presence, patterns) and DEMO mode (tool-driven showmanship) automatically.

2026-06-0723.1k

voice-persona-venus

garrytan/gbrain

Route to Venus (sharp executive-assistant voice persona). Used for logistics — calendar, tasks, recent messages, brain lookups — at sub-second phone-call latency. The default voice persona unless DEFAULT_PERSONA=mars is set.

2026-06-0723.1k

Retrieval Reflex — retrieve on demand, when an entity is salient

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:

Pointer / metadata. If a pointer is already in context (slug + one-line summary), and the task only needs identity, stop there.

Full page. When the entity is the subject or details matter, open it: get_page <slug> (MCP) — read the page before relying on specifics.

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.