llmkb — local, folder-first LLM knowledge bases
A template and toolkit for LLM knowledge bases that are just a git directory of markdown pages, in the style of Karpathy's LLM-wiki. An agent plus that directory is a complete system: agents ingest sources and file what they learn, the wiki compounds synthesis over time, and a small CLI keeps the bookkeeping honest. No server, no database, no proprietary format.
This repo ships the format spec, a CLI, an optional MCP server, and agent skills. Actual knowledge bases are separate directories stamped out per project — this repo never contains anyone's knowledge.
Install
uv tool install llmkb # or: pipx install llmkb
# optional MCP server:
uv tool install "llmkb[mcp]"
Quickstart
llmkb init my-project-kb --description "notes for my project"
# drop sources into my-project-kb/raw/, then use the kb-ingest skill
llmkb reindex --kb my-project-kb
llmkb lint --kb my-project-kb
llmkb search "some query" --kb my-project-kb
What's in a KB
A knowledge base is a directory:
my-project-kb/
kb.yaml # identity + format version
SCHEMA.md # the writing discipline agents follow
raw/ # curated sources, never modified
wiki/
summaries/ concepts/ entities/
index.md # derived catalog (llmkb reindex rebuilds it)
log.md # append-only operation record
See docs/FORMAT.md for the full versioned contract and examples/example-kb/
for a working example.
CLI
llmkb init <dir>— scaffold a new KB.llmkb reindex— rebuildwiki/index.mdfrom page frontmatter.llmkb lint— catch broken links, orphans, index drift, malformed frontmatter; exit code reflects health.llmkb search <query>— full-text search (SQLite FTS5, cached in.llmkb/).
All commands take --kb <dir> (repeatable; defaults to the current directory)
and tag multi-KB output by name.
MCP server (optional)
llmkb-mcp --kb <dir> runs a read-only MCP stdio server exposing search,
get_page, get_index, and list_kbs to any MCP-capable agent.
Skills
Four portable, dual-harness skills live in skills/ — kb-ingest, kb-query,
kb-lint, kb-init. Install them once (user-wide or as a plugin); never copy
them into a KB instance, so they evolve centrally.
License
Apache-2.0. See LICENSE.
Metadata
Release files for llmkb 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| llmkb-0.1.0.tar.gz | 26.1 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| llmkb-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 46.6 kB
Release files / llmkb-0.1.0.tar.gz
| Download URL | llmkb-0.1.0.tar.gz |
|---|---|
| Size | 26.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
91b3cba47eb33bc5f3f80b3a0ce6321cd31fa0db0e0cc92fd6c2e0c4f209c767
|
|
BLAKE2b-256 checksum How to use checksums |
e7def882e4b3e7086838a7da247819c5bea8e1751bb1f3d2b8ad650d354d671e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 15, 2026.
Transparency logRelease files / llmkb-0.1.0-py3-none-any.whl
| Download URL | llmkb-0.1.0-py3-none-any.whl |
|---|---|
| Size | 20.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4cf889dc759990f340c37808175bef3506ad3dca445e4b0f22b65f0948f43f24
|
|
BLAKE2b-256 checksum How to use checksums |
6826b3d51b11ccfb9bb721e64fd6fe4fb1894da9d15e837701ab6629c042bcf5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 15, 2026.
Transparency log