Run any Skill in Manus with one click

ingest

Stars3

Forks0

UpdatedJune 20, 2026 at 12:54

Ingest a source into the Loop Library — read it, mirror it immutably, write its Source concept, and compile it into the wiki (loops/concepts/comparisons), updating indexes and the log. Use when the user adds a source (a paper, post, doc, transcript) or drops a file in inbox/ and wants it folded into the knowledge base.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

dudgeon

dudgeon/loop-library

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Market Research Analysts and Marketing SpecialistsBusiness and Financial Operations Occupations·SOC 13-1161

SKILL.md

readonly

name	ingest
description	Ingest a source into the Loop Library — read it, mirror it immutably, write its Source concept, and compile it into the wiki (loops/concepts/comparisons), updating indexes and the log. Use when the user adds a source (a paper, post, doc, transcript) or drops a file in inbox/ and wants it folded into the knowledge base.

Ingest

Karpathy's first operation: a source → many compiled pages. The bottleneck is bookkeeping; your job is to do all of it. Read CLAUDE.md §3 and the schema in _meta/SPEC-loop.md first.

Preconditions

The source must be approved: already in sources/, or the human OK'd a file in inbox/. Never invent a source. If it's only in inbox/, confirm before promoting.

Steps

Read the source fully from sources/<id>.md (or the approved inbox/ file).
Discuss the key takeaways with the human; ask what to emphasize. Ingest one source at a time and stay involved unless told to batch. When you need a decision (what to emphasize, whether to promote an inbox/ file, which pages to compile), ask with the structured AskUserQuestion prompt (concrete options), not a free-text question.
Immutable mirror — ensure sources/<id>.md exists (canonical name <author-or-org>-<year>-<slug>.md). If you just promoted it from inbox/, move it now. Never edit a mirror after creation.
Source concept — create/update wiki/sources/<id>.md with type: Source, resource: (canonical URL), raw_mirror: ../sources/<id>.md, authors:, a one-paragraph digest, # Key points, # Notable excerpts (short verbatim quotes), # Compiled into.
Compile into wiki/: create or update the Loop, Concept, and Comparison pages this source informs. One source typically touches several pages. Each compiled page must declare type, summary:, sources: (link back to /sources/<id>.md), provenance:, and a # Citations section. Tag each claim's basis honestly (extracted vs inferred).
Indexes — update wiki/index.md and each affected directory index.md.
Log — append a newest-first entry to wiki/log.md: - ingest | <Source title> — <what changed>.
Verify — run scripts/conformance.sh (must pass) and scripts/lint.sh (review warnings). A change isn't done until conformance is green.

Don'ts

Don't auto-promote from inbox/ without approval. Don't edit sources/. Don't write a compiled page without at least one citation. Don't fill gaps with confident guesses — mark them inferred or flag them.

More from this repository

same repository

distill

dudgeon/loop-library

Keep this project's graph lean and trustworthy — merge duplicates, retire stale notes (respecting task hierarchy), resolve contradictions, fix links, resolve entities, flag type drift, re-derive the per-entity timelines, regenerate the index-views, and surface stale tasks. Suggest-only; asks before deleting. Use periodically, before an important piece of work, or when the graph feels noisy. (brainkit's name for Karpathy's "lint".)

2026-06-303

ingest

dudgeon/loop-library

Capture new material into this project's graph as a typed entity — resolve what it mentions to canonical notes (with you, at capture), expand its shorthand and link it, preserve the raw, append to any touched entity's timeline, and extract the reusable knowledge and tasks. Use whenever the user shares or refers to something the brain should remember — a call, a meeting note, a doc, a decision, a person, a task, a link.

2026-06-303

query

dudgeon/loop-library

Put this project's graph to work toward the deliverable — answer a grounded question, advance a work/ deliverable with citations, run gap analysis ("what's missing for this?"), or read the task and reading-queue views — and file genuinely new conclusions back. Use when the user asks something the brain should know, asks to move a deliverable forward, or asks what's open or unprocessed.

2026-06-303

sync

dudgeon/loop-library

Curate upstream improvements into this kit — a research task, not a script. Read canonical brainkit upstream, reason about what genuinely improved, and pull in only the changes you and the user find compelling, preserving local tweaks. Suggest-only; never bulk-overwrites. Use when the user wants to refresh the kit's machinery from origin.

2026-06-283

sync

dudgeon/loop-library

Curate upstream improvements into this kit — a research task, not a script. Read canonical karpathy-core upstream, reason about what genuinely improved, and pull in only the changes you and the user find compelling, preserving local tweaks. Suggest-only; never bulk-overwrites. Use when the user wants to refresh the kit's machinery from origin.

2026-06-283

sync

dudgeon/loop-library

Curate upstream improvements into this kit — a research task, not a script. Read canonical loopkit upstream, reason about what genuinely improved, and pull in only the changes you and the user find compelling, preserving local tweaks. Suggest-only; never bulk-overwrites. Use when the user wants to refresh the kit's machinery from origin.

2026-06-283

name	ingest
description	Ingest a source into the Loop Library — read it, mirror it immutably, write its Source concept, and compile it into the wiki (loops/concepts/comparisons), updating indexes and the log. Use when the user adds a source (a paper, post, doc, transcript) or drops a file in inbox/ and wants it folded into the knowledge base.

Ingest

Karpathy's first operation: a source → many compiled pages. The bottleneck is bookkeeping; your job is to do all of it. Read CLAUDE.md §3 and the schema in _meta/SPEC-loop.md first.

Preconditions

The source must be approved: already in sources/, or the human OK'd a file in inbox/. Never invent a source. If it's only in inbox/, confirm before promoting.

Steps

Read the source fully from sources/<id>.md (or the approved inbox/ file).
Discuss the key takeaways with the human; ask what to emphasize. Ingest one source at a time and stay involved unless told to batch. When you need a decision (what to emphasize, whether to promote an inbox/ file, which pages to compile), ask with the structured AskUserQuestion prompt (concrete options), not a free-text question.
Immutable mirror — ensure sources/<id>.md exists (canonical name <author-or-org>-<year>-<slug>.md). If you just promoted it from inbox/, move it now. Never edit a mirror after creation.
Source concept — create/update wiki/sources/<id>.md with type: Source, resource: (canonical URL), raw_mirror: ../sources/<id>.md, authors:, a one-paragraph digest, # Key points, # Notable excerpts (short verbatim quotes), # Compiled into.
Compile into wiki/: create or update the Loop, Concept, and Comparison pages this source informs. One source typically touches several pages. Each compiled page must declare type, summary:, sources: (link back to /sources/<id>.md), provenance:, and a # Citations section. Tag each claim's basis honestly (extracted vs inferred).
Indexes — update wiki/index.md and each affected directory index.md.
Log — append a newest-first entry to wiki/log.md: - ingest | <Source title> — <what changed>.
Verify — run scripts/conformance.sh (must pass) and scripts/lint.sh (review warnings). A change isn't done until conformance is green.

Don'ts

Don't auto-promote from inbox/ without approval. Don't edit sources/. Don't write a compiled page without at least one citation. Don't fill gaps with confident guesses — mark them inferred or flag them.