ingest

Ingest local files, git histories, and web crawls into the gnosis-mcp knowledge base.

27|9|Updated Feb 15, 2026
One-click install
npx skills add https://github.com/nicholasglazer/gnosis-mcp --skill ingest-nicholasglazer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ingest
Source: https://github.com/nicholasglazer/gnosis-mcp/tree/main/skills/ingest
Command: npx skills add https://github.com/nicholasglazer/gnosis-mcp --skill ingest-nicholasglazer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ingests and indexes docs into the gnosis-mcp knowledge base.

Core Features & Use Cases

  • Ingest local files, git histories, and web crawls and build a searchable index.
  • Supports incremental updates and pruning of missing sources to keep the index accurate.
  • Optional embedding workflow for richer search capabilities when enabled.

Quick Start

Ingest the contents of the docs folder to populate and update the knowledge base.

Frequently Asked Questions about ingest

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

FAQPage Schema
How do I index local documentation files into a searchable knowledge base?

To index local documentation files, you ingest the contents of your docs folder to populate and update the knowledge base. This builds a searchable index directly from your local files.

Can I index git history and web crawl results alongside local files?

Yes, you can ingest git histories and web crawl results alongside local files. The ingestion process builds a searchable index combining all three source types into one knowledge base.

What is the best way to keep an indexed knowledge base accurate when sources change?

The best way to keep an indexed knowledge base accurate is using incremental updates and pruning of missing sources. This maintains index accuracy by removing outdated entries during reingest cycles.

Does the ingestion process support embedding workflows for richer search?

Yes, the ingestion process supports an optional embedding workflow for richer search capabilities. You can enable embeddings using the --embed flag during the ingestion lifecycle.

What flags are available to control the reingest lifecycle and index maintenance?

Available flags to control the reingest lifecycle include --force, --prune, --wipe, --embed, and --include-crawled. These single-entry point flags manage index updates and safe pruning options.

When should I use the prune or wipe options during documentation ingestion?

Use the --prune flag to safely remove missing sources during incremental updates, or use --wipe to clear the index entirely. These options maintain index accuracy when original documentation sources are deleted or moved.