
Kb Ingest
- 3 installs
- 3 repo stars
- Updated July 9, 2026
- bahayonghang/obsidian-notes-karpathy
kb-ingest is a Claude Code skill that registers and normalizes raw source intake for an Obsidian knowledge base into a canonical raw/_manifest.yaml before compile runs.
About
The kb-ingest skill registers and normalizes raw source intake for an Obsidian knowledge base into a canonical raw/_manifest.yaml manifest before compile runs. A developer uses it to discover raw sources, compare against the manifest, and record new or changed entries. It matters because it keeps paper PDFs and assets visible at the manifest layer, preserves first_seen_at, and never rewrites raw content.
- Registers and normalizes raw sources into raw/_manifest.yaml before compile runs
- Explicitly marks deferred sources such as paper PDFs instead of hiding them
- Preserves first_seen_at and never rewrites raw/ content
Kb Ingest by the numbers
- 3 all-time installs (skills.sh)
- Ranked #1,267 of 1,879 Documentation skills by installs in the Skillselion catalog
- Data as of Jul 28, 2026 (Skillselion catalog sync)
kb-ingest capabilities & compatibility
Free; operates on a local Obsidian vault, no API keys stated.
- Capabilities
- kb compile · kb review · kb init
- Works with
- obsidian
- Use cases
- documentation
- Pricing
- Free
What kb-ingest says it does
Track raw sources in a canonical manifest before compile shapes draft knowledge.
never rewrite `raw/**` content
npx skills add https://github.com/bahayonghang/obsidian-notes-karpathy --skill kb-ingestAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 3 |
|---|---|
| repo stars | ★ 3 |
| Last updated | July 9, 2026 |
| Repository | bahayonghang/obsidian-notes-karpathy ↗ |
What it does
Register and normalize raw sources into an Obsidian vault manifest before compiling draft knowledge.
Who is it for?
Recording raw/** captures into a canonical manifest before kb-compile shapes draft knowledge.
Skip if: Draft generation, review, query, or maintenance once the source registry is already current.
When should I use this skill?
The user says kb ingest, ingest sources, refresh manifest, register new raw files, or scan raw library.
What you get
An up-to-date raw/_manifest.yaml recording new, changed, unchanged, removed, and deferred sources.
- updated raw/_manifest.yaml
- intake report of new/changed/deferred sources
By the numbers
- 4-step minimal loop
Files
KB Ingest
Track raw sources in a canonical manifest before compile shapes draft knowledge.
Minimal loop
1. discover raw sources 2. compare them against raw/_manifest.yaml 3. register new or changed entries 4. mark deferred sources such as paper PDFs explicitly instead of hiding them
Read before ingesting
- local
AGENTS.md - local
CLAUDE.mdif present ../obsidian-notes-karpathy/scripts/skill-contract-registry.json../obsidian-notes-karpathy/references/file-model.md../obsidian-notes-karpathy/references/lifecycle-matrix.md../obsidian-notes-karpathy/references/activity-log-template.md../obsidian-notes-karpathy/references/paper-ingestion-lifecycle.md../obsidian-notes-karpathy/references/source-manifest-contract.md../obsidian-notes-karpathy/references/profile-contract.md
Treat skill-contract-registry.json as the canonical source for required references, baseline script, and write surfaces.
If available, run:
../obsidian-notes-karpathy/scripts/scan_ingest_delta.py../obsidian-notes-karpathy/scripts/sync_source_manifest.pywhen the task is writable
Rules
- never rewrite
raw/**content - always record paper PDFs in the manifest even when compile must defer them
- keep image and data assets visible at the manifest layer even if downstream compile remains metadata-first
- preserve
first_seen_atwhen an entry already exists - use
raw/_manifest.yamlas the user-visible canonical registry
Output to the user
Report:
1. whether the manifest was missing, current, or stale 2. how many sources were new, changed, unchanged, or removed 3. which sources were deferred and why 4. whether the next step is kb-compile
Related skills
FAQ
Does kb-ingest change raw content?
No, it never rewrites raw/** content and preserves first_seen_at when an entry already exists.
How are paper PDFs handled?
They are always recorded in the manifest even when compile must defer them.