llm-wiki
Skill127 starsChanged 27 days agoMITView on GitHub
Build a persistent compounding wiki from raw sources using the LLM Wiki pattern
94 other projects use a version of this.
Adopted by
Most recently taken up by
- Damon-GSY/skillstheir own version, first seen Nov 8, 2026
- DracoUnion/skillstheir own version, first seen Nov 8, 2026
- Ar9av/obsidian-wikitheir own version, first seen Nov 8, 2026
- fralapo/awesome-agent-skillstheir own version, first seen Nov 7, 2026
- delorenj/skillstheir own version, first seen Nov 7, 2026
- ianchanning/skillstheir own version, first seen Nov 6, 2026
Used with
Projects with it also use touchdesigner-mcp, teams-meeting-pipeline and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
john-data-chenSkilltouchdesigner-mcp
Control a running TouchDesigner instance via twozero MCP — create operators, set parameters, wire connections, execute Python, build real-time visuals. 36 native tools.
Also in 7 projects that use this
john-data-chenSkillteams-meeting-pipeline
Operate the Teams meeting summary pipeline via Hermes CLI — summarize meetings, inspect pipeline status, replay jobs, manage Microsoft Graph subscriptions.
Also in 9 projects that use this
mae616Skillp5js
p5.js(クリエイティブコーディング)のProcessing由来「コードでスケッチ」思想を軸に、setup/drawループ・座標系・インタラクション・パフォーマンス最適化を整理する。p5.js、Processing、クリエイティブコーディング、ジェネラティブアート、インタラクティブ表現、ビジュアルプログラミング、Canvas描画、パーティクル、フラクタル、ノイズ表現に関する相談で必ず使うこと。ユーザーが「コードでアート」「動くビジュアル」「インタラクティブな描画」と言った場合にも適用する。
Also in 12 projects that use this
aivrarSkillcompetitor-news-monitor
Watch named companies for material news; cited digests.
Also in 6 projects that use this
math-incSkillheartmula
Set up and run HeartMuLa, the open-source music generation model family (Suno-like). Generates full songs from lyrics + tags with multilingual support.
Also in 7 projects that use this
Ivy-Chen1999Skillclaude-history-ingest
Ingest Claude Code conversation history into the Obsidian wiki. Use this skill when the user wants to mine their past Claude conversations for knowledge, import their ~/.claude folder, extract insights from previous coding sessions, or says things like "process my Claude history", "add my conversations to the wiki", "what have I discussed with Claude before". Also triggers when the user mentions their .claude folder, Claude projects, session data, past conversation logs, local-agent-mode sessions, or audit logs.
Also in 3 projects that use this
Other versions94 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 94
- Ar9av/obsidian-wiki★ 3.7ksame name
- sdyckjq-lab/llm-wiki-skill★ 2.5ksame name
- staruhub/ClaudeSkills★ 705same name
- lewislulu/llm-wiki-skill★ 654same name
- zosmaai/pi-llm-wiki★ 622same name
- Tommy-yw/RunbookHermes★ 546same name
- aivrar/portable-hermes-agent★ 239same name
- luotwo/llm-wiki★ 218same name
- sammcj/agentic-coding★ 169same name
- MehmetGoekce/llm-wiki★ 163same name
84 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository38 other files it gives its agents.
- AGENTS.mdAGENTS.md
- wiki/AGENTS.mdAGENTS.md
- wiki/CLAUDE.mdCLAUDE.md
- accountable-engineeringSkill
- adrSkill
- babysit-prSkill
- blindspot-passSkill
- capability-experimentsSkill
- codemapSkill
- code-quality-reviewSkill
- code-reviewSkill
- commit-atomicSkill
- context-discoverySkill
- diagnosing-bugsSkill
- doc-searchSkill
- docs-updateSkill
- draft-pull-requestSkill
- git-contextSkill
- handoffsSkill
- implementation-loggerSkill
- implement-specSkill
- orchestrating-fusionSkill
- pickupSkill
- plannotator-setup-goalSkill
- portless-localSkill
- prdSkill
- pr-reviewSkill
- prSkill
- qmd-knowledgeSkill
- quiz-meSkill
- ralphSkill
- retroSkill
- security-auditSkill
- slopSkill
- spec-interviewSkill
- tddSkill
- tmuxSkill
- visual-prSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
17 rules. 0 are common, 6 are distinctive, and 11 are very specific to this project.
0
Common
Most of the 76 edited versions we read keep these.
6
Distinctive
This author's own choices. Worth a look.
11
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 55
Create the directory structure: raw/, wiki/, wiki/entities/, wiki/concepts/, wiki/sources/
- Very specific: line 57
Create wiki/index.md from $SKILL_PATH/templates/index.md
- Very specific: line 59
Create a starter wiki/overview.md stating the wiki's domain and purpose
- Distinctive: line 62
Done when: all five files and directories exist and the user has been told the next step.
- Distinctive: line 68
Read the source file; share key takeaways and ask the user what to emphasize
- Very specific: line 69
Create wiki/sources/<slug>.md with a structured summary
- Very specific: line 70
Update wiki/overview.md if the source shifts the big picture
- Very specific: line 71
Create or update entity pages in wiki/entities/ for key people, places, organizations
- Very specific: line 72
Create or update concept pages in wiki/concepts/ for key ideas and themes
- Distinctive: line 73
Add a contradiction note on any existing page where this source conflicts with current content
- Very specific: line 74
Update wiki/index.md — every new or modified page must appear with a one-line summary
- Very specific: line 77
Done when: every affected page is updated, every new or changed page appears in index.md, and the log entry is appended.
- Very specific: line 83
Read wiki/index.md to identify the most relevant pages
- Distinctive: line 84
Read those pages in full
- Very specific: line 86
If the answer is a valuable synthesis (comparison, analysis, discovered connection), offer to file it as a new wiki page.
- Distinctive: line 107
Done when: all six issue types are checked and reported, suggestions are given, and the log entry is appended.
- Distinctive: line 115
Done when: all four items are reported.
“Common” is measured: kept by at least 6 in 10 of the 76 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
LLM Wiki
Build and maintain a persistent, compounding knowledge wiki from raw sources.
Based on Karpathy's LLM Wiki pattern: the LLM incrementally integrates each new source into a structured wiki of markdown files — updating entity pages, flagging contradictions, strengthening cross-references. Synthesis is compiled once and kept current, not re-derived on every query.
Usage
/llm-wiki <ACTION> [ARGUMENTS]
Actions
- init [DIRECTORY] - Initialize a new wiki (default:
wiki/) - ingest
<SOURCE>- Process a source file and integrate it into the wiki - query
<QUESTION>- Answer a question using the wiki as the knowledge base - lint - Health-check the wiki for contradictions, orphan pages, and stale content
- status - Show a summary of the wiki's current state
Architecture
your-wiki/
├── raw/ # Immutable source documents — you add, LLM never modifies
│ └── assets/ # Downloaded images referenced by sources
├── wiki/ # LLM-generated and maintained pages
│ ├── index.md # Catalog of all pages with one-line summaries
│ ├── log.md # Append-only record of all operations
│ ├── overview.md
│ ├── entities/ # People, places, organizations
│ ├── concepts/ # Ideas, topics, themes
│ └── sources/ # One summary page per source
└── CLAUDE.md # Schema: wiki conventions and per-operation workflowsTemplates for all three layers are in $SKILL_PATH/templates/.
For "init [DIRECTORY]":
- Create the directory structure:
raw/,wiki/,wiki/entities/,wiki/concepts/,wiki/sources/ - Copy
$SKILL_PATH/templates/schema.mdtoCLAUDE.md(orAGENTS.md) - Create
wiki/index.mdfrom$SKILL_PATH/templates/index.md - Create
wiki/log.mdfrom$SKILL_PATH/templates/log.md - Create a starter
wiki/overview.mdstating the wiki's domain and purpose - Tell the user to add sources to
raw/and run/llm-wiki ingest <file>next
Done when: all five files and directories exist and the user has been told the next step.
For "ingest <SOURCE>":
- Read the source file; share key takeaways and ask the user what to emphasize
- Create
wiki/sources/<slug>.mdwith a structured summary - Update
wiki/overview.mdif the source shifts the big picture - Create or update entity pages in
wiki/entities/for key people, places, organizations - Create or update concept pages in
wiki/concepts/for key ideas and themes - Add a contradiction note on any existing page where this source conflicts with current content
- Update
wiki/index.md— every new or modified page must appear with a one-line summary - Append to
wiki/log.md:## [YYYY-MM-DD] ingest | <Source Title>
Done when: every affected page is updated, every new or changed page appears in index.md, and the log entry is appended. A single ingest typically touches 5–15 pages.
For "query <QUESTION>":
- Read
wiki/index.mdto identify the most relevant pages - Read those pages in full
- Synthesize an answer with citations to specific wiki pages
- If the answer is a valuable synthesis (comparison, analysis, discovered connection), offer to file it as a new wiki page; if filed, update
wiki/index.mdand append towiki/log.md
Done when: the question is answered with citations, and any filing decision (page created or skipped) is resolved.
For "lint":
Scan the entire wiki and report on each of the following:
- Contradictions — conflicting claims across pages
- Stale content — pages superseded by newer ingested material
- Orphan pages — pages with no inbound links
- Missing pages — concepts mentioned on multiple pages but lacking their own page
- Broken links —
[[Page Name]]links pointing to non-existent pages - Data gaps — areas a targeted source or web search could fill
Suggest new questions and sources. Ask before making any fixes.
Append to wiki/log.md: ## [YYYY-MM-DD] lint | health check
Done when: all six issue types are checked and reported, suggestions are given, and the log entry is appended.
For "status":
Report: source count in raw/, wiki page count, last 10 entries in wiki/log.md, and any obvious health issues (orphan pages, missing index entries).
Done when: all four items are reported.
Index and log
wiki/index.md — content catalog, updated on every ingest. Every page with a link and one-line summary, organized by category. The LLM reads this first when answering queries.
wiki/log.md — append-only operation log. Entry format: ## [YYYY-MM-DD] <operation> | <title>. Grep-parseable:
grep "^## \[" wiki/log.md | tail -5 # last 5 operations
grep "^## \[.*\] ingest" wiki/log.md # all ingests
grep "^## \[.*\] query" wiki/log.md # all queriesOptional: qmd search
For larger wikis, add qmd — local hybrid BM25/vector search with an MCP server:
bun install -g @tobilu/qmd
qmd collection add ./wiki --name my-wiki
qmd embed
qmd query "how does X relate to Y" -c my-wikiTips
- Obsidian Web Clipper converts web articles to markdown — fast source collection for
raw/. - File good answers: valuable query results (comparisons, analyses, new connections) should become wiki pages — explorations compound the knowledge base just like ingested sources do.
- Ingest one source at a time — read the summaries, check the updates, guide emphasis. You get more value staying in the loop than batch-ingesting unattended.
- The wiki is a git repo of markdown files — version history and collaboration come free.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

