llm-wiki

Distill and organize knowledge into a persistent three-layer wiki.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Michael1Peng/watson --skill llm-wiki-michael1peng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: llm-wiki
Source: https://github.com/Michael1Peng/watson/tree/main/.agents/skills/llm-wiki
Command: npx skills add https://github.com/Michael1Peng/watson --skill llm-wiki-michael1peng

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

The wiki is a persistent, compounding knowledge base. It is not a chatbot — it is a compiled artifact where knowledge is distilled once and kept current, not re-derived on every query.

Core Features & Use Cases

  • Three-layer architecture: Raw Sources (immutable), The Wiki (LLM-maintained), and The Schema (rules and workflows) to keep knowledge organized and up-to-date.
  • Cross-linking, provenance, and templated pages enable navigation, traceability, and incremental improvement over time.
  • Use cases include understanding the wiki pattern, setting up a new knowledge base, or guiding knowledge-management strategy.

Quick Start

Define a three-layer wiki outline and initialize a new knowledge base using raw sources, a maintained wiki, and a defined schema.

Frequently Asked Questions about llm-wiki

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

FAQPage Schema
How do I structure a persistent knowledge base instead of re-deriving answers in chat?

Structure a persistent knowledge base using a three-layer architecture: immutable raw sources, an LLM-maintained wiki, and a defined schema. This compiles knowledge into an artifact kept current over time rather than re-derived on every query.

What is the three-layer pattern for knowledge management?

The three-layer pattern for knowledge management separates raw sources, a maintained wiki, and a schema of rules. This architecture organizes information to enable navigation, traceability, and incremental improvement across your vault.

How do I set up a new Obsidian vault for LLM knowledge distillation?

Set up a new Obsidian vault by defining a three-layer wiki outline and initializing raw sources, a maintained wiki, and a schema. Enforce frontmatter conventions, page templates, and wikilinks for environment-driven configurations.

Does this wiki pattern enforce provenance and page templates in Obsidian?

Yes, the wiki pattern enforces frontmatter conventions, page templates, wikilinks, and provenance. These mechanisms enable navigation, traceability, and incremental improvement within vault-based knowledge systems.

Can I use wikilinks to maintain traceability in an LLM-maintained knowledge base?

Yes, you can use wikilinks to maintain traceability in an LLM-maintained knowledge base. Cross-linking and provenance tracking enable navigation and incremental improvement across templated pages within the vault.

When should I not use a compiled wiki artifact for knowledge management?

Avoid using a compiled wiki artifact when you need conversational interactions rather than a persistent knowledge base. This approach is designed for compiling knowledge once and keeping it current, not for functioning as a chatbot.