agentleFS
barakgutbarakgut/llm-wiki/skills/wiki-ingest/SKILL.md

wiki-ingest

Skill1 starsChanged 33 days agoMITView on GitHub

Ingest a raw source into the wiki - write its source page and integrate it into entity, concept and overview pages. Use when the user adds a file to raw/, pastes or links something to file, or says ingest/process/add this.

45 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use wiki-status, wiki-capture and 9 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • nexuschainsSkill

    wiki-status

    Reports the current state of the wiki vault — page counts, category breakdown, hub pages, orphans, stale entries, and a delta showing what has changed since the last ingest. Use this skill when the operator asks "what's the status", "wiki dashboard", "how many pages", "what's stale", "what's been ingested", "show me the delta", or "wiki health overview". Also surfaces structural insights (top hubs, fragmented clusters, bridge pages) when the operator asks "wiki insights", "what's central", or "show me the hubs". Read-only: this skill reports and recommends; it does not modify any files.

    Also in 5 projects that use this

  • jehrhardtSkill

    wiki-capture

    Quickly capture raw thoughts, links, images, or notes to today's Obsidian daily note from anywhere in Pi. Use when the user wants to jot something down for later wiki processing.

    Also in 6 projects that use this

  • Ivy-Chen1999Skill

    wiki-research

    Autonomously research a topic via multi-round web search, synthesize findings, and file structured results into the Obsidian wiki. Use this skill when the user says "/wiki-research [topic]", "research X", "find everything about Y", "do a deep dive on Z", "autonomous research on X", or wants comprehensive, web-sourced knowledge on a topic filed directly into their wiki.

    Also in 5 projects that use this

  • nexuschainsSkill

    cross-linker

    Scans the wiki vault and adds missing [[wikilinks]] between pages that are related but not yet connected. Use this skill when the operator says "link my pages", "find missing links", "cross-reference the wiki", "connect my wiki", "add wikilinks", or after any large ingest to weave new pages into the existing knowledge graph. Also trigger when orphaned pages need connecting or when wiki-lint reports fragmented tag clusters. This is a write-heavy skill — it modifies page files to insert links, unlike wiki-lint which only reports.

    Also in 4 projects that use this

  • Ivy-Chen1999Skill

    wiki-setup

    Initialize a new Obsidian wiki vault with the correct structure, special files, and configuration. Use this skill when the user wants to set up a new wiki from scratch, initialize the vault structure, create the .env file, or says things like "set up my wiki", "initialize obsidian", "create a new vault", "get started with the wiki". Also use when the user needs to reconfigure their existing vault or fix a broken setup.

    Also in 5 projects that use this

  • bozhouDevSkill

    wiki-update

    Use when revising existing wiki pages because knowledge has changed, a new piece of information updates or contradicts existing content, or the user wants to directly edit wiki content with LLM assistance.

    Also in 8 projects that use this

  • +1 more from nexuschains
  • +3 more from Ivy-Chen1999

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 36 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Select: Use the source the user named.

    line 32
  2. Very specific:

    PDF: follow llm-wiki ref pdf-ingest instead - extract, read all the text, read every image, chunk by chunk.

    line 34
  3. Distinctive:

    Standalone image: read it; the source page describes what it shows.

    line 35

“Common” is measured: kept by at least 6 in 10 of the 36 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Ingest

Page conventions: llm-wiki ref page-formats - read it before the first ingest of a session.

Paths written here (raw/…, wiki/…, AGENTS.md) are from the wiki root; the first line of llm-wiki stats says where that is. The CLI takes them as written and prints paths from the current directory: open, write and edit files by the printed form.

Ingest one source at a time. For a batch, run this whole sequence per source.

Dispatch (main session)

