Skip to main content
skill CX Codex

wiki-ingest · thoreinstein — Claude Code skill: what it does, how to install

wiki-ingest distills external files, transcripts, and Readwise exports into structured Obsidian notes with RAG-based deduplication and source tracking.

ISC ★ 102 updated 2026-10-25

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add thoreinstein/gemini-obsidian --skill wiki-ingest -a claude-code
Open on GitHub

What wiki-ingest does

The skill accepts local files, directories, or internal vault notes to process. It checks .manifest.json at the vault root first: if a source was already processed and remains unchanged since ingested_at, it skips execution unless invoked with --force.

Extracted information is sorted into patterns, traps, decisions, and concepts. Each point receives provenance metadata indicating whether it was directly extracted, inferred via ^[inferred], or ambiguous via ^[ambiguous]. Before touching any files, the agent queries the vault using obsidian_rag_query to decide between creating a new note or appending details to an existing entry.

All modifications require explicit user confirmation after the agent presents the ingest plan. The workflow relies directly on vault tools such as obsidian_read_note and obsidian_create_note, making an active Obsidian integration mandatory.

What it helps with

  • distill research papers and PDFs into Obsidian vault notes
  • avoid duplicate notes using vector RAG search across the vault
  • track statement provenance with explicit inference markers
  • maintain an ingestion audit log inside .manifest.json

Example prompts for the agent

  • /wiki-ingest ~/Documents/paper.pdf
  • /wiki-ingest working/appiary/knowledge/auth-notes.md
  • /wiki-ingest --force ~/Documents/paper.pdf

How to install wiki-ingest

1Skills CLI (Vercel)

npx skills add thoreinstein/gemini-obsidian --skill wiki-ingest -a claude-code

2Manually: put the files in place

~/.claude/skills/wiki-ingest/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/wiki-ingest/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about wiki-ingest

How to install wiki-ingest in Claude Code?

Run npx skills add thoreinstein/gemini-obsidian --skill wiki-ingest -a claude-code in your terminal.

What does wiki-ingest do?

It reads documents, identifies patterns and decisions, checks for vault duplicates via RAG, and generates structured notes with source citations.

Where does wiki-ingest place new notes?

Cross-project notes go into Engineering/Patterns/, Engineering/Traps/, or Engineering/Decisions/, while project-specific findings go to working/<project>/knowledge/.

Source text

SKILL.md · ISC
---
name: wiki-ingest
description: >-
  Use when the user wants to ingest external sources into the vault — PDFs,
  markdown files, transcripts, Readwise exports, or any document. Triggers on
  "ingest", "process document", "import into vault", "distill this", "add to
  vault", or "extract knowledge from".
---

# Wiki Ingest

Distill external sources into vault-native notes following VAULT_CONVENTIONS, with provenance tracking and deduplication.

## Workflow

### 1. Identify Sources

Accept one or more source paths from the user. Sources can be:
- Files on disk (markdown, PDF, text, transcripts)
- Vault-internal notes (Readwise highlights, working notes to promote)
- A directory to scan for ingestible files

For vault-internal sources, use `obsidian_read_note`. For external files, use the `Read` tool.

### 2. Check Manifest

Read `.manifest.json` from the vault root using `Read` tool.

For each source path, check if it exists in `sources`:
- **Not present** → new source, proceed to extract
- **Present but source modified since `ingested_at`** → re-ingest
- **Present and unchanged** → skip (tell user "already ingested, use --force to re-process")

### 3. Extract Knowledge

Read the source content. Identify:
- **Patterns** — reusable approaches, techniques, or practices
- **Traps** — pitfalls, anti-patterns, things that went wrong
- **Decisions** — architectural or design choices with rationale
- **Concepts** — definitions, mental models, frameworks

For each extraction, classify its **provenance**:
- **Extracted** (unmarked) — directly stated in the source
- **Inferred** `^[inferred]` — synthesized, generalized, or implied but not stated
- **Ambiguous** `^[ambiguous]` — source is unclear or contradicts other sources

### 4. Deduplicate

For each extracted concept, search the vault:
1. Call `obsidian_rag_query` with the concept name/summary, `limit: 5`
2. If a strong match exists, read the existing note with `obsidian_read_note`
3. Decide: **merge** into existing note or **create** new note

**Merge** when: the existing note covers the same concept and the new source adds information.
**Create** when: no existing note covers this concept, or the angle is sufficiently different.

### 5. Present Plan

Before creating or modifying any notes, present the plan to the user:

```
## Ingest Plan for: <source name>

### New Notes
- Engineering/Patterns/<name>.md — <one-line summary>
- Engineering/Traps/<name>.md — <one-line summary>

### Merge Into Existing
- Engineering/Patterns/<existing>.md — adding: <what's new>

### Skipped
- <concept> — already covered in [[existing-note]]
```

Wait for user confirmation before proceeding.

### 6. Write Notes

For **new notes**, use `obsidian_create_note` with content following VAULT_CONVENTIONS templates:

- Set `type:` to pattern, trap, or decision
- Set `project:` to the source project or "general"
- Set `tags:` from content
- Set `created:` to today's date
- Set `provenance:` fractions based on inline marker counts
- Include `## Links` section with `[[wikilinks]]` to related vault notes
- Add `## Sources` section citing the ingested source

For **merges**, use `obsidian_insert_at_heading` or `obsidian_replace_section` to add new content to existing notes. Update the `provenance:` frontmatter if the mix changed, using `obsidian_update_frontmatter`.

### 7. Placement Rules

- Cross-project patterns/traps/decisions → `Engineering/Patterns/`, `Engineering/Traps/`, `Engineering/Decisions/`
- Project-specific knowledge → `working/<project>/knowledge/`
- If unclear, ask the user

### 8. Update Manifest

After all notes are written, update `.manifest.json`:

For each processed source, add/update an entry in `sources`:
```json
{
  "<source-path>": {
    "ingested_at": "<ISO8601 now>",
    "size_bytes": <file size>,
    "modified_at": "<source file mtime>",
    "source_type": "document",
    "pages_created": ["Engineering/Patterns/foo.md"],
    "pages_updated": ["Engineering/Traps/bar.md"]
  }
}
```

Update `stats.total_sources_ingested` and `stats.total_pages`. Set `last_updated` to now.

Write the updated manifest back using the `Write` tool.

### 9. Suggest MOC Updates

For each new Engineering/ note created, check which thematic MOCs it belongs in. Suggest additions but don't auto-edit MOCs — use `/moc-update` for that.

## Arguments

- Source path(s): `/wiki-ingest ~/Documents/paper.pdf`
- Optional project scope: `/wiki-ingest working/appiary/knowledge/auth-notes.md`
- Optional force flag: `/wiki-ingest --force <path>` to re-ingest unchanged sources

## Tips

- Run `/index` first if `obsidian_rag_query` returns poor results
- For Readwise books, ingest the book's highlight file (e.g., `Readwise/Books/<title>.md`)
- Large sources may yield many extractions — review the plan carefully before confirming
- Provenance fractions don't need to be exact; approximate to the nearest 0.05

© thoreinstein · ISC · thoreinstein/gemini-obsidian

Similar skills

All skills for Notes, tasks and projects →

wiki-ingest by other authors comes first.

wiki-ingest sanyuan0704 wiki-ingest builds a linked wiki knowledge base from articles, documents, and notes. Use it when project material needs to become separate, cross-referenced knowledge pages. CX Codex +1 2,900installs wiki-ingest Ar9av wiki-ingest pulls documents, folders, pasted text and URLs into an Obsidian wiki, turning them into linked pages and skipping sources that have not changed. CX Codex +1 3,700installs wiki-ingest AgriciDaniel The wiki-ingest skill turns supplied material into linked Obsidian notes while keeping provenance and tracking claims. Useful when a paper, file or link needs to be filed into a vault. CX Codex +1 555installs llm-wiki akillness llm-wiki turns articles, notes, transcripts, and other source files into a linked markdown wiki. The agent keeps source material apart from its maintained knowledge pages. CX Codex +1 324installs wiki AgriciDaniel wiki initializes or connects an Obsidian vault and routes note-taking tasks to specialized sub-skills. Useful for managing knowledge bases directly from an agent. CX Codex +1 589installs wiki-update Ar9av wiki-update distills architecture decisions and project context from your current repository into an Obsidian vault. Useful when you need durable notes without manual copy-pasting. CX Codex +1 3,400installs wiki-query Ar9av wiki-query searches and synthesizes answers from a compiled Obsidian vault using graph indexing without modifying existing notes. CX Codex +1 3,600installs wiki-knowledge-complier bradduy wiki-knowledge-complier turns documents into a personal markdown knowledge base: the plugin ingests sources, builds an entity graph and answers questions from it. ★ 12repo stars wiki-mode AgriciDaniel wiki-mode configures vault filing methodologies like PARA, LYT, or Zettelkasten and suggests destinations for new Obsidian notes without writing files. CX Codex +1 344installs

From the same set15

The whole set →
research research is a Claude Code skill that searches an Obsidian vault, reads relevant notes, and follows links to answer questions about stored knowledge. CX Codex +1 ★ 102repo stars moc-update moc-update finds the Maps of Content (MOCs) in an Obsidian vault that should link to a freshly created Engineering/ note. Fires on prompts like “update MOC” or “which MOCs”. CX Codex +1 ★ 102repo stars link-audit link-audit audits Obsidian vaults for broken wikilinks and orphaned notes. Helps repair target paths or generate new links via semantic search. CX Codex +1 ★ 102repo stars knowledge This skill finds ideas repeated across project notes and drafts a shared note in Engineering/. Use it to turn recurring project knowledge into a linked concept. CX Codex +1 ★ 102repo stars journal journal — a skill for your Obsidian daily note: it reads today's entry, appends quick logs and builds weekly or end-of-day reviews from CLI sessions. CX Codex +1 ★ 102repo stars obsidian-companion obsidian-companion connects your assistant to an Obsidian vault to edit files, inspect broken wikilinks, and run queries using local RAG. CX Codex +1 ★ 102repo stars cross-linker cross-linker finds mentions of other Obsidian notes that lack wikilinks, then sorts possible links by confidence. Use it to connect notes across a chosen folder or a wider vault scope. CX Codex +1 ★ 102repo stars vault-lint vault-lint audits an Obsidian vault across five checks and returns a prioritised report with fixes you accept one at a time. CX Codex +1 ★ 102repo stars

Project sponsors

Companies that keep this analytics open