How do I install the Ingest Corpus skill?

Run npx skillmds@latest add egregore-labs/ingest-corpus in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Ingest Corpus skill do?

Turn a large folder of documents into a Connect-only knowledge base that answers questions with sources. Say 'build a knowledge base'. Not a few files (/ingest) or a meeting/Notion/Google source. It is listed under Research & Search on SkillMD.

Is Ingest Corpus safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Ingest Corpus?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Ingest Corpus free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Ingest Corpus?

egregore-labs (@egregore-labs) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Ingest Corpus by egregore-labs — Agent Skill

Name: Ingest Corpus
Author: egregore-labs

File contents

Egregore ingest-corpus Adapter

This is fallback coverage for a long-tail Egregore workflow that has not been ported to a hand-written Codex-native skill yet.

Use the project shell and filesystem directly. Do not invoke Claude Code commands. Translate interactive choices to structured Codex question tooling when it is available; otherwise render compact numbered choices with an Other: option and wait for the user.

Read .claude/skills/ingest-corpus/SKILL.md for the workflow details.
Run the referenced bin/ scripts directly from Codex.
Treat graph and publish steps as best-effort unless that workflow explicitly says they are required.
For every external notification, follow .claude/context/notification-consent.md: plan without sending, then show a separate exact Send / Edit / Cancel checkpoint. Never infer notification consent from the workflow request or a batch approval.
Keep local-mode behavior filesystem-first and avoid graph or notification calls when egregore.json declares "mode": "local".
Never call the deprecated egregore-handoff CLI for Egregore project handoffs.

Frequently asked questions

Ingest Corpus