llmwiki-ingest
Skill383 starsChanged 5 months agoMITView on GitHub
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/`.
In this repository7 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- llmwiki-querySkill
- llmwiki-syncSkill
- project-maintainerSkill
- self-learnSkill
- wiki-allSkill
The file
We split this skill into the rules it gives an agent
11 rules. About 0 are common, 2 are distinctive, and 9 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
9
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 27
Follow the Ingest Workflow from the repo's CLAUDE.md exactly:
- Distinctive: line 29
Read the source file(s) with the Read tool
- Very specific: line 30
Read wiki/index.md and wiki/overview.md for context
- Very specific: line 31
Write wiki/sources/<slug>.md using the Source Page Format
- Very specific: line 32
Update wiki/index.md — new entry under ## Sources
- Very specific: line 33
Update wiki/overview.md if substantial new info
- Very specific: line 34
Create/update entity pages (wiki/entities/<TitleCase>.md)
- Very specific: line 35
Create/update concept pages (wiki/concepts/<TitleCase>.md)
- Very specific: line 42
When the source is under raw/sessions/ (a session transcript converted by the converter):
- Very specific: line 54
No silent overwrites. Conflicting claims go under ## Contradictions.
- Very specific: line 55
Every page has a ## Connections section with at least one [[wikilink]].
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
llmwiki-ingest
What this skill does
Takes a source file (or a folder) and turns it into wiki pages following the Karpathy LLM Wiki pattern:
- Writes a
wiki/sources/<slug>.mdsummary - Creates/updates entity pages for people, companies, projects, tools, libraries mentioned
- Creates/updates concept pages for ideas, patterns, decisions discussed
- Cross-links everything with
[[wikilinks]] - Flags contradictions
- Updates
wiki/index.md,wiki/overview.md,wiki/log.md
When to use
- User says "ingest this file", "add this to the wiki", "process this into the wiki"
- User runs the
/wiki-ingestslash command - User says "sync the wiki" — in that case, the
llmwiki-syncskill runs the converter first, then invokes this skill for each new file
Workflow
Follow the Ingest Workflow from the repo's CLAUDE.md exactly:
- Read the source file(s) with the Read tool
- Read
wiki/index.mdandwiki/overview.mdfor context - Write
wiki/sources/<slug>.mdusing the Source Page Format - Update
wiki/index.md— new entry under## Sources - Update
wiki/overview.mdif substantial new info - Create/update entity pages (
wiki/entities/<TitleCase>.md) - Create/update concept pages (
wiki/concepts/<TitleCase>.md) - Cross-link with
[[wikilinks]]under## Connections - Flag contradictions under
## Contradictions - Append to
wiki/log.md:## [YYYY-MM-DD] ingest | <title>
Session-specific rules
When the source is under raw/sessions/ (a session transcript converted by the converter):
- Trust the frontmatter as authoritative (project, started, model, tools_used, etc.)
- Do not copy the
## Conversationsection verbatim — use it as raw material to summarise - Create a project entity page at
wiki/entities/<ProjectSlug>.mdwith a## Sessionslist - Extract decisions into
wiki/concepts/— anything the user explicitly locked - Extract tools used — every entry in
tools_usedis a candidate entity - If
is_subagent: true— link to the parent session rather than creating a new project entity
Hard rules
raw/is immutable. Never modify files there.- No silent overwrites. Conflicting claims go under
## Contradictions. - Every page has a
## Connectionssection with at least one[[wikilink]]. - Frontmatter is authoritative. Always populate
title,type,tags,sources,last_updated.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

