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
npx skills add thoreinstein/gemini-obsidian --skill wiki-ingest -a claude-codeWhat 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-code2Manually: put the files in place
~/.claude/skills/wiki-ingest/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/wiki-ingest/
1Skills CLI (Vercel)
npx skills add thoreinstein/gemini-obsidian --skill wiki-ingest -a codex2Manually: put the files in place
.agents/skills/wiki-ingest/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add thoreinstein/gemini-obsidian --skill wiki-ingest -a cursor2Manually: put the files in place
.cursor/skills/wiki-ingest/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install thoreinstein/gemini-obsidian skills/wiki-ingest2Manually: put the files in place
.github/skills/wiki-ingest/SKILL.md1Skills CLI (Vercel)
npx skills add thoreinstein/gemini-obsidian --skill wiki-ingest -a gemini-cli2Platform CLI
gemini skills install https://github.com/thoreinstein/gemini-obsidian --path skills/wiki-ingestManually: put the files in place
.devin/skills/wiki-ingest/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
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.