Build an Interlinked Markdown Knowledge Base with Hermes

The bundled LLM Wiki skill describes a filesystem-first knowledge base with three concerns kept separate: immutable raw sources, synthesized entity or concept pages, and an operating layer made of SCHEMA.md, index.md, and an append-only log. The design favors resumability and provenance over a pile of disconnected notes.

Official skill reference: LLM Wiki

Resume before adding

At the start of every session, read the schema, index, and recent log. Those files define naming, frontmatter, tags, page thresholds, and recent changes. Search the existing wiki before creating a new page so aliases and overlapping concepts remain consolidated.

Ingest source material into raw/ without silently rewriting it. Store source URL, ingestion date, and a content hash. Synthesize durable pages only when the material crosses the wiki's quality threshold, and connect pages with meaningful [[wikilinks]]. For multi-source synthesis, place provenance markers near the claims they support.

Knowledge-base checklist

Set and verify the exact wiki root.
Read SCHEMA.md, index.md, and recent log.md entries.
Hash and preserve raw source material.
Reuse the established frontmatter and tag taxonomy.
Add at least two useful outbound links and update related pages.
Update the index and append a log entry in the same change.
Run lint checks for broken links, orphans, and stale metadata.

Common pitfalls

Writing synthesis directly into raw sources. That destroys provenance.
Creating a page for every mention. Thin pages increase fragmentation without adding knowledge.
Skipping the resume files. Conventions drift between sessions.
Letting the index become stale. Search alone does not replace a curated content map.
Syncing private material to an unintended service. Review the vault and sync boundary before enabling Obsidian or another remote layer.

Verification

Run the wiki linter, then inspect broken links, pages with no inbound links, duplicated titles, missing frontmatter, and sources whose hash changed. Open the updated index and follow links to the new or changed pages. A good verification pass proves both retrieval and provenance: the synthesized claim is discoverable, and its raw source remains traceable.