llm-wiki

Maintain a persistent Obsidian wiki with frontmatter metadata and cross-linking.

Updated Apr 27, 2014
One-click install
npx skills add https://github.com/Nirajkashyap/nirajkashyap.github.io --skill llm-wiki-nirajkashyap
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: llm-wiki
Source: https://github.com/Nirajkashyap/nirajkashyap.github.io/tree/main/.agents/skills/llm-wiki
Command: npx skills add https://github.com/Nirajkashyap/nirajkashyap.github.io --skill llm-wiki-nirajkashyap

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Builds and sustains a cohesive, AI-assisted knowledge base that persists knowledge over time, reducing duplication and rework.

Core Features & Use Cases

  • Persistent compilation: distills sources into a navigable wiki that remains current rather than re-derived on every query.
  • Three-layer architecture governance: defines Layer 1 raw sources, Layer 2 wiki, and Layer 3 schema to standardize structure and workflows.
  • Ontology and structure guidance: prescribes categories, projects, and cross-link conventions to support scalable knowledge management across domains.
  • Use cases include: setting up a new knowledge base, organizing distilled knowledge, and discussing knowledge-management strategies and wiki structure decisions.

Quick Start

Initialize a new Obsidian vault following the LLM Wiki three-layer pattern and create first pages with proper frontmatter and wikilinks.

Frequently Asked Questions about llm-wiki

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

FAQPage Schema
What is the LLM Wiki pattern for knowledge distillation?

The LLM Wiki pattern is a knowledge-management architecture that distills raw sources into a persistent, navigable Obsidian wiki. It standardizes information architecture using a three-layer system of raw sources, wiki pages, and schema to reduce knowledge duplication and rework over time.

How do I organize distilled knowledge in Obsidian using a three-layer architecture?

You organize distilled knowledge by separating it into Layer 1 raw sources, Layer 2 wiki, and Layer 3 schema. This three-layer architecture governs structure and workflows, applying frontmatter-driven metadata, cross-linking, and schema-based governance to maintain a cohesive knowledge base.

Can I use this Skill to set up a new Obsidian vault for knowledge management?

Yes, you can initialize a new Obsidian vault following the LLM Wiki three-layer pattern. The Skill guides you to create your first pages with proper frontmatter and wikilinks, prescribing categories, projects, and cross-link conventions to support scalable knowledge management across domains.

What is the best way to maintain a persistent, compiled knowledge base instead of re-deriving answers?

The best way to maintain a persistent knowledge base is to compile and distill sources into an Obsidian wiki that remains current. By applying schema-based governance and frontmatter-driven metadata, the wiki persists knowledge over time rather than re-deriving information on every query.

How does frontmatter-driven metadata and cross-linking support wiki structure decisions?

Frontmatter-driven metadata and cross-linking support wiki structure decisions by enforcing schema-based governance across pages. These conventions standardize categories, projects, and cross-links, ensuring the knowledge base remains navigable and scalable across different domains.

When should I not use a three-layer wiki architecture for information management?

You should avoid a three-layer wiki architecture when your knowledge management needs are temporary or when your workflow does not benefit from persistent compilation. If your tasks require re-deriving information on every query rather than maintaining a long-term, navigable Obsidian wiki, this structured approach adds unnecessary overhead.