llm-wiki

Ingest sources into an interlinked markdown wiki with schema and linting.

1|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/eddielueng/hermes-agent-zh --skill llm-wiki-eddielueng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: llm-wiki
Source: https://github.com/eddielueng/hermes-agent-zh/tree/main/skills/research/llm-wiki
Command: npx skills add https://github.com/eddielueng/hermes-agent-zh --skill llm-wiki-eddielueng

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

This Skill helps users turn scattered research inputs into a compounding, persistent knowledge base so future questions can be answered from an organized set of interlinked notes rather than re-reading sources.

Core Features & Use Cases

  • Compiling a knowledge base once, then keeping it current using an interlinked markdown wiki instead of per-query ad-hoc RAG.
  • Structured wiki architecture with layers for raw immutable sources, agent-owned pages, and a schema that enforces conventions.
  • Ingest, query, and lint workflows including orientation (SCHEMA/index/log), automatic cross-referencing, provenance marking for multi-source syntheses, and wiki consistency audits.

Quick Start

Use the llm-wiki skill to initialize a wiki at the configured WIKI_PATH by instructing the agent: “Create a new LLM research wiki for my domain, write the SCHEMA.md, index.md, and log.md, and then suggest the first sources I should ingest.”

Frequently Asked Questions about llm-wiki

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build a persistent markdown knowledge base from scattered research sources?

To build a persistent markdown knowledge base, you ingest raw sources into an immutable layer and synthesize them into interlinked wiki pages. This creates a compounding research repository with cross-references and provenance markers for later retrieval.

What is the best way to maintain an interlinked research wiki instead of using per-query RAG?

An interlinked research wiki replaces per-query RAG by compiling knowledge once into structured markdown pages. You maintain it through ingest, query, and lint workflows that enforce cross-references, tag taxonomy, and hash-based drift handling for raw sources.

How do I audit consistency and track provenance in a markdown wiki?

You audit consistency and track provenance in a markdown wiki by running linting workflows that check cross-references and tag taxonomy. Provenance markers are automatically applied during synthesis to track multi-source compilations.

Can I use a structured wiki architecture to answer questions from compiled research notes?

Yes, a structured wiki architecture lets you answer questions from compiled research notes by retrieving information from synthesized, interlinked markdown pages. It requires a persistent directory schema with SCHEMA.md, index.md, log.md, and raw/wiki layers.

How do I initialize a directory schema for an interlinked research wiki?

You initialize a directory schema for an interlinked research wiki by creating SCHEMA.md, index.md, and log.md files alongside raw and wiki layers. This schema enforces conventions for agent-owned pages, cross-references, and provenance tracking.

What are the limitations of using a markdown wiki for research knowledge management?

Limitations of using a markdown wiki for research include requiring a persistent directory schema and manual ingestion workflows. It is not designed for ad-hoc per-query retrieval but for compiling knowledge once into immutable raw material and synthesized pages.