llm-wiki

Distill raw documents into an Obsidian wiki with frontmatter metadata and wikilinks.

6|2|Updated May 11, 2026
One-click install
npx skills add https://github.com/pax-k/war-gov-uap-wiki --skill llm-wiki-pax-k
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: llm-wiki
Source: https://github.com/pax-k/war-gov-uap-wiki/tree/main/.skills/llm-wiki
Command: npx skills add https://github.com/pax-k/war-gov-uap-wiki --skill llm-wiki-pax-k

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

The LLM Wiki pattern provides a structured approach to building and maintaining a persistent, compiled knowledge base, so knowledge is created once and kept current, not re-derived on every query.

Core Features & Use Cases

  • Three-layer architecture: Layer 1 Raw Sources, Layer 2 The Wiki, Layer 3 The Schema, with clear provenance and cross-linking.
  • Obsidian-backed knowledge graph: Pages include YAML frontmatter, Obsidian wikilinks, and lifecycle metadata to enable reliable navigation and governance.
  • Governance and scalability: A configurable schema that guides templates, categories, and workflows for growing, cross-project knowledge bases.

Quick Start

Set up a new wiki using the LLM Wiki pattern and begin distilling raw sources into an Obsidian vault following the three-layer architecture.

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 knowledge wiki from raw documents without re-deriving context on every query?

To build a persistent knowledge wiki, distill raw documents into a compiled Obsidian vault using a three-layer architecture that separates raw sources, the wiki, and the schema, ensuring knowledge is created once and kept current.

What is the best way to maintain provenance and source tracking in an Obsidian knowledge graph?

Maintaining provenance in an Obsidian knowledge graph requires frontmatter-based metadata and Obsidian wikilinks to track source origins and lifecycle governance across a structured three-layer architecture.

How do I enforce schema and templates when distilling research notes into an Obsidian vault?

Enforce schema in an Obsidian vault by applying a configurable schema layer that guides templates, categories, and workflows for ingesting and curating raw sources into citation-grounded wiki pages.

Can I use this knowledge distillation approach for organizational wikis that require lifecycle governance?

Yes, this knowledge distillation approach applies to organizational wikis by enforcing frontmatter-based metadata and lifecycle governance to manage growing, cross-project knowledge bases with clear provenance.

Does the three-layer wiki architecture require Obsidian wikilinks and YAML frontmatter?

Yes, the three-layer wiki architecture relies on Obsidian wikilinks and YAML frontmatter to enable reliable navigation, schema enforcement, and governance across raw sources, the wiki, and the schema layers.