Obsidian Wiki Ingest
Automate adding Markdown, PDFs, and other sources into an Obsidian vault with deduplication, frontmatter, and cross-links via the wiki-ingest pipeline.
Overview
Obsidian Wiki Ingest is an agent skill most often used in Build (also Operate iterate) that orchestrates deduplicated document ingestion into an Obsidian vault via the wiki-ingest pipeline.
Install
npx skills add https://github.com/ar9av/obsidian-wiki --skill obsidian-wiki-ingestWhat is this skill?
- Triggers on phrases like ingest to wiki or add to wiki inside the obsidian-wiki project
- Ingest modes: append, full, and raw—selected from user input or source change type
- Deduplication via manifest, frontmatter, and cross-links to existing pages
- Validates vault path and sources dir from environment before running wiki-ingest
- Updates manifest and logs and can refresh project overview pages after ingest
- Three ingest modes: append, full, and raw
Adoption & trust: 1.1k installs on skills.sh; 1.8k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
Your research and specs pile up in _raw_ folders while the Obsidian vault drifts out of sync, duplicates pages, and lacks cross-links.
Who is it for?
Solo builders running the obsidian-wiki project who want agent-driven, repeatable ingest from OBSIDIAN_SOURCES_DIR or _raw_ into OBSIDIAN_VAULT_PATH.
Skip if: Teams without Obsidian or the obsidian-wiki ingest toolchain who only need a one-off Markdown file created in chat.
When should I use this skill?
User says ingest to wiki, add to wiki, or similar while working in the obsidian-wiki project context.
What do I get? / Deliverables
Sources are processed through wiki-ingest with manifest updates, frontmatter, cross-links, and optional overview pages so the vault reflects the latest corpus.
- Updated vault pages with frontmatter and cross-links
- Updated ingest manifest and log metadata
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Personal and product knowledge bases are built and maintained as docs assets during implementation and ongoing operation. Ingest orchestration, manifest updates, and wiki cross-links are documentation/knowledge-base work, not application backend code.
Where it fits
Append new spec Markdown from OBSIDIAN_SOURCES_DIR into the vault with frontmatter and links to related pages.
Run a full ingest after reorganizing _raw_ so manifest and overview pages match production notes.
Ingest research PDFs into the wiki so discovery material is searchable alongside build docs.
How it compares
Project-specific ingest orchestration skill—not a generic note-taking MCP or manual Obsidian plugin tutorial.
Common Questions / FAQ
Who is obsidian-wiki-ingest for?
It is for maintainers of the obsidian-wiki repo who want an agent to run the wiki-ingest workflow instead of hand-merging every document.
When should I use obsidian-wiki-ingest?
Use it in Build when consolidating project docs into the vault, and in Operate when routinely adding imports from sources or _raw_ with append, full, or raw modes.
Is obsidian-wiki-ingest safe to install?
It can modify vault files and manifests on disk; review the Security Audits panel on this Prism page and confirm paths before full or raw modes.
SKILL.md
READMESKILL.md - Obsidian Wiki Ingest
#!/bin/bash set -e PROJECT_DIR="/home/ubuntu/projects/obsidian-wiki" VAULT_PATH="" SOURCES_DIR="" INGEST_MODE="append" echo "[obsidian-wiki-ingest] project= vault= sources= mode=" --- name: obsidian-wiki-ingest description: > Automates ingestion of documents into the Obsidian wiki (obsidian-wiki) using the wiki-ingest pipeline. Handles deduplication via manifest, frontmatter, and cross-links; triggers on user request within the obsidian-wiki project context. --- # Obsidian Wiki Ingest — Automation Skill You are the automation layer that ingests documents into the Obsidian wiki project. This skill orchestrates the ingestion workflow, ensuring deduplication, proper frontmatter, and cross-linking with existing pages. ## Trigger - User says: "ingest to wiki", "add to wiki", or any phrasing that targets the obsidian-wiki repository. - Context: active in the /home/ubuntu/projects/obsidian-wiki workspace. ## Responsibilities - Validate target vault path from the environment and manifest state. - Decide between Append, Full, or Raw ingest modes based on user input or changes in the source. - Invoke the wiki-ingest workflow to process new/modified sources. - Update manifest and log files with ingest metadata. - Create or update project overview pages and cross-links as needed. ## Inputs - Source documents (Markdown, PDFs, text, images) from OBSIDIAN_SOURCES_DIR or _raw/ - Vault path from OBSIDIAN_VAULT_PATH - Optional: ingest mode (append|full|raw) ## Outputs - Updated wiki pages with distilled knowledge - Updated .manifest.json and log entries - Optional: new/updated project overview pages ## Probing and Safety - Do not ingest secrets or sensitive data. - Respect existing page structure and avoid duplicating content. - Mark inferred/ambiguous knowledge with provenance notes. ## Example Workflow (high level) 1) Determine ingest mode and target paths 2) Run wiki-ingest with the chosen mode 3) Update manifest/log and refresh wiki index 4) Return a brief summary of changes ## Next Steps - If you approve, I’ll create a small wrapper script (scripts/ingest-wiki.sh) that kicks off the ingest for the current project and updates the manifest. Then wire a simple command alias to trigger this skill from the CLI. ## QMD Refresh After Vault Writes QMD is a search index, not the source of truth. If `$QMD_WIKI_COLLECTION` is empty or unset, skip this step. Run it only after this skill has written or rewritten vault markdown. If QMD refresh fails, do not roll back the vault changes; report the QMD status separately. Use `$QMD_CLI` if set; otherwise use `qmd`. ```bash ${QMD_CLI:-qmd} update ``` If the output says vectors are needed or embeddings may be stale, run: ```bash ${QMD_CLI:-qmd} embed ``` Verify the collection with either: ```bash ${QMD_CLI:-qmd} ls "$QMD_WIKI_COLLECTION" ``` or, when a specific page path is known: ```bash ${QMD_CLI:-qmd} get "qmd://$QMD_WIKI_COLLECTION/<page>.md" -l 5 ``` Record one of: - `QMD refreshed: update + embed + verified` - `QMD refreshed: update only + verified` - `QMD skipped: QMD_WIKI_COLLECTION unset` - `QMD skipped: qmd CLI unavailable` - `QMD failed: <short error summary>`