Verified:GitHub

kb-ingest

3|Updated Apr 3, 2026

Search Tags:#automation #workflow #obsidian #manifest #knowledge-base #ingest #raw-sources

Ready to run

npx skills add https://github.com/bahayonghang/obsidian-notes-karpathy --skill kb-ingest-bahayonghang

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: kb-ingest
Source: https://github.com/bahayonghang/obsidian-notes-karpathy/tree/main/skills/kb-ingest
Command: npx skills add https://github.com/bahayonghang/obsidian-notes-karpathy --skill kb-ingest-bahayonghang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

In Karpathy's LLM Wiki pattern, ingest is the moment raw evidence becomes visible to the system. A well-maintained manifest means compile can trust what it sees, deferred sources stay explicit instead of silently lost, and the user always knows what the knowledge base has ingested.

Core Features & Use Cases

Register new or changed sources into raw/_manifest.yaml to keep the manifest current and auditable.
Detect deltas between the filesystem and the manifest, present them for confirmation, and synchronize changes to the manifest.
Tie ingestion state to downstream processes (compile, review, and logging) to ensure provenance and traceability.

Quick Start

Scan the raw/ directory for sources and run ingest sync to update raw/_manifest.yaml.

Frequently Asked Questions about kb-ingest

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

FAQPage Schema

How do I normalize raw sources for an Obsidian knowledge base manifest?▼

To normalize raw sources, scan the raw/ directory to detect new or changed files and run ingest sync to register deltas into raw/_manifest.yaml, ensuring your knowledge base manifest remains current and auditable.

What is the best way to track deferred or duplicate sources in a knowledge base?▼

Tracking deferred or duplicate sources requires synchronizing the filesystem state with raw/_manifest.yaml. The ingest sync command detects these anomalies during scanning and keeps them explicitly recorded in the manifest for review.

How do I detect file deltas between my filesystem and a yaml manifest?▼

Detecting file deltas involves scanning the raw/ directory for new or changed sources and comparing them against raw/_manifest.yaml. The ingest scan command identifies these discrepancies for confirmation before updating the manifest.

Why does my knowledge base compile process show missing provenance for raw sources?▼

Missing provenance occurs when raw sources are not registered in raw/_manifest.yaml. Running ingest sync normalizes entries and ties ingestion state to compile, review, and logging, ensuring full traceability of ingested files.

Do I need an up-to-date raw/_manifest.yaml before running ingest sync commands?▼

Yes, an up-to-date raw/_manifest.yaml is required. The ingest sync command compares filesystem deltas against this manifest to register new sources, detect changes, and prepare entries for downstream compile and review processes.