ingest

Ingest sources from URLs, workspace paths, or attachments into a vault.

9|1|Updated Mar 14, 2026

Search Tags:#workspace #vault #knowledge-management #ingest #web_fetch

Ready to run

npx skills add https://github.com/lmorchard/decafclaw --skill ingest-lmorchard

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ingest
Source: https://github.com/lmorchard/decafclaw/tree/main/src/decafclaw/skills/ingest
Command: npx skills add https://github.com/lmorchard/decafclaw --skill ingest-lmorchard

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ingest a source into the vault from a URL, workspace path, or attachment.

Core Features & Use Cases

Ingest from multiple source types (URL, workspace file, or attachments) and automatically create or update a main page with linked context.
Resolve conflicts and select the most relevant attachment when multiple exist, ensuring robust handling of edge cases.
Extend vault content with cross-links to related pages and keep provenance via a Sources section for traceability.

Quick Start

Provide a source (URL, workspace path, or attachment) to ingest and automatically create a primary vault page with related updates.

Frequently Asked Questions about ingest

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

FAQPage Schema

How do I ingest content from a URL into my knowledge vault?▼

To ingest content from a URL into your knowledge vault, provide the source URL to automatically create a primary vault page and generate cross-linked updates to related pages with provenance tracking.

Can I import workspace files and attachments into a knowledge management vault?▼

Yes, you can ingest workspace files and attachments into a knowledge management vault. The system routes by source type, resolves conflicts when multiple attachments exist, and writes the content with full provenance tracking.

What is the best way to organize ingested web content with cross-links in a vault?▼

The best way to organize ingested web content is to use a system that creates a primary vault page and automatically extends the vault with cross-links to related pages, ensuring all information is contextually connected.

How does provenance tracking work when importing attachments to a knowledge base?▼

Provenance tracking when importing attachments works by recording the source in a dedicated Sources section, ensuring traceability for every primary vault page created from a URL, workspace path, or attachment.

What happens if multiple attachments exist when ingesting a source into a vault?▼

When multiple attachments exist during source ingestion, the system automatically resolves conflicts and selects the most relevant attachment to ensure robust handling of edge cases while writing to the vault.