wiki-ingest
byagricidaniel· 164 skills
Ingest sources into the Obsidian wiki vault. Reads a source, extracts entities and concepts, creates or updates wiki pages, cross-references, and logs the operation. Supports files, URLs, and batch mode. Triggers on: ingest, process this source, add this to the wiki, read and file this, batch ingest, ingest all of these, ingest this url.
How to install wiki-ingest?
agricidaniel/claude-obsidian/wiki-ingest
$npx -y skills add agricidaniel/claude-obsidian --skill wiki-ingestInstalls into the current project.
›Prefer a prompt? Paste this to your agent
Run `npx skills use "https://github.com/agricidaniel/claude-obsidian" --skill "agricidaniel/claude-obsidian/wiki-ingest"` and follow the generated skill instructions now. Read its complete output, redirecting it to a temporary file first if necessary. Resolve relative paths from the supporting-files directory it provides.
Use the skills in "https://github.com/agricidaniel/claude-obsidian" that are relevant to the current task. Run `npx skills add "https://github.com/agricidaniel/claude-obsidian"` and select the relevant skills, then follow their instructions.
SKILL.md
| 1 | You are a wiki ingestion specialist. Your job is to process one source document and integrate it fully into the wiki. |
| 2 | |
| 3 | You will be given: |
| 4 | - A source file path (in `.raw/`) |
| 5 | - The vault path |
| 6 | - Any specific emphasis the user requested |
| 7 | |
| 8 | ## Your Process |
| 9 | |
| 10 | 1. Read the source file completely. |
| 11 | 2. Read `wiki/index.md` to understand existing wiki pages and avoid duplication. |
| 12 | 3. Read `wiki/hot.md` for recent context. |
| 13 | 4. Create a source summary page in `wiki/sources/`. Use proper frontmatter. |
| 14 | 5. For each significant person, org, product, or repo mentioned: check the index. Create or update the entity page in `wiki/entities/`. |
| 15 | 6. For each significant concept, idea, or framework: check the index. Create or update the concept page in `wiki/concepts/`. |
| 16 | 7. Update relevant domain pages. Add a brief mention and wikilink to new pages. |
| 17 | 8. Update `wiki/entities/_index.md` and `wiki/concepts/_index.md`. |
| 18 | 9. Check for contradictions with existing pages. Add `> [!contradiction]` callouts where needed. |
| 19 | 10. Return a summary of what you created and updated. |
| 20 | |
| 21 | ## Mode awareness (v1.8+): consult the router BEFORE writing |
| 22 | |
| 23 | Before creating any page under `wiki/`, consult the vault's methodology mode via: |
| 24 | |
| 25 | ```bash |
| 26 | python3 scripts/wiki-mode.py route <type> "<name>" |
| 27 | ``` |
| 28 | |
| 29 | Where `<type>` is `source`, `entity`, `concept`, or `session`. The router returns the vault-relative path appropriate for the active mode (`generic` / `lyt` / `para` / `zettelkasten`). If `.vault-meta/mode.json` is absent, the router returns mode=generic paths, preserving v1.7 behavior byte-for-byte. |
| 30 | |
| 31 | Replace the hardcoded paths in §Your Process steps 4-6 with router-returned paths: |
| 32 | - Step 4 (source page): `python3 scripts/wiki-mode.py route source "<source-slug>"` instead of `wiki/sources/<slug>.md` |
| 33 | - Step 5 (entity pages): `python3 scripts/wiki-mode.py route entity "<Name>"` instead of `wiki/entities/<Name>.md` |
| 34 | - Step 6 (concept pages): `python3 scripts/wiki-mode.py route concept "<Name>"` instead of `wiki/concepts/<Name>.md` |
| 35 | |
| 36 | This matches the orchestrator-side behavior of `skills/wiki-ingest/SKILL.md` §Mode awareness. The orchestrator and this sub-agent MUST route consistently — otherwise parallel batch-ingest in LYT/PARA/Zettelkasten vaults files to the wrong folders. |
| 37 | |
| 38 | Names passed to the router are sanitized via `safe_name()` (path-traversal + control-char strip) in v1.8.2+, so passing user-extracted entity/concept names directly is safe. |
| 39 | |
| 40 | ## Concurrency (v1.7+): per-file locks REQUIRED for page writes |
| 41 | |
| 42 | Multi-writer page creation IS safe in v1.7 because every page write is gated by `scripts/wiki-lock.sh`. Acquire before write, release after: |
| 43 | |
| 44 | ```bash |
| 45 | bash scripts/wiki-lock.sh acquire wiki/sources/<slug>.md || { |
| 46 | # Another writer holds the same page — skip it this pass; log to wiki/log.md |
| 47 | echo "skipped wiki/sources/<slug>.md (locked)"; continue |
| 48 | } |
| 49 | # … write the page via Write/Edit ($Transport-selected method) … |
| 50 | bash scripts/wiki-lock.sh release wiki/sources/<slug>.md |
| 51 | ``` |
| 52 | |
| 53 | The lock semantics (age-based, 60s default stale window, cross-process release allowed) are documented in `scripts/wiki-lock.sh` and `skills/wiki-ingest/SKILL.md` §Concurrency. There is no opt-out; this is core in v1.7. |
| 54 | |
| 55 | ## DragonScale address assignment (still single-writer at the allocator) |
| 56 | |
| 57 | If the vault has adopted DragonScale Mechanism 2 (detected by `[ -x ./scripts/allocate-address.sh ] && [ -d ./.vault-meta ]`): |
| 58 | |
| 59 | - **Parallel ingest sub-agents STILL MUST NOT call `scripts/allocate-address.sh` directly.** The allocator is flock-guarded for atomicity, but the `.raw/.manifest.json` `address_map` update pattern assumes single-writer semantics for the manifest specifically. |
| 60 | - The orchestrator (not this sub-agent) runs the allocator sequentially for each page after all parallel sub-agents finish, then updates the `address_map` in `.raw/.manifest.json` and writes addresses into frontmatter. |
| 61 | - Sub-agents write pages WITHOUT the `address:` field. The orchestrator backfills addresses in a post-pass. |
| 62 | |
| 63 | The wiki-lock guard covers PAGE writes; the allocator guard covers ADDRESS writes. Both are needed because they protect different invariants (file content vs. counter monotonicity). |
| 64 | |
| 65 | If the |
Related
6 picksType
- grill-with-docsA relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.Jul 2026
- lark-doc飞书云文档（Docx / Wiki 文档）：读取和编辑飞书文档内容。当用户给出文档 URL 或 token，或需要查看、创建、编辑文档、插入或下载文档图片附件时使用。文档中嵌入的电子表格、多维表格、画板，先用本 skill 提取 token 再切到对应 skill。当用户给出 doubao.com 的 /docx/…Jul 2026
- lark-wiki飞书知识库：管理知识空间、空间成员和文档节点。创建和查询知识空间、查看和管理空间成员、管理节点层级结构、在知识库中组织文档和快捷方式。当用户需要在知识库中查找或创建文档、浏览知识空间结构、查看或管理空间成员、移动或复制节点时使用。当用户给出 doubao.com 的 /wiki/ URL/token…Jul 2026
- lark-minutes飞书妙记：搜索妙记、查看妙记基础信息、下载/上传音视频、读取或编辑妙记的产物内容、改标题、替换说话人/关键词、申请妙记查看/编辑权限。当给出minute_token、本地音视频文件，要查/改/转妙记产物，或用户明确要主动申请妙记权限时使用；本地音视频转纪要/逐字稿优先走本 skill，不要用…Jul 2026
- lark-vc飞书视频会议：搜索历史会议记录、查询会议纪要（总结/待办/章节/逐字稿）、查询参会人快照。当用户查询已结束的会议、获取会议产物（纪要/妙记）、查看参会人时使用；查询未来日程走 lark-calendar。不负责：Agent 真实入会/离会、会中实时事件（走 lark-vc-agent）。Jul 2026
- writing-great-skillsReference for writing and editing skills well — the vocabulary and principles that make a skill predictable.Jul 2026
