llm-wiki

Build a persistent, incrementally updated wiki from ingested sources.

141|15|Updated Apr 13, 2026
One-click install
npx skills add https://github.com/selmakcby/knowledge-pipeline --skill llm-wiki-selmakcby
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: llm-wiki
Source: https://github.com/selmakcby/knowledge-pipeline/tree/main
Command: npx skills add https://github.com/selmakcby/knowledge-pipeline --skill llm-wiki-selmakcby

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Standard LLM retrieval-augmented generation (RAG) fails to build cumulative, persistent knowledge: every query re-discovers information from scratch, context windows fill up and compress away nuance, and manual wiki maintenance creates unsustainable overhead for teams and individuals.

Core Features & Use Cases

  • Three core operations: Ingest new sources into the wiki, query the wiki for answers with full source attribution, and run periodic health checks to catch conflicts, orphan pages, and stale claims.
  • Domain-agnostic design: Works for academic research, book note-taking, product development, team knowledge bases, personal development tracking, and competitive analysis.
  • Strict guardrails: Enforces immutable raw source storage, source-backed claims for all wiki content, conflict marking instead of deletion, and append-only logging to maintain long-term consistency.

Quick Start

Use the llm-wiki skill to set up a persistent Obsidian vault for your research project, then ingest your first source document to start building your cumulative, searchable knowledge base.

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 cumulative knowledge base from LLM chats instead of re-discovering information?

To build cumulative knowledge from LLM chats, you can use a persistent wiki that ingests sources and incrementally updates pages. This prevents context window compression and avoids re-discovering information from scratch on every query.

What is the best way to maintain long-term wiki consistency for team knowledge management?

The best way to maintain long-term wiki consistency is enforcing strict guardrails like immutable raw source storage, source-backed claims, and append-only logging. This ensures trustworthiness by marking conflicts instead of deleting them.

How do I set up an Obsidian vault for academic research note-taking with LLM automation?

To set up an Obsidian vault for academic research, use the llm-wiki skill to configure a persistent storage location, then ingest your first source document to start building your searchable, cumulative knowledge base automatically.

Does this knowledge management approach work for product development and competitive analysis?

Yes, this knowledge management approach works for product development and competitive analysis because it features a domain-agnostic design. It supports diverse use cases by querying a persistent wiki with full source attribution.

How do I catch conflicts and orphan pages in an automated knowledge base?

To catch conflicts and orphan pages in an automated knowledge base, run periodic health checks. These health checks identify stale claims, orphan pages, and conflicts to maintain long-term wiki consistency and trustworthiness.

Why does standard RAG fail at persistent knowledge retrieval compared to wiki automation?

Standard RAG fails at persistent knowledge retrieval because every query re-discovers information from scratch and context windows compress away nuance. Wiki automation solves this by building an incrementally updated, source-backed knowledge structure.