llm-wiki

Organize sources into a cross-referenced markdown wiki with frontmatter schema.

Updated Jun 1, 2026
One-click install
npx skills add https://github.com/SatangThevalue/ai-skills --skill llm-wiki-satangthevalue
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: llm-wiki
Source: https://github.com/SatangThevalue/ai-skills/tree/main/skills/research/llm-wiki
Command: npx skills add https://github.com/SatangThevalue/ai-skills --skill llm-wiki-satangthevalue

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Karpathy's LLM Wiki solves the challenge of creating a persistent, interlinked markdown knowledge base that can be ingested, updated, and queried without starting from scratch each time.

Core Features & Use Cases

  • Ingest and organize sources into a cross-referenced wiki structure with layers for raw materials, wiki content, and schema.
  • Maintain provenance, tagging, and consistent page structure to enable reliable questioning and research workflows.
  • Use cases include starting a wiki, updating entries from new sources, linting for consistency, and referencing knowledge across notes.

Quick Start

Set up the wiki path and begin ingesting sources to build your evolving knowledge base.

Frequently Asked Questions about llm-wiki

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build an interlinked markdown wiki from research sources?

To build an interlinked markdown wiki, ingest raw sources into a cross-referenced structure with layers for raw materials and content. The wiki enforces frontmatter schemas like title, tags, and sources for reliable navigation.

Can I use this knowledge base with Obsidian for note-taking?

Yes, the knowledge base supports Obsidian integration by enforcing consistent markdown page structures and cross-linking rules. This enables reliable questioning and research workflows within your note-taking environment.

How do I maintain provenance when updating wiki entries from new sources?

To maintain provenance when updating wiki entries, the schema requires frontmatter fields including sources, created, and updated dates. This tracks origin and modifications across your evolving knowledge base.

What is the best way to organize a persistent markdown knowledge base without losing context?

The best way to organize a persistent markdown knowledge base is compiling sources into a layered structure with enforced schemas. This provides provenance, tagging, and cross-linking rules to prevent losing context.

How do I lint my markdown wiki for consistency and broken cross-links?

You can lint your markdown wiki for consistency by checking pages against the enforced frontmatter schema and cross-linking rules. This validates structure, tags, and source references across the knowledge base.

Does this wiki schema require frontmatter for every page entry?

Yes, the wiki schema requires frontmatter for every page entry, mandating fields like title, created, updated, type, tags, and sources. This ensures consistent structure and provenance across the knowledge base.