// Ingest one source document (or a folder of them) into the llmwiki. Use when the user drops a new markdown file, PDF, or URL into the wiki and asks you to process it. The user will typically say "ingest this", "add this to the wiki", "process this file into the wiki", or point at a file under `raw/`.
| name | llmwiki-ingest |
| description | Ingest one source document (or a folder of them) into the llmwiki. Use when the user drops a new markdown file, PDF, or URL into the wiki and asks you to process it. The user will typically say "ingest this", "add this to the wiki", "process this file into the wiki", or point at a file under `raw/`. |
Takes a source file (or a folder) and turns it into wiki pages following the Karpathy LLM Wiki pattern:
wiki/sources/<slug>.md summary[[wikilinks]]wiki/index.md, wiki/overview.md, wiki/log.md/wiki-ingest slash commandllmwiki-sync skill runs the converter first, then invokes this skill for each new fileFollow the Ingest Workflow from the repo's CLAUDE.md exactly:
wiki/index.md and wiki/overview.md for contextwiki/sources/<slug>.md using the Source Page Formatwiki/index.md — new entry under ## Sourceswiki/overview.md if substantial new infowiki/entities/<TitleCase>.md)wiki/concepts/<TitleCase>.md)[[wikilinks]] under ## Connections## Contradictionswiki/log.md: ## [YYYY-MM-DD] ingest | <title>When the source is under raw/sessions/ (a session transcript converted by the converter):
## Conversation section verbatim — use it as raw material to summarisewiki/entities/<ProjectSlug>.md with a ## Sessions listwiki/concepts/ — anything the user explicitly lockedtools_used is a candidate entityis_subagent: true — link to the parent session rather than creating a new project entityraw/ is immutable. Never modify files there.## Contradictions.## Connections section with at least one [[wikilink]].title, type, tags, sources, last_updated.Run the complete llmwiki pipeline from scratch — init, sync, graph, build, lint, and serve. Use when the user says "run everything", "full pipeline", "wiki-all", or wants to rebuild the entire wiki from session history.
Answer a question by querying the user's llmwiki. Use when the user asks about their own past work — "what did I decide about X", "what have I been working on", "how did I solve Y", "what's my preferred approach to Z", or any question that the wiki (built from their session history) might answer. Always read the wiki first before falling back to external search.
Sync Claude Code session transcripts into the user's llmwiki and ingest them into the wiki. Use when the user says "sync the wiki", "update llmwiki", "ingest recent sessions", "refresh the knowledge base", or asks a knowledge question that would benefit from up-to-date sessions. Also use when the user explicitly asks to refresh or rebuild the LLM wiki from their agent history.
Maintain an llmwiki-style open-source project across the full framework pipeline. Use when the user says "maintain the project", "check my tasks", "update progress", "run phase gate", "do a monthly verify", "lint my wiki", "check stale entries", or invokes any form of ongoing project-keeping chore. Reads _progress.md, tasks.md, docs/roadmap.md, and .github issues to figure out what's next and what's drifted.
Extract reusable patterns from recent sessions, propose framework improvements, and (with approval) update the framework docs. This is the dogfooding meta-loop — the project learns from its own usage. Use when the user says "learn from this", "what did we learn", "extract lessons", "update the framework", "add this to steering rules", or after completing any substantial feature or debugging session.