llm-wiki
Skill16 starsChanged 6 months agoMITView on GitHub
General-purpose personal knowledge base built on Karpathy's LLM Wiki pattern: an immutable raw/ source layer, a generated human-readable wiki/ layer, and a CLAUDE.md schema/contract. Portable, stdlib-only, Obsidian-compatible. Use when the user says \"个人知识库\", \"llm wiki\", \"personal wiki\", \"ingest into wiki\", \"建/查个人知识库\", or wants a durable cross-project notes graph that is NOT research-lifecycle specific. For paper/idea/experiment/claim research graphs use /research-wiki instead.
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 repository56 other files it gives its agents.
- argument-stress-testSkill
- citation-auditSkill
- comm-lit-review-claude-singleSkill
- comparative-lawSkill
- exa-searchSkill
- feishu-notifySkill
- figure-descriptionSkill
- figure-specSkill
- formula-derivationSkill
- grant-proposalSkill
- legal-writingSkill
- mermaid-diagramSkill
- novelty-checkSkill
- overleaf-syncSkill
- paper-claim-auditSkill
- paper-compileSkill
- paper-figureSkill
- paper-illustrationSkill
- paper-planSkill
- paper-posterSkill
- paper-slidesSkill
- paper-writeSkill
- paper-writingSkill
- prism-pipelineSkill
- proof-checkerSkill
- proof-writerSkill
- rebuttalSkill
- research-litSkill
- research-pipelineSkill
- research-refine-pipelineSkill
- research-refineSkill
- research-reviewSkill
- research-wikiSkill
- semantic-scholarSkill
- comm-lit-reviewSkill
- feishu-notifySkill
- formula-derivationSkill
- grant-proposalSkill
- mermaid-diagramSkill
- novelty-checkSkill
- paper-compileSkill
- paper-figureSkill
- paper-illustrationSkill
- paper-planSkill
- paper-posterSkill
- paper-slidesSkill
- paper-writeSkill
- paper-writingSkill
- proof-writerSkill
- rebuttalSkill
- research-litSkill
- research-pipelineSkill
- research-refine-pipelineSkill
- research-refineSkill
- research-reviewSkill
- statute-case-mapperSkill
The file
We split this skill into the rules it gives an agent
11 rules. 0 are common, 4 are distinctive, and 7 are very specific to this project.
0
Common
Most of the 76 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 62
All structure and search logic lives in two stdlib-only scripts (per the integration contract — one implementation, not copy-pasted prose):
- Very specific: line 86
After init, tell the user: drop sources into raw/, then run /llm-wiki ingest.
- Very specific: line 107
Add a one-line entry under the right section of wiki/index.md for any new page.
- Distinctive: line 116
Always run this before broad external search.
- Very specific: line 135
Run lint to find orphans and missing-index entries.
- Very specific: line 136
Add any orphaned durable pages to wiki/index.md.
- Distinctive: line 144
Prefer updating an existing page over creating a near-duplicate.
- Very specific: line 145
Every write appends wiki/log.md.
- Very specific: line 146
Every substantive claim carries a status tag.
- Very specific: line 147
Use Obsidian-style [[topics/foo]] links so the graph stays navigable.
- Distinctive: line 153
When linking a project to a local wiki, this is the general-purpose target.
“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: Portable Personal Knowledge Base
Subcommand: $ARGUMENTS
Overview
/llm-wiki builds and maintains a general-purpose personal knowledge base
that follows Karpathy's LLM Wiki pattern:
compile knowledge once into durable, linked Markdown; keep it current; never
re-derive on every query.
It is discipline-agnostic and Obsidian-compatible. Use it for durable
domain knowledge, reading notes, distilled answers, and any long-lived personal
KB. For the research-lifecycle graph (papers / ideas / experiments / claims with
typed edges) use /research-wiki instead — the two
do not share directories and should not be merged.
This skill matches the external-wiki shape documented in
shared-references/local-wiki-link.md, so any wiki created here is
auto-detectable by the rest of Prism.
Three layers
| Layer | Path | Mutability | Purpose |
| Raw | raw/ | immutable — never edit/delete | source material: PDFs, clippings, transcripts, dumps |
| Wiki | wiki/ | agent-generated | distilled, linked, durable knowledge |
| Schema | CLAUDE.md | human-owned | how the wiki is built & linted |
<root>/
raw/ immutable sources
wiki/
index.md navigation catalog
log.md append-only timeline
topics/ concepts/ sources/ memos/
scripts/query_wiki.py shipped search helper
scripts/llm_wiki.py shipped scaffold/lint helper
CLAUDE.md schema + maintenance contractStatus tags
Tag every non-trivial claim so future reads know how much to trust it:
已确认— confirmed, stable prior knowledge有争议— contested; preserve competing positions推论— inference; usable as reasoning, not as a source待核验— unverified; do NOT cite as settled support
Claims with no source anchor MUST be tagged 待核验.
Canonical helpers
All structure and search logic lives in two stdlib-only scripts (per the integration contract — one implementation, not copy-pasted prose):
tools/llm_wiki.py—init,lint,logtools/query_wiki.py— keyword search
The repo copies live under Prism's tools/; init also copies both into the
wiki's own scripts/ so the wiki is self-contained and portable.
Subcommands
init <path> — scaffold a new wiki
python3 tools/llm_wiki.py init <path>Creates the three-layer structure, seed index.md / log.md, a starter
CLAUDE.md schema, an example concept page, and copies the search/scaffold
helpers into <path>/scripts/. Idempotent — existing files are never
overwritten.
After init, tell the user: drop sources into raw/, then run /llm-wiki ingest.
ingest [raw-path] — fold a source into the wiki
For each new item under raw/ (or the given path):
- Read the raw source (do not modify it).
- Query first to avoid duplication:
python3 <root>/scripts/query_wiki.py --wiki <root>/wiki --query "<topic>" --top 8 - Write/update a
wiki/sources/<slug>.mdsummary page with a link or anchor back to theraw/item. - Fold durable facts into the relevant
wiki/topics/orwiki/concepts/page. Prefer updating an existing page over creating a near-duplicate. Tag each claim with a status. Add[[wiki-links]]to related pages. - Append the log and update the index:
Add a one-line entry under the right section ofpython3 <root>/scripts/llm_wiki.py log <root> --msg "ingest — <pages> — <source>"wiki/index.mdfor any new page.
query <topic> — search prior knowledge
python3 <root>/scripts/query_wiki.py --wiki <root>/wiki --query "<topic>" --top 8Always run this before broad external search. Read only the top relevant pages. Treat conclusions by their status tag (see above).
lint — hygiene check
python3 <root>/scripts/llm_wiki.py lint <root>Reports broken links, missing H1 titles, untagged substantive pages, stale pages (>180d), conflicting status on one line, orphan pages (no incoming links and not in index), and index references to missing pages. Exit code 1 on error-level findings (missing-page references). Fix warnings opportunistically; fix errors before relying on the wiki.
sync — reconcile index/log with disk
Rebuild coverage after manual edits:
- Run
lintto find orphans and missing-index entries. - Add any orphaned durable pages to
wiki/index.md. - Append a
log.mdentry summarizing the reconciliation.
Write-back rules (hard)
- Never modify or delete anything under
raw/. - Prefer updating an existing page over creating a near-duplicate.
- Every write appends
wiki/log.md; new pages also updatewiki/index.md. - Every substantive claim carries a status tag; unsourced claims are
待核验. - Use Obsidian-style
[[topics/foo]]links so the graph stays navigable.
Relationship to other Prism wiki systems
- External wiki protocol (
shared-references/local-wiki-link.md): a wiki created by/llm-wiki initis exactly the shape that protocol auto-detects. When linking a project to a local wiki, this is the general-purpose target. /research-wiki: the research-lifecycle graph (papers/ideas/experiments/ claims +graph/edges.jsonl). Use both when useful; do not merge directories. Query/llm-wikifor durable domain knowledge; update/research-wikifor the project's research graph.
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.

