wiki-skills plugin

Claude Code plugin for a personal wiki per Karpathy's pattern: the agent grows pages from sources and answers with citations.

  • 189 ★ on the repository
  • Last commit
  • MIT
Plugin

Minimal access

Why this level

  • The pre-commit hook and `core.hooksPath` setting change git behavior in the wiki repository.
All reasons and checks

kfchou/wiki-skills

Install

Works in

In your terminal, with SkillFoxx CLI

npx skillfoxx add plugins/wiki-skills

Detects the agents on your machine, shows the access level and pins the version.

Other ways to install

Access and checks

How we review

Minimal accessThe tool runs nothing and makes no network calls.

  • The pre-commit hook and `core.hooksPath` setting change git behavior in the wiki repository.

This is third-party code. Review the repository files before installing.

What it does

wiki-skills is a Claude Code plugin implementing Andrej Karpathy's LLM Wiki pattern. Instead of searching raw documents each time, the agent keeps an interlinked Markdown wiki and grows it with every new source. The plugin ships seven skills: `wiki-init` bootstraps a wiki, `wiki-ingest` adds an article, URL, file or transcript, `wiki-query` answers from the wiki and files the answer as a page on request, `wiki-lint` checks for contradictions, orphans and broken links, `wiki-update` revises pages showing a diff, `wiki-audit` verifies each footnote against its source, and `wiki-merge` consolidates duplicates. In a git repository `wiki-init` installs a pre-commit hook that blocks a commit on an unresolved contradiction or a broken `[[link]]`.

Who it is for. Researchers and developers who accumulate notes and papers on a topic and want an agent to maintain them as a linked knowledge base instead of re-searching each time.

Good fit when

  • A wiki on a research topic is built from a dozen articles and transcripts.
  • An answer is saved as a cited page so it need not be derived again.
  • Every few ingests a lint pass checks the wiki for orphans and contradictions between pages.
  • A page's footnotes are verified against the originals before publishing.

Not a fit when

  • You need a one-off summary of a single document, so a wiki is overkill.
  • The environment is not Claude Code: the README covers only that.
  • Knowledge cannot be kept in files next to the project.

Example request

Create a wiki on RAG, add three articles from links and answer a question from them, saving the answer as a page.

Limitations

Installation targets Claude Code, and the author cannot confirm other harnesses. The `bin/` scripts need `uv`. `wiki-audit strong` uses the `codex` or `gemini` CLI, otherwise a Claude subagent does the check and the signal is weaker. The wiki grows inside your repository, and the hook changes git configuration through `core.hooksPath`. Wiki pages and the log live in your repository, so backups are on you; the author has not tested the scheme outside Claude Code.

How to disable. Run `/plugin uninstall wiki-skills@wiki-skills` and `/plugin marketplace remove wiki-skills`. Remove the generated wiki and the `core.hooksPath` hook yourself.

FAQ

What does a typical workflow look like?

`wiki-init` first, then `wiki-ingest` for each source in turn. Questions go through `wiki-query`, with a periodic `wiki-lint` every five to ten ingests.

Is git required?

No, but it is recommended. Without git the wiki keeps a plain `wiki/log.md` and installs no hook scripts or git configuration.

What does wiki-audit strong do?

It adds a pass by a different model, `codex` or `gemini`, and records disagreements with the normal check. Without those CLIs a Claude subagent runs instead, with a weaker signal.

How can I check that a page is accurate?

Run `wiki-audit` on the page: it flags uncited claims and verifies each footnote against its source. The verdict lands in `wiki/pages/audit-<page>-<date>.md`.

What does wiki-merge do?

It consolidates two pages on the same concept or splits an overloaded slug into qualified pages, rechecking links and backlinks along the way.

Discussion

No questions or reviews yet.

Plugins

LLM Wiki Manager keeps a personal Markdown wiki through an agent: it ingests sources, links pages and answers with citations

PluginExtended access73Repository stars

A Claude Code plugin for Obsidian: stores sources, compiles linked wiki pages and answers from the accumulated knowledge.

PluginExtended access110Repository stars

A plugin that turns PDFs, articles and notes into a shared markdown wiki that agents search, cite and keep growing

PluginExtended access123Repository stars

A Claude Code plugin that runs a Karpathy-style wiki on Logseq or Obsidian and splits knowledge into memory rules and a deep wiki

PluginExtended access169Repository stars

Karpathy LLM Wiki

karpathy-llm-wiki

A skill for a personal knowledge base the model maintains: ingest sources, compile cited articles, lint integrity

SkillExtended access2.7KRepository stars

Turns session history of Claude Code, Codex, Cursor and Gemini CLI into a searchable wiki on Karpathy's LLM Wiki pattern, locally

PluginBroad access402Repository stars

Comparison with similar tools

Cards that share the main search query, and how they differ.

ToolOfficialAuthenticationRepository starsMain difference
wiki-skills (this card)no189
LLM Wikino107installs a CLI and four skills for an Obsidian vault; wiki-skills is a plugin with seven skills and a commit hook
LLM Wiki Memorynonot required130turns agent sessions into a wiki with git history; wiki-skills grows from external sources and audits footnotes

README in short

The wiki has layers: raw sources, pages and an overview. The index is not hand-maintained; a script builds it from page metadata.

README badge

Report a problem