llm-wiki

Distill knowledge into a persistent Obsidian wiki with three-layer architecture.

3.2k|320|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/Ar9av/obsidian-wiki --skill llm-wiki-ar9av
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: llm-wiki
Source: https://github.com/Ar9av/obsidian-wiki/tree/main/.skills/llm-wiki
Command: npx skills add https://github.com/Ar9av/obsidian-wiki --skill llm-wiki-ar9av

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Distill knowledge into a persistent, compounding Obsidian wiki to avoid re-deriving knowledge on every query and to provide a stable, navigable knowledge base.

Core Features & Use Cases

  • Guidance on building and maintaining a three-layer Wiki: raw sources, wiki, and schema.
  • Instructions for establishing provenance, wikilinks, and Obsidian-compatible structure across projects and categories.
  • Real-world scenarios include setting up a new knowledge base, organizing distilled content, and governing knowledge maintenance.

Quick Start

Instruct the agent to initialize the LLM Wiki schema and connect to your Obsidian vault.

Frequently Asked Questions about llm-wiki

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

FAQPage Schema
How do I create a persistent knowledge base in Obsidian to stop re-deriving the same information?

A three-layer wiki architecture organizes knowledge into raw sources, a distilled wiki, and a schema. This structure separates original inputs from refined insights and governs consistent metadata, enabling stable navigation and preventing knowledge re-derivation in your Obsidian vault.

How do I structure distilled knowledge in Obsidian using wikilinks and frontmatter?

You structure distilled knowledge by enforcing frontmatter-based metadata, strong wikilinks, and provenance markers. This approach supports consistent ingestion and maintenance workflows, ensuring your Obsidian wiki remains navigable and effectively organized across projects and categories.

What is the best way to set up a knowledge management workflow that tracks provenance in Obsidian?

The best way to track provenance is establishing a three-layer architecture with provenance markers and templates. This guides users through a knowledge-management strategy that records the origins of raw sources and maintains governance over the distilled wiki content.

Does this wiki distillation approach work for organizing raw sources and schemas across multiple projects?

Yes, the wiki distillation approach works across multiple projects by establishing an Obsidian-compatible structure. It organizes distilled content and raw sources using a schema layer, ensuring consistent ingestion and maintenance workflows regardless of project scale or category.

When should I use a schema layer instead of just storing raw markdown sources in Obsidian?

You should use a schema layer when you need to govern knowledge maintenance and ensure consistent metadata across your Obsidian vault. Adding a schema above raw markdown sources provides structural templates that prevent disorganized ingestion and maintain stable, navigable distilled knowledge.