wiki-ingest
Skill0 starsChanged 4 months agoMITView on GitHub
Ingest a source into the wiki — store it raw (immutable), summarize it, update/create concept pages, and cross-link. Usage: /wiki-ingest {path-or-url} [topic]
47 other projects use a version of this.
Adopted by
Most recently taken up by
- microsoft/llmwikitheir own version, first seen Nov 15, 2026
- tboome33/obsidian-mcp-routertheir own version, first seen Nov 15, 2026
- methylo/claude-skill-booktheir own version, first seen Nov 8, 2026
- Ar9av/obsidian-wikitheir own version, first seen Nov 8, 2026
- barakgut/llm-wikitheir own version, first seen Nov 1, 2026
- chobizzy/llm-wikitheir own version, first seen Nov 1, 2026
Used with
Projects with it also use wiki-status, wiki-research 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.
nexuschainsSkillwiki-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
Ivy-Chen1999Skillwiki-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
nexuschainsSkillcross-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-Chen1999Skillwiki-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
bozhouDevSkillwiki-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
bozhouDevSkillwiki-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
Other versions47 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 47
- AgriciDaniel/claude-obsidian★ 16ksame name
- sanyuan0704/code-review-expert★ 3.9ksame name
- sanyuan0704/sanyuan-skills★ 3.9ksame name
- Ar9av/obsidian-wiki★ 3.7ksame name
- kfchou/wiki-skills★ 189same name
- IssacW228/student-llm-wiki★ 173same name
- microsoft/llmwiki★ 116same name
- bozhouDev/bozhou-skills★ 78same name
- vanillaflava/llm-wiki-skills★ 65same name
- cookyman74/llmwiki-harness★ 34same name
37 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository21 other files it gives its agents.
- add-to-claudeSkill
- add-to-rulesSkill
- audit-claudeSkill
- audit-rulesSkill
- autopilotSkill
- better-planSkill
- design-autoSkill
- designSkill
- execute-autoSkill
- executeSkill
- facts-extSkill
- factsSkill
- questionsSkill
- research-autoSkill
- researchSkill
- review-autoSkill
- structure-autoSkill
- structureSkill
- wiki-captureSkill
- wiki-lintSkill
- wiki-querySkill
The file
We split this skill into the rules it gives an agent
10 rules. 0 are common, 3 are distinctive, and 7 are very specific to this project.
0
Common
Most of the 38 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 6
Read wiki/SCHEMA.md first — it defines layout, frontmatter, naming, and the [[wikilink]] cross-reference convention.
- Very specific: line 15
If a URL: fetch it and save a markdown capture to wiki/raw/{topic}/YYYY-MM-DD-{slug}.md with a header line recording the original URL and …
- Very specific: line 17
If a local path: copy (don't move) the file into wiki/raw/{topic}/ if it isn't already there.
- Distinctive: line 18
Never edit raw sources after this — they are the verification baseline.
- Distinctive: line 22
Read the source. Summarize the 5–10 most important, concrete takeaways to the user (facts, mechanisms, constraints, numbers — not vibes).
- Very specific: line 27
Create wiki/sources/{slug}.md with frontmatter (type: source, sources: ["raw/.../{file}"]) and the confirmed takeaways as bullets.
- Very specific: line 33
If a wiki/concepts/{slug}.md (or entities/) page exists, update it — add facts (each with a sources: trace), revise summaries, and flag …
- Distinctive: line 36
If it doesn't exist and matters, create it from the SCHEMA template.
- Very specific: line 40
Add [[wikilinks]] between the new/updated pages and existing related pages (aim ~5–15 across the ingest).
- Very specific: line 45
Add/refresh the page's line in wiki/index.md under the right type heading.
“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.
Files
Read wiki/SCHEMA.md first — it defines layout, frontmatter, naming, and
the [[wikilink]] cross-reference convention. Follow it exactly.
Parse the input:
- First argument is a path or URL to the source.
- Any remaining text is a topic hint.
Phase 1 — Acquire into raw/ (immutable)
- If a URL: fetch it and save a markdown capture to
wiki/raw/{topic}/YYYY-MM-DD-{slug}.mdwith a header line recording the original URL and fetch date. - If a local path: copy (don't move) the file into
wiki/raw/{topic}/if it isn't already there. - Never edit raw sources after this — they are the verification baseline.
Phase 2 — Discuss takeaways
Read the source. Summarize the 5–10 most important, concrete takeaways to the user (facts, mechanisms, constraints, numbers — not vibes). Confirm or let the user correct emphasis before filing.
Phase 3 — Write the source summary
Create wiki/sources/{slug}.md with frontmatter (type: source, sources: ["raw/.../{file}"]) and
the confirmed takeaways as bullets. Each takeaway should name the concept(s) it informs via [[links]].
Phase 4 — Update / create concept & entity pages
For each concept the source touches:
- If a
wiki/concepts/{slug}.md(orentities/) page exists, update it — add facts (each with asources:trace), revise summaries, and flag contradictions with what was there (don't silently overwrite — note the conflict and prefer the better-sourced claim; bumpupdated:andconfidence:). - If it doesn't exist and matters, create it from the SCHEMA template.
Phase 5 — Cascade cross-links
Add [[wikilinks]] between the new/updated pages and existing related pages (aim ~5–15 across the
ingest). Update each touched page's related: frontmatter. Do not leave a new page orphaned.
Phase 6 — Update index & log
- Add/refresh the page's line in
wiki/index.mdunder the right type heading. - Append one line to
wiki/log.md:YYYY-MM-DD | ingest | {pages touched} | {note}.
Phase 7 — Report
Tell the user: the raw path, the source summary page, which concept pages were created vs updated, any contradictions flagged, and any referenced-but-missing concepts that should be filled next.
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.

