agentos.guide › blog
The Hermes LLM wiki is the bundled llm-wiki skill in Hermes Agent, which makes the agent build and maintain a knowledge base as a folder of linked markdown pages.
It is based on Andrej Karpathy's LLM Wiki pattern, and Nous Research ships it with Hermes, installed by default.
You set WIKI_PATH to a folder, type /llm-wiki, and Hermes writes the schema, index and log, then ingests, queries and lints the wiki for you.
This page is the quick start, plus how it fits an Agent OS that runs several agents side by side.
This is the shortest path from a fresh Hermes install to a working wiki.
| Step | What you do | Command or file |
|---|---|---|
| 1 | Update Hermes so the bundled skills are synced. | hermes update |
| 2 | Choose the folder your wiki lives in. | WIKI_PATH in your Hermes .env |
| 3 | Start the wiki from chat. | /llm-wiki |
| 4 | Tell Hermes what the wiki covers. | SCHEMA.md, index.md, log.md |
| 5 | Add a source and let it build pages. | A URL, a PDF or pasted text |
| 6 | Ask questions and lint it weekly. | Answers cite [[wikilinks]] |
Every step comes from the official Llm Wiki skill page and the Hermes skills docs.
If WIKI_PATH isn't set, the skill falls back to ./wiki, using the line WIKI="${WIKI_PATH:-$HOME/wiki}".
The docs say every installed skill becomes a slash command, so /llm-wiki works in the CLI and on any messaging platform Hermes is connected to.
You can also preload it for a whole session, because hermes chat takes -s or --skills to preload skills.
Hermes Agent is the free, open-source AI agent from Nous Research.
The Hermes LLM wiki is its bundled llm-wiki skill, which the docs describe as "Karpathy's LLM Wiki: build/query interlinked markdown KB."
The docs list it as installed by default, version 2.1.0, MIT-licensed, for Linux, macOS and Windows, with obsidian and arxiv as related skills.
When I checked my own Hermes install, which runs v0.22.1, the skill was already in my skills folder without me installing anything.
The skill costs nothing, and the only running cost is the model you connect to Hermes.
Andrej Karpathy published the pattern as a GitHub gist called LLM Wiki in April 2026.
He wrote it as an idea file to paste into an agent such as Codex, Claude Code or OpenCode, and he kept it deliberately abstract.
His argument is that RAG-style tools rediscover knowledge on every question, while an agent-maintained wiki compiles it once and keeps it current.
He splits the work cleanly, with the human curating sources and asking questions, and then he adds: "The LLM's job is everything else."
The git history of the Hermes repo shows Nous added the skill two days after the gist went up.
In my video below I walk through the idea, the three layers and the three operations.
On a new wiki, the skill tells Hermes to create this structure, ask you what the wiki covers and write the three starter files.
wiki/
├── SCHEMA.md # Conventions, structure rules, domain config
├── index.md # Sectioned content catalog with one-line summaries
├── log.md # Chronological action log (append-only, rotated yearly)
├── raw/ # Layer 1: Immutable source material
│ ├── articles/ # Web articles, clippings
│ ├── papers/ # PDFs, arxiv papers
│ ├── transcripts/ # Meeting notes, interviews
│ └── assets/ # Images, diagrams referenced by sources
├── entities/ # Layer 2: Entity pages (people, orgs, products, models)
├── concepts/ # Layer 2: Concept/topic pages
├── comparisons/ # Layer 2: Side-by-side analyses
└── queries/ # Layer 2: Filed query results worth keeping
The raw/ layer holds your sources, and the agent reads them but never edits them.
The pages in entities/, concepts/, comparisons/ and queries/ are written and maintained by the agent.
SCHEMA.md is the rulebook for filenames, frontmatter and the 10 to 20 tags the wiki is allowed to use.
At the start of every session the agent reads SCHEMA.md, index.md and the last 20 to 30 log entries before it does anything.
🔥 Want the exact Hermes Agent setup I run inside my Agent OS?
Inside the AI Profit Boardroom you get the installable Agent OS, step-by-step video tutorials, four coaching calls a week and 3,400+ members building real automations.
The skill gives Hermes a fixed order of work for a brand-new wiki, so you know exactly what to expect.
WIKI_PATH, or asks you, with ~/wiki as the default.SCHEMA.md customised to your domain, an index.md with section headers and a log.md with a creation entry.My advice is to answer the domain question narrowly, because a tight domain gives you a tight tag taxonomy and cleaner pages.
The schema's page thresholds mean a page only gets created when something appears in two or more sources or is central to one.
That rule stops the wiki filling up with pages about passing mentions.
The skill ends with a pitfalls list, and these are the rules worth remembering.
raw/, because sources are immutable and corrections go into wiki pages.SCHEMA.md, and new tags are added there first._archive/ folder.| Operation | What you say | What Hermes does |
|---|---|---|
| Ingest | You ask it to add a URL, PDF or pasted text to the wiki. | It saves the source under raw/, updates 5 to 15 pages, the index and the log, and reports every change. |
| Query | You ask a question about the wiki's subject. | It reads the index and the relevant pages, answers with citations and files substantial answers back. |
| Lint | You ask it to lint, audit or health-check the wiki. | It runs 13 checks, from broken links to source drift, and reports them by severity. |
Each raw source gets a sha256 hash in its frontmatter, so a re-ingest skips unchanged sources and flags drift.
Pages built from three or more sources carry provenance markers such as ^[raw/articles/source-file.md], so you can trace each claim.
The optional confidence and contested fields let lint surface weak claims before they harden into accepted fact.
Lint also flags pages that are more than 90 days stale, pages over 200 lines and a log that has passed 500 entries.
🔥 Want the exact Hermes Agent setup I run inside my Agent OS?
Inside the AI Profit Boardroom you get the installable Agent OS, step-by-step video tutorials, four coaching calls a week and 3,400+ members building real automations.
My Agent OS runs several agents side by side, and the hard part is always shared knowledge rather than raw intelligence.
| Agent OS job | How the Hermes LLM wiki helps |
|---|---|
| Shared research memory | Every agent that can read files can read the same markdown wiki, because there is no database in the way. |
| Overnight research | Hermes cron jobs can attach skills with --skill, and the skill skips the takeaways chat in cron contexts. |
| A wiki per client or project | Each Hermes profile has its own Hermes home, so each profile's .env can set its own WIKI_PATH. |
| A visual layer | The folder opens as an Obsidian vault, with Graph View showing how pages connect. |
| Trust and review | Ingests that would touch 10 or more existing pages wait for your approval. |
The cron docs show the multi-skill pattern as hermes cron create "every 1h" "Use both skills and combine the result" --skill blogwatcher --skill maps, and you swap in the skills you need.
A natural pairing is the bundled competitor-news-monitor skill, which the catalog says watches named companies for material news with cited digests.
If you want the other direction, where other agents query Hermes, my guide to running Hermes as an MCP server covers that.
The docs say the wiki folder works as an Obsidian vault out of the box, with clickable wikilinks, Graph View and Dataview queries.
They recommend setting Obsidian's attachment folder to raw/assets/.
If you use the bundled obsidian skill too, set OBSIDIAN_VAULT_PATH to the same folder as your wiki.
On a server with no display, the skill documents npm install -g obsidian-headless, which needs Node.js 22 or newer and an Obsidian Sync subscription.
After ob login, ob sync-create-remote --name "LLM Wiki" and ob sync-setup --vault "<vault-id>" inside the wiki folder, ob sync --continuous keeps it syncing.
I built a vault-based second brain for Hermes in my Hermes second brain guide, and the Obsidian habits carry straight over.
| Problem | Why it happens | Fix |
|---|---|---|
/llm-wiki isn't recognised | The profile opted out of bundled skills. | Run hermes skills opt-in --sync to re-seed them. |
| The skill stopped updating | You edited it, so Hermes treats it as user-modified. | Run hermes skills reset llm-wiki, or add --restore for the original. |
The wiki landed in ~/wiki | WIKI_PATH isn't set. | Set WIKI_PATH in your Hermes .env file. |
| Duplicate pages appear | The agent skipped orientation. | Ask it to read SCHEMA.md, index.md and the recent log first. |
| An ingest pauses | It would touch 10 or more existing pages. | Approve the scope, and it carries on. |
The docs also mention llm-wiki-compiler, a Node.js CLI for batch-compiling a source folder into a wiki.
They say it owns page generation and is tuned for small corpora, so the skill is the better fit for a wiki you keep curating.
The skill is a set of instructions, so the quality of every page depends on the model you connect.
Karpathy says an index file works well at around 100 sources and hundreds of pages, and the skill adds file search past 100 pages.
Big ingests wait for approval, which is safe but slows fully unattended runs.
Your sources sit on disk as plain files, so keep the folder somewhere you control.
If you want to talk through where an agent knowledge base fits an SEO business, you can book a free SEO strategy session with my team.
The Hermes LLM wiki is the bundled llm-wiki skill in Hermes Agent. It builds and maintains a persistent knowledge base of linked markdown files, based on Andrej Karpathy's LLM Wiki pattern, and it is installed by default.
Andrej Karpathy published it as an idea file in a GitHub gist in April 2026. Nous Research turned it into the llm-wiki skill that ships with Hermes Agent.
Set WIKI_PATH in the .env file in your Hermes home, or leave it unset to use ~/wiki, then type /llm-wiki and tell Hermes what the wiki covers.
Yes. Hermes cron jobs can attach skills with --skill, and the llm-wiki skill skips the discuss-takeaways step in automated or cron contexts.
No. The docs say it is just a directory of markdown files, so you can open it in Obsidian, VS Code or any editor.
Run hermes skills reset llm-wiki --restore, which deletes your local copy and re-copies the current bundled version.
Set the folder, run the slash command, feed it one good source at a time and lint it weekly, and your Agent OS gets a research memory that compounds.
If you want a second opinion on how agents should fit your SEO business, you can book a free SEO strategy session with my team.
If you want the whole Agent OS with Hermes already wired in, it lives inside the AI Profit Boardroom, with 3,400+ members and four coaching calls a week.
That is the fastest way to get real value from the Hermes LLM wiki.
About Julian
I'm Julian Goldie, an AI entrepreneur, SEO expert and the founder of the AI Profit Boardroom, which has 3,400+ members.
I help business owners scale with AI agents, automation and SEO.
My YouTube channel has 400,000+ subscribers, and I run Goldie Agency, a seven-figure SEO agency.
→ Hermes /learn: The Book Brain Engine
The installable system behind every guide on this site — dashboard, agents, memory and pipelines — updated as new tools land, with 3,400+ members and four coaching calls a week.
Join the AI Profit Boardroom →📺 Video notes + links to the tools 👉
🎥 Learn how I make these videos 👉