corpus-ingest

Route URLs, files, and pasted articles into a Lorekit knowledge base.

5|1|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/GYF0311/lorekit --skill corpus-ingest
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: corpus-ingest
Source: https://github.com/GYF0311/lorekit/tree/main/skills/corpus-ingest
Command: npx skills add https://github.com/GYF0311/lorekit --skill corpus-ingest

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

corpus-ingest solves the problem of turning scattered external inputs (URLs, files, pasted articles, and PDFs) into durable, cross-linked knowledge inside a central Lorekit corpus instead of leaving them as unstructured one-off notes.

Core Features & Use Cases

  • Centralized ingest routing: Accepts user-provided sources and delegates the actual filing and wiki compilation behavior to the corpus-local rules.
  • Controlled archive + wiki compilation: Fetches URL content via the configured lorekit binary, archives sources into the corpus raw layer, and compiles them into the knowledge layer with backlinks and ingest state tracking.
  • Safety-first handling: Preserves fetched slugs when rules allow, prevents deletion, avoids bypassing duplicate/in-progress states, and stops if the corpus cannot be written.

Quick Start

Tell your AI: ingest this URL into your default Lorekit corpus using corpus-ingest.

Frequently Asked Questions about corpus-ingest

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

FAQPage Schema
How do I ingest URLs and articles into a centralized knowledge base?

To ingest URLs and articles into a centralized knowledge base, you route external source inputs into a central Lorekit corpus where they are preserved immutably and compiled into cross-linked wiki pages.

What is the best way to archive external documents while preserving the original source material?

Archiving external documents while preserving source material is best handled by routing inputs into a corpus raw layer, enforcing safety constraints that fetch content immutably and prevent deletion of the original sources.

Can I compile pasted articles and PDFs into cross-linked wiki pages automatically?

Yes, you can compile pasted articles and PDFs into cross-linked wiki pages by running the wiki-ingest process, which applies corpus-specific filing rules to generate the structured knowledge layer.

Does corpus ingestion require reading specific configuration and filing rules before fetching?

Yes, document ingestion requires reading global-corpus configuration and corpus-local AGENTS or CLAUDE filing rules before fetching URL content to ensure sources are compiled correctly under specific constraints.

Why does the wiki-ingest process stop when the corpus cannot be written?

The wiki-ingest process stops when the corpus cannot be written to enforce safety constraints, preventing the bypassing of duplicate or in-progress ingest states and protecting the existing knowledge base.

What happens if I try to ingest a duplicate URL that is already in progress?

When ingesting a duplicate URL already in progress, the process avoids bypassing existing ingest states, stopping safely to preserve the current archival workflow and prevent duplicate source material compilation.