super-brain: Skill for Claude Code

Query

Answer from the wiki, not from memory, and keep the answer so the next question starts further along.

Write the answer and every file you produce in the language the human is using.

How to invoke

• Any question the vault plausibly covers
• "What do we know about X?"
• "Compare X and Y from what I have"
• "Write me a briefing on X"
• /query

How it works

1. Find the pages

Read 4-Knowledge/index.md first. It is the map, and it exists so you do not have to read every page to find three.

Pick the pages that bear on the question, entity pages included when the question names a person, company or tool.

If the index promises a page that is not on disk, or you find a page the index never lists, tell the human. Both are real findings.

2. Read them

Read the pages you picked, in full. Follow [[links]] one hop out when the question sits between two topics.

3. Answer

Cite every claim with [source: page-name.md], naming the wiki page you actually read.

Where the wiki disagrees with itself, show both sides and name the sources. A > CONTRADICTION: marker is a finding to surface, not noise to smooth over.

Where the wiki is thin, say so in the answer. If you add something from outside the vault, mark it plainly as outside knowledge so the human can tell the two apart.

4. Save the output

Write 9-Outputs/[YYYY-MM-DD]-[short-slug].md:

---
question: [the question, as asked]
date: [YYYY-MM-DD]
pages: [wiki pages used]
filed_back: [page name, or: no]
---

# [Question as a title]

[The answer, with [source: page-name.md] citations]

## What this is built on
- [[Page A]] - what it contributed
- [[Page B]] - what it contributed

## Gaps
[What the wiki could not answer. The most useful section in the file: it tells
the human what to read next.]

A one-line lookup does not need a file. Say out loud that you skipped it, so the human knows this answer was not kept.

When the answer has a shape that prose flattens - a comparison across dimensions, a timeline, a distribution - offer the better format and save it beside the markdown under the same slug. The format rules are in 8-System/brain.md under Conventions.