ingest

Resolve filing targets and update frontmatter when ingesting external sources into wiki pages.

1|Updated Feb 18, 2026
One-click install
npx skills add https://github.com/bcbeidel/toolkit --skill ingest-bcbeidel
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ingest
Source: https://github.com/bcbeidel/toolkit/tree/main/plugins/wiki/skills/ingest
Command: npx skills add https://github.com/bcbeidel/toolkit --skill ingest-bcbeidel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ingest provides a structured way to bring external sources into wiki pages, preserving provenance and enabling context-aware documentation.

Core Features & Use Cases

  • Resolve target pages based on RESOLVER rules or user input, and create or update pages in append-only fashion.
  • Enforce frontmatter contracts (sources, created, updated, type, confidence) and support optional source summaries.
  • Coordinate pre-ingest steps (RESOLVER.md, filing table, vocabulary) to ensure consistent context.

Quick Start

Provide a source (URL, file path, or pasted text) and confirm the planned page updates.

Frequently Asked Questions about ingest

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

FAQPage Schema
How do I ingest external sources into wiki pages while preserving provenance?

You can ingest external sources into wiki pages by resolving filing targets and updating frontmatter, preserving provenance through tracked sources and append-only content changes. This ensures context-aware documentation for URLs, files, or pasted text.

What is frontmatter hygiene and why does it matter for knowledge management?

Frontmatter hygiene maintains metadata contracts for sources, created dates, updated dates, type, and confidence. It ensures your wiki pages have consistent, traceable provenance, which is critical for reliable knowledge management and context-aware documentation.

How do I bulk ingest URLs and files into a wiki with consistent structure?

You can bulk ingest URLs and files by providing the sources and confirming the planned page updates. The process resolves target pages based on filing rules, applies append-only content additions, and enforces frontmatter contracts before running a post-ingest linting step.

Can I use resolver rules to automatically file ingested content into specific wiki pages?

Yes, you can use RESOLVER rules to automatically determine filing targets for ingested content. The process coordinates pre-ingest steps like the RESOLVER file and filing table to ensure sources are consistently routed to the correct wiki pages.

Does the wiki ingestion process support append-only content updates?

Yes, the wiki ingestion process strictly enforces append-only content changes. This means existing page content is preserved and new external sources are added alongside it, ensuring historical context and provenance are never overwritten during the update.

What are the limitations of using automated wiki ingestion for content organization?

The automated wiki ingestion process requires pre-configured resolver rules, a filing table, and vocabulary to ensure consistent context. Without these pre-ingest coordination steps, the system cannot accurately resolve target pages or enforce the necessary frontmatter contracts.