Menu
When/what to retrieve — open the brain page for a salient entity before answering from memory.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Save any thought or content into the brain via one CLI command. The single human-facing entrypoint that replaces "put_page vs commit-then-sync vs autopilot-wait" with one command that just works.
Lift a proven skill from a host repo (e.g. your OpenClaw fork) back into gbrain's bundle so other clients can scaffold it. Editorial workflow: the CLI does the file copy + privacy lint; this skill drives the judgment-heavy genericization (scrub real names, generalize triggers, lift fork-specific conventions to references).
Skill validation framework PLUS daily test-suite health and regression intelligence. Validates skill conformance (frontmatter, manifest coverage, resolver coverage). Runs the project test suite in tiered phases (unit / evals / integration / system health), classifies failures, and produces a regression-aware report.
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.
Validate and auto-repair YAML frontmatter on brain pages. Catches malformed pages before they enter the brain (missing closing
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.
Baseado na classificação ocupacional SOC
| 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"] |
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.
Retrieve when ANY of these holds AND the page isn't already loaded in context:
Skip trivial passing mentions, logistics pings, and anything already loaded. Judgment first — retrieve when it changes the quality of the reply, not reflexively.
Escalate only as far as the task needs:
get_page <slug> (MCP) — read the page before relying on specifics.graph / backlinks for the slug.Resolve only the name(s) the current task needs, use them, drop them. No bulk-loading the inner circle.
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.