The main session selects, dispatches and talks to the user; the reading and writing happen in wiki-ingester subagents, each in a fresh context. A subagent given one of the assignments below goes straight to Steps.

  1. Select (step 1). For a PDF, run llm-wiki pdf raw/<file>.pdf and note the number of chunks. A text source over about 3,000 lines counts as multi-chunk.
  2. Read. Dispatch wiki-ingester with read raw/<file>. Multi-chunk PDF: one read chunk N of raw/<file>.pdf per chunk, up to 4 at a time (they write separate notes files). Done when llm-wiki pdf raw/<file>.pdf --plan shows every chunk done; re-dispatch any that is todo.
  3. Discuss (step 3), from the readers' reports. For more detail read the notes files' Summary sections, leaving the source itself to the subagents.
  4. Integrate. Dispatch one wiki-ingester with integrate raw/<file> and the user's steer.
    • More than 3 notes files: integrate in passes, so no context holds the whole document. Group the notes files in order, 2-3 per pass along clause boundaries, and dispatch integrate raw/<file> - pass K of N: notes <files> one pass at a time (passes edit the same pages). Every prompt carries the user's steer and what earlier passes created or left open. Pass 1 creates the source page with a [!todo] integration-status marker and a stub per part not yet integrated, and its sibling pages; each pass fills its part and ends at llm-wiki lint 0 errors; the last pass removes the marker and every other staging trace, revises the overview and writes the one log entry for the whole ingest.
    • A pass reads sections, not pages, so its context does not grow with the passes before it. From the source page it reads the status marker, the structure table and Open questions (grep -n '^## ' for the line numbers, then Read with offset and limit). To a sibling page it appends after reading only the page's last lines.
  5. Report (step 10) from its report - for a staged integration, from all the passes' reports. If it ended with lint errors, dispatch integrate again with those errors.

Unattended or batch ingest of a single-chunk source: one dispatch, ingest raw/<file>, replaces 2-4. Several sources: dispatch them one after another, since integrations edit the same pages.

Steps

  1. Select. Use the source the user named; otherwise llm-wiki pending and take the oldest. A URL or pasted text is first saved verbatim as a new file raw/<YYYY-MM-DD>-<slug>.md.
  2. Read the whole source, then every image it references in raw/assets/. Done when you can state its argument without looking.
    • PDF: follow llm-wiki ref pdf-ingest instead - extract, read all the text, read every image, chunk by chunk.
    • Standalone image: read it; the source page describes what it shows.
  3. Discuss. Give the user 3-7 takeaways, what looks new or contradicts the wiki, and what you plan to emphasize. Wait for their steer. Skip the wait only when they asked for unattended or batch ingest.
  4. Map. List every entity and concept the source says something substantive about. For each, run llm-wiki search "<name>" and classify it: update (page exists), create (no page, and it matters beyond this one source or the user cares), or mention only. Done when every item is classified.
  5. Source page. llm-wiki new source "<Title>" --raw raw/<file> --summary "<claim>" --tags a,b, then fill it: summary, key claims, links to every mapped entity/concept. A multi-chunk source puts claims, figures and errata on sibling pages from the start (llm-wiki new source "<Title> - figures" --slug <slug>-figures --raw raw/<file>; page-formats.md, Page size and sibling pages).
  6. Integrate. For each update page: read it, merge the new material where it belongs (rewrite, don't append a dated blob), cite [[source-slug]], add the slug to sources:, set updated. For each create: llm-wiki new entity|concept "<Name>" --sources <source-slug> and write it. Where the source disagrees with a page, add a [!contradiction] callout on both pages. Done when every mapped item is handled.
  7. Overview. Revise wiki/overview.md if the source changes the thesis, adds a thread, or closes an open question.
  8. Verify. llm-wiki lint - fix until 0 errors and no orphan, stale or unlinked-mention findings involving pages you touched.
  9. Log. llm-wiki log ingest "<Title>" -m "created: …; updated: …; contradictions: …".
  10. Report pages created and updated, contradictions found, and 2-3 follow-up questions or sources worth finding.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.