agentleFS
Sign inStart free
MicrosoftKnown publishermicrosoft/llmwiki/plugin/skills/wiki-ingest/SKILL.md

wiki-ingest

Skill116 starsChanged 4 days agoMITView on GitHub

Ingest a source document (article, paper, notes, transcript) into the user's LLM Wiki and integrate it — summary page, entity and concept pages, crosslinks and a health check — with the LLM Wiki MCP tools. Use when the user wants to add, file, import or ingest a source into their wiki.

47 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

  • 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-init

    Use when bootstrapping a new personal wiki for any knowledge domain — research, codebase documentation, reading notes, competitive analysis, or any long-term knowledge accumulation project.

    Also in 7 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

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 0 are distinctive, and 5 are very specific to this project.

  • 0

    Common

    Most of the 38 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 5

    Very specific

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

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

    Ingest: Call wiki_ingest_with_context with sourcePath set to raw/<file>.

    line 10
  2. Very specific:

    Improve the summary: Read the source and the summary page.

    line 13
  3. Very specific:

    Connect: Use wiki_add_crosslinks to link the new pages to related existing pages, and the existing pages back to the new ones.

    line 16
  4. Very specific:

    Check health: Run wiki_lint and fix anything this ingest introduced (for example broken links).

    line 17
  5. Very specific:

    If a tool reports that no wiki is open, call wiki_open with the absolute path of the current workspace folder, then retry.

    line 20

“Common” is measured: kept by at least 6 in 10 of the 38 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 a source into the wiki

  1. Place the source. Sources live in .wiki/raw/ and are never modified there. If the user points at a file elsewhere, copy it into .wiki/raw/ (keep the original where it is). In VS Code with the LLM Wiki extension, a file that appears in .wiki/raw/ is also ingested by the extension automatically.
  2. Ingest. Call wiki_ingest_with_context with sourcePath set to raw/<file>. It writes a summary page under sources/ and returns related_pages and suggested_actions.
    • If it reports skipped because the source was already ingested (for example by the VS Code extension), don't force it. Read the existing summary page it returns as summary_page, check which entity and concept pages already exist, and only add what is missing in the steps below.
    • Re-ingesting with force: true overwrites the summary page; do it only if the user asks.
  3. Improve the summary. Read the source and the summary page. If the summary is a thin stub, rewrite it with wiki_update_page (bodyReplace): key points, notable claims and numbers, open questions.
  4. Extract entities and concepts. For each important person, organization or named thing, use wiki_create_entity; for each idea, technique or mechanism, use wiki_create_concept. Pass sources with the summary page path (for example ["sources/article-summary.md"]) so the page is cleaned up if the source is removed later.
    • First check related_pages and wiki_query: if a page already exists, extend it with wiki_update_page (bodyAppend) and pass addSources with the summary page path instead. The create tools overwrite a page with the same name.
  5. Connect. Use wiki_add_crosslinks to link the new pages to related existing pages, and the existing pages back to the new ones.
  6. Check health. Run wiki_lint and fix anything this ingest introduced (for example broken links).
  7. Report what was created, updated and linked.

If a tool reports that no wiki is open, call wiki_open with the absolute path of the current workspace folder, then retry.

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.

Check your setup, free