ingest

Route incoming content to ingestion sub-skills by detecting input type.

Updated May 16, 2026
One-click install
npx skills add https://github.com/Morris-UTRUST/GBrain-knowledge --skill ingest-morris-utrust
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ingest
Source: https://github.com/Morris-UTRUST/GBrain-knowledge/tree/main/skills/ingest
Command: npx skills add https://github.com/Morris-UTRUST/GBrain-knowledge --skill ingest-morris-utrust

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill acts as a router for content ingestion, directing each input to the most appropriate specialized ingestion workflow. It ensures that raw sources are preserved, entities are detected and linked, and brain pages for people, companies, concepts, meetings, and sources are created or updated with proper provenance.

Core Features & Use Cases

  • Input type detection: automatically classifies meetings, articles, emails, and other content, routing them to the correct ingestion sub-skill.
  • Entity creation & linking: creates page entries for mentioned people and organizations, with cross-links and iron-law back-links.
  • Timeline & provenance: adds timeline entries and preserves raw sources for provenance with structured citations.
  • Quality & filing rules: enforces notability gates and rewrites state with current best understanding.

Quick Start

Provide a source item (meeting notes, article, or message) and let the router delegate to the appropriate ingestion workflow.

Frequently Asked Questions about ingest

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

FAQPage Schema
How do I automatically route meeting notes and articles to different ingestion workflows?

Content routing automatically classifies input types like meetings, articles, and emails, delegating each to the correct ingestion sub-skill for specialized processing and structured filing.

How does entity detection work when ingesting content into my knowledge base?

Entity detection during content ingestion creates page entries for mentioned people and organizations, establishing cross-links and iron-law back-links to maintain a connected knowledge graph.

What's the best way to preserve provenance and raw sources when capturing meeting notes?

Preserving provenance during content ingestion captures raw sources directly and applies structured citations, ensuring full traceability when updating timelines and brain pages.

How do I enforce notability gates and filing rules before creating new pages for detected entities?

Notability gates and filing rules evaluate detected entities during the ingestion routing process, rewriting state with current best understanding to prevent low-value page creation.

Can I use a single ingestion router for emails, articles, and meeting notes simultaneously?

A single ingestion router handles emails, articles, and meeting notes simultaneously by detecting each input type and delegating tasks to appropriate specialized sub-skills across brain storage.

Why do my back-links break when ingesting content from multiple different source formats?

Broken back-links during content ingestion occur when routing lacks robust provenance capture; this skill enforces iron-law back-linking across all detected entities to maintain structural integrity.