karpathy-wiki-read
karpathy-wiki read
You loaded this skill because the user asked a question (per Iron Rule 4 in the loader: NO ANSWERING ANY USER QUESTION WITHOUT ORIENTING FIRST). Your job is to determine whether the wiki covers the answer, retrieve the coverage, and either cite-and-answer from the wiki or fall through to web search — without ever pre-classifying the question as "wiki-irrelevant."
The 6-step ladder
Every step is deterministic. There is no agent judgement at branch points; each branch is gated on a counted or boolean condition.
Step A — Orient
Read these files in order:
<wiki>/schema.md— taxonomy, conventions, thresholds.- The relevant
<wiki>/<category>/_index.mdfor the question's apparent topic. If the question crosses categories or you cannot tell which category applies, read<wiki>/index.md(the root MOC).
If you have already oriented earlier in this session, skip to Step B — the schema and index content are already in your working memory. Orientation is once per session.
Step B — Count signal-matching candidates
More from toolboxmd/karpathy-wiki
karpathy-wiki
|
8karpathy-project-wiki
Build and maintain a persistent Karpathy Project Wiki — an auto-updating knowledge base for your codebase based on Andrej Karpathy's LLM Wiki pattern. TRIGGER when: user modifies project files (code, configs, docs), adds new modules, refactors architecture, merges PRs, asks about project architecture ('how does auth work', 'what's the data flow', 'where is X implemented', 'explain this module', 'what patterns does this project use'), or requests a documentation health check ('is the wiki up to date', 'check the docs', 'find undocumented code'). Also triggers when git shows changes since last wiki update. DO NOT TRIGGER when: user wants a general research wiki on external topics (use karpathy-wiki instead), asks to read a single specific file, or asks general programming questions unrelated to this project.
3karpathy-wiki-ingest
|
2karpathy-wiki-capture
|
2using-karpathy-wiki
|
2