wiki-ingest

Ingest articles, PDFs, videos, and transcripts into interlinked wiki pages with provenance.

133|19|Updated May 4, 2026
One-click install
npx skills add https://github.com/Mark393295827/third-brain-v5-skills --skill wiki-ingest-mark393295827
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wiki-ingest
Source: https://github.com/Mark393295827/third-brain-v5-skills/tree/main/skills/wiki-ingest
Command: npx skills add https://github.com/Mark393295827/third-brain-v5-skills --skill wiki-ingest-mark393295827

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It turns raw sources into durable, interlinked knowledge pages so research, notes, and evidence do not get lost in chat history.

Core Features & Use Cases

  • Source capture: Creates immutable source notes with provenance, risk labels, and structured metadata.
  • Knowledge expansion: Builds linked entity pages, concept pages, navigation updates, and timeline entries from a source.
  • Governed promotion: Supports supervised conversion of insights into skills, SOPs, schemas, behaviors, or review queues when warranted.
  • Use case: Use it when you want an article, PDF, transcript, or note transformed into a persistent wiki with verification and traceability.

Quick Start

Tell the agent to use wiki-ingest on your source and create source notes, concept pages, entity pages, navigation updates, and a verification summary.

Frequently Asked Questions about wiki-ingest

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

FAQPage Schema
How do I turn PDF articles and transcripts into a linked knowledge wiki?

You can ingest articles, PDFs, and transcripts to automatically generate immutable source notes, concept pages, and entity pages. This process creates a persistent, interlinked knowledge wiki with provenance tracking and verification summaries.

What is provenance tracking and why do I need it for knowledge management?

Provenance tracking records the origin and risk labels of ingested sources to prevent research loss. It requires immutable source capture and verification summaries, ensuring your knowledge wiki maintains traceability and evidence integrity across all notes.

How do I organize research notes into entity pages and concept pages?

Organize research notes by ingesting source material to automatically build linked entity pages and concept pages. This knowledge expansion requires at least two wikilinks per page and includes navigation updates to maintain a persistent, interlinked wiki structure.

Can I promote verified wiki notes into SOPs and governance queues?

Yes, you can use supervised promotion to convert verified wiki insights into SOPs, schemas, skills, or governance queues. This governed promotion happens after source capture and knowledge expansion, ensuring only warranted insights are promoted.

Does wiki-ingest work with YAML-frontmatter and what linting does it require?

Wiki-ingest works with YAML-frontmatter wiki pages and requires targeted linting for broken references and missing metadata. This linting ensures source capture integrity and validates that pages meet the minimum requirement of two wikilinks per page.

What are the limitations of using automated source capture for knowledge management?

Automated source capture requires immutable provenance and at least two wikilinks per page, which limits rapid informal note-taking. Additionally, supervised promotion into SOPs or governance queues requires manual oversight, preventing fully automated knowledge pipeline execution.