agentleFS
jellydnjellydn/my-ai-tools/skills/llm-wiki/SKILL.md

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

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-chenSkill

    touchdesigner-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-chenSkill

    teams-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

  • mae616Skill

    p5js

    p5.js(クリエイティブコーディング)のProcessing由来「コードでスケッチ」思想を軸に、setup/drawループ・座標系・インタラクション・パフォーマンス最適化を整理する。p5.js、Processing、クリエイティブコーディング、ジェネラティブアート、インタラクティブ表現、ビジュアルプログラミング、Canvas描画、パーティクル、フラクタル、ノイズ表現に関する相談で必ず使うこと。ユーザーが「コードでアート」「動くビジュアル」「インタラクティブな描画」と言った場合にも適用する。

    Also in 12 projects that use this

  • aivrarSkill

    competitor-news-monitor

    Watch named companies for material news; cited digests.

    Also in 6 projects that use this

  • math-incSkill

    heartmula

    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-Chen1999Skill

    claude-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

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
  1. Very specific:

    Create the directory structure: raw/, wiki/, wiki/entities/, wiki/concepts/, wiki/sources/

    line 55
  2. Very specific:

    Create wiki/index.md from $SKILL_PATH/templates/index.md

    line 57
  3. Very specific:

    Create a starter wiki/overview.md stating the wiki's domain and purpose

    line 59
  4. Distinctive:

    Done when: all five files and directories exist and the user has been told the next step.

    line 62
  5. Distinctive:

    Read the source file; share key takeaways and ask the user what to emphasize

    line 68
  6. Very specific:

    Create wiki/sources/<slug>.md with a structured summary

    line 69
  7. Very specific:

    Update wiki/overview.md if the source shifts the big picture

    line 70
  8. Very specific:

    Create or update entity pages in wiki/entities/ for key people, places, organizations

    line 71
  9. Very specific:

    Create or update concept pages in wiki/concepts/ for key ideas and themes

    line 72
  10. Distinctive:

    Add a contradiction note on any existing page where this source conflicts with current content

    line 73
  11. Very specific:

    Update wiki/index.md — every new or modified page must appear with a one-line summary

    line 74
  12. Very specific:

    Done when: every affected page is updated, every new or changed page appears in index.md, and the log entry is appended.

    line 77
  13. Very specific:

    Read wiki/index.md to identify the most relevant pages

    line 83
  14. Distinctive:

    Read those pages in full

    line 84
  15. Very specific:

    If the answer is a valuable synthesis (comparison, analysis, discovered connection), offer to file it as a new wiki page.

    line 86
  16. Distinctive:

    Done when: all six issue types are checked and reported, suggestions are given, and the log entry is appended.

    line 107
  17. Distinctive:

    Done when: all four items are reported.

    line 115

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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 workflows

Templates for all three layers are in $SKILL_PATH/templates/.


For "init [DIRECTORY]":

  1. Create the directory structure: raw/, wiki/, wiki/entities/, wiki/concepts/, wiki/sources/
  2. Copy $SKILL_PATH/templates/schema.md to CLAUDE.md (or AGENTS.md)
  3. Create wiki/index.md from $SKILL_PATH/templates/index.md
  4. Create wiki/log.md from $SKILL_PATH/templates/log.md
  5. Create a starter wiki/overview.md stating the wiki's domain and purpose
  6. 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>":

  1. Read the source file; share key takeaways and ask the user what to emphasize
  2. Create wiki/sources/<slug>.md with a structured summary
  3. Update wiki/overview.md if the source shifts the big picture
  4. Create or update entity pages in wiki/entities/ for key people, places, organizations
  5. Create or update concept pages in wiki/concepts/ for key ideas and themes
  6. Add a contradiction note on any existing page where this source conflicts with current content
  7. Update wiki/index.md — every new or modified page must appear with a one-line summary
  8. 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>":

  1. Read wiki/index.md to identify the most relevant pages
  2. Read those pages in full
  3. Synthesize an answer with citations to specific wiki pages
  4. 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.md and append to wiki/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 queries

Optional: 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-wiki

Tips

  • 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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.