compile-knowledge

Compile Knowledge

Overview

Durable knowledge is worth keeping as many small, interlinked markdown files compiled over time and surfaced through an index — not as one giant doc, a chat log, or a one-off notes.md that rots. This skill makes compiling consistent, so what an agent learns in one session is retrievable in the next one instead of being re-derived from scratch.

The shape is deliberately boring: one fact per file, a one-line description that recall matches against, [[slug]] links between related files, and a single index line per entry. The hard part is not the format — it is the discipline of writing only what is durable, and of updating an existing file instead of creating a near-duplicate.

When to Use This Skill

• Use when you have just produced research, competitive intel, a digest, or an

investigation result, and are about to close the task — compile before you close.

• Use when you learn a non-obvious fact the hard way (a tool that fails silently, a

measurement that contradicts the docs, a constraint nobody wrote down).

• Use when the user says "save this", "write this to the wiki", "update the memory",

"log this finding", "structure this knowledge", or "follow the karpathy method".

• Do not use it for routine work. A deploy, a restart, or a one-line fix usually

produces nothing durable, and filler pollutes recall.

How It Works