Skip to content

LLM Wiki skill (llm-wiki)

The bundled llm-wiki skill (research/llm-wiki, v2.1.0) implements Andrej Karpathy’s LLM Wiki pattern: an interlinked markdown knowledge base that compiles knowledge once instead of re-deriving it per query. Cross-references already exist, contradictions are flagged, synthesis reflects everything ingested. Unlike RAG, nothing is re-discovered.

The skill is the estate’s single wiki mechanism (decision 2026-09-13): a Repo Wiki is simply this skill applied at a repository root. There is no separate home-grown mechanism to maintain.

Situation Use the skill?
Navigating a repo’s documentation (verified paths, typed relations) Yes — as a Repo Wiki (index file at the repo root)
A work directory that accumulates knowledge (research dossiers, reform folders, watch lists) Yes — full wiki, SCHEMA + index + layers
Personal notes in Google Drive (PARA) No — those belong to the Drive Vault
One-off glossary or single concept No — use CONTEXT.md
Quick web lookups No — plain search
wiki/
├── SCHEMA.md # Conventions of THIS wiki: domain, tags, local adaptations
├── index.md # Page catalog: one-line summaries, [[wikilinks]]
├── log.md # Append-only action log (rotated yearly past 500 entries)
├── raw/ # Immutable sources (articles, papers, transcripts)
├── entities/ concepts/ comparisons/ queries/

Three layers: raw/ (immutable sources) → agent-owned pages (entities, concepts, comparisons, queries) → navigation (SCHEMA.md, index.md, log.md).

Step What to do
1 Load the skill: skill_view(name='llm-wiki')
2 Pick the location (a repo root for a Repo Wiki, or any work directory)
3 Define the domain with the user (specific, not generic)
4 Write SCHEMA.md tailored to the domain — declare local adaptations here (WIKI_PATH can stay unset; orientation is manual via SCHEMA)
5 Write the initial index.md (sectioned catalog)
6 Write the initial log.md (creation entry)
7 Suggest first sources to ingest
Operation Trigger Effect
Ingest « ingest ce lien / ce PDF / ce texte » Raw source stored in raw/; existing pages updated; new pages only past the schema thresholds; index.md + log.md updated; changes reported
Query Any question in the wiki’s domain index.md read first (plus search_files past 100 pages); answer synthesized and cited to wiki pages; valuable answers filed back
Lint « audit / health-check du wiki » Orphan pages, broken links, index completeness, frontmatter validation, stale content, contradictions, source drift, page size, tag audit, log rotation — grouped by severity

Repo Wiki: applying the skill to one repository

Section titled “Repo Wiki: applying the skill to one repository”

A Repo Wiki is the skill applied at a repository root. Conventions established on the YEU pilot (2026-09-12):

  • Index file: WIKI.md (the historical pilot name; a local SCHEMA may declare a non-standard index name — this is a documented local adaptation, not a second mechanism).
  • Index format: tables of verified paths + typed relations (→ defines · → decides · → details · → audits · → generates · → references · → feeds).
  • No invented paths: every entry is checked against the tree before writing (pilot exit criterion).
  • Manual updates after sessions: the wiki is not auto-rewritten; a session that changes repo docs updates WIKI.md and appends log.md.
  • Existing docs stay in place: they are both source and page — never moved into raw/, never copied into the index.

Adding a Repo Wiki to a new repo: add SCHEMA.md + log.md at the root, write the WIKI.md index with verified paths, point the repo’s AGENTS.md (Carte) at it, commit on its own branch, review before merge.

Instance Kind Since Notes
YEU (repo) Repo Wiki — WIKI.md index, typed relations 2026-09-12 (pilot), SCHEMA/log added 2026-09-13 Paths verified, 0 bogus links
Hostinger-VPS-hermes-instance (work dir) Full wiki — SCHEMA + index + layers 2026-09-13 Reform workdir; existing docs indexed in place

WIKI_PATH is not set globally: each wiki orients manually via its own SCHEMA.md. Generalization to other repos is open — the YEU exit criteria (verified paths, no invented links) are met.

  • Glossary: Repo Wiki, Bibliothèque
  • Hermes context injection — WIKI.md is read on demand, never injected
  • The skill body itself (skill_view(name='llm-wiki')) for full operations and pitfalls