wiki-ingest

Ingest Markdown, text, PDFs, web clippings, and images into an Obsidian wiki.

Updated Apr 18, 2026
One-click install
npx skills add https://github.com/ChrisWiles/wiles-wiki --skill wiki-ingest-chriswiles
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wiki-ingest
Source: https://github.com/ChrisWiles/wiles-wiki/tree/main/.skills/wiki-ingest
Command: npx skills add https://github.com/ChrisWiles/wiles-wiki --skill wiki-ingest-chriswiles

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

The wiki-ingest skill solves the challenge of manually creating and maintaining interconnected wiki pages. It automates the process of extracting knowledge from various sources and integrating it into an Obsidian wiki.

Core Features & Use Cases

  • Knowledge Distillation: Automates the process of converting documents into interconnected wiki pages.
  • Multi-format Support: Handles various formats such as Markdown, text, PDFs, web clippings, and images.
  • QMD Integration: Uses QuickMD to identify related papers and avoid duplicate pages.
  • Provenance Tracking: Provides clear attribution for extracted claims to maintain content integrity.

Quick Start

Run the skill with the command 'wiki-ingest <path_to_document>'

Frequently Asked Questions about wiki-ingest

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

FAQPage Schema
How do I automate document ingestion into an Obsidian wiki?

Automating document ingestion into an Obsidian wiki involves processing formats like Markdown, PDFs, and text to distill knowledge into interconnected pages. This skill handles multi-format extraction and provenance tracking automatically.

Can I extract knowledge from PDFs and web clippings for Obsidian?

Yes, you can extract knowledge from PDFs and web clippings for Obsidian. The ingestion process supports multiple formats including Markdown, text, PDFs, web clippings, and images to build interconnected wiki pages.

How does provenance tracking work for extracted wiki claims?

Provenance tracking for extracted wiki claims works by providing clear attribution for knowledge distilled from source documents. This maintains content integrity by linking extracted information back to its original input.

What is the best way to avoid duplicate pages when creating an Obsidian wiki?

The best way to avoid duplicate pages when creating an Obsidian wiki is using QuickMD integration. It identifies related papers during the document ingestion process to prevent redundant page creation.

Does wiki-ingest require QuickMD to process documents?

wiki-ingest does not strictly require QuickMD to process documents, but the integration is used to identify related papers and avoid duplicate pages. Standard ingestion handles Markdown, text, PDFs, and images independently.

What are the limitations of automating information architecture with this approach?

Limitations of automating information architecture depend on source document quality and format complexity. While it processes formats like PDFs and web clippings, highly unstructured data may require manual review to ensure accurate wiki interconnection.