Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →astro-han/karpathy-llm-wiki
Use when building or maintaining a personal LLM-powered knowledge base. Triggers: ingesting sources into a wiki, querying wiki knowledge, linting wiki quality, 'add to wiki', 'what do I know about', or any mention of 'LLM wiki' or 'Karpathy wiki'.
Passed 14 of 19 test cases with the skill, and 7 of 19 without it.
and 7 more in the full report
8 fixed8 passed either way6 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
While compiling a raw article into a wiki page, the source states that the benchmark achieved '42K requests/sec'. Should I normalize this to '42,000 requests/sec' for clean formatting across the wiki, or copy the exact representation '42K'?
| Checked | Without skill | With skill |
|---|---|---|
| Preserves literal value 42K from raw source instead of converting to 42,000 | Missed | Passed |
The instructions your model reads when the skill loads.
Build and maintain a personal knowledge base using LLMs. You manage two directories: raw/ (immutable source material) and wiki/ (compiled knowledge articles). Sources go into raw/, you compile them into wiki articles, and the wiki compounds over time.
Core ideas from Karpathy:
Three layers, all under the user's project root:
raw/ — Immutable source material. You read, never modify. Organized by topic subdirectories (e.g., raw/machine-learning/).
wiki/ — Compiled knowledge articles. You have full ownership. Organized by topic subdirectories, one level only: wiki/<topic>/<article>.md. Contains two special files:
wiki/index.md — Global index. One row per article, grouped by topic, with link + summary + Updated date.wiki/log.md — Append-only operation log.SKILL.md (this file) — Schema layer. Defines structure and workflow rules.
Templates live in references/ relative to this file. Read them when you need the exact format for raw files, articles, archive pages, or the index.
Triggers only on the first Ingest. Check whether raw/ and wiki/ exist. Create only what is missing; never overwrite existing files:
raw/ directory (with .gitkeep)wiki/ directory (with .gitkeep)wiki/index.md — heading # Knowledge Base Index, empty bodywiki/log.md — heading # Wiki Log, empty bodyIf Query or Lint cannot find the wiki structure, tell the user: "Run an ingest first to initialize the wiki." Do not auto-create.
Every load-bearing fact in wiki/ — numbers, dates, direct quotes — exists verbatim in the raw/ files linked by that article's Raw field. Compile establishes this invariant (locate before you write); lint verifies it (scripts/check_evidence.py greps the high-signal literals — suffixed or large numbers, decimals, ISO dates, longer quotes — in the linked raws; the compile-time locate-before-write rule covers the rest). Because raw/ is immutable, a verified article stays verified; the script re-checks the whole wiki in seconds, so there is no incremental state to maintain.
test cases passed, vs 7 / 19 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.