wiki-ingest
Use when the user wants to ingest external sources into the vault — PDFs, markdown files, transcripts, Readwise exports, or any document.
Skill by thoreinstein
Install
Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.
npx agentmarket install skill/thoreinstein-wiki-ingest-c54424
Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.
Get the weekly diff
The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.
About
Use cases: documents
Reviews
Write a reviewNo reviews yet. Installed it? Reviews come from verified installers only. How reviews work
Permissions
What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.
- Tools
- No tools found
- Secrets
- None asked for
- Install scripts
- None found
Network hosts it talks to 1
codeload.github.com· found in install command
Files it touches
~/.claude/skills/wiki-ingest
What's inside
- Skill 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".
- License
- ISC
- Instructions
- 127 lines in SKILL.md · view on GitHub
Files (1)
- SKILL.md
SKILL.md (first lines)
# 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 sourcesFrom thoreinstein/gemini-obsidian, ISC.
More from thoreinstein/gemini-obsidian
- 0.776score
journal
thoreinstein
Use when the user wants to work with their daily note — view today's entry, add a log, do a daily review, or capture quick thoughts.
SkillAFreshness: A★ 102Claude Code +9 - 0.649score
vault
thoreinstein
Use when the user wants to set, change, or create their Obsidian vault, or says "vault", "set vault", "change vault", "create vault", or "new vault".
SkillAFreshness: A★ 102Claude Code +9 - 0.597score
moc-update
thoreinstein
Use after creating a new Engineering/ note to suggest which Maps of Content (MOCs) it belongs in.
SkillDFreshness: D★ 102Claude Code +9 - 0.597score
research
thoreinstein
Use when the user asks a question about their vault, wants to explore a topic across notes, or says "research", "find out", "what do I know about", or…
SkillDFreshness: D★ 102Claude Code +9 - 0.597score
vault-lint
thoreinstein
Use when the user wants a health audit of the vault — stale content, provenance drift, frontmatter compliance, or MOC coverage gaps.
SkillDFreshness: D★ 102Claude Code +9 - 0.494score
compound
thoreinstein
Use when the user wants to promote cross-project knowledge to the global Engineering/ folder, or says "promote knowledge", "compound notes", "knowledge…
SkillDFreshness: D★ 102Claude Code +9 - 0.494score
cross-linker
thoreinstein
Use when the user wants to find and insert missing wikilinks across vault notes.
SkillDFreshness: D★ 102Claude Code +9 - 0.494score
knowledge
thoreinstein
Use when the user wants to promote cross-project knowledge to the global Engineering/ folder, or says "promote knowledge", "compound notes", "knowledge…
SkillDFreshness: D★ 102Claude Code +9 - 0.494score
link-audit
thoreinstein
Use when the user wants to audit vault link health, find broken wikilinks, orphaned notes, or semantic clusters.
SkillDFreshness: D★ 102Claude Code +9 - 0.494score
index
thoreinstein
Use when the user wants to index their vault for semantic search, rebuild the RAG index, or says "index", "reindex", or "rebuild index".
SkillDFreshness: D★ 102Claude Code +9 - 0.494score
links
thoreinstein
Use when the user wants to explore connections between notes, see what links to or from a note, or says "links", "backlinks", "connections", or "graph".
SkillDFreshness: D★ 102Claude Code +9 - 0.493score
search
thoreinstein
Use when the user wants to find notes by keyword or filename, or says "search", "find notes", or "look for".
SkillDFreshness: D★ 102Claude Code +9
Signals
- Stars
- 102
- Forks
- 11
- Open issues
- 0
- Last commit (this folder)
- Apr 11, 2026 (6 months ago)
From GitHub (fetched Oct 24, 2026).
Details
- License
- ISC
- Repository
- github.com/thoreinstein/gemini-obsidian
- First seen
- Oct 24, 2026
- Last checked
- Oct 24, 2026
- Source
- GitHubgithub-graphql
Same skill elsewhere
Copies of this SKILL.md published by others; search shows only one of them.
More from thoreinstein
- 0.776score
journal
thoreinstein
Use when the user wants to work with their daily note — view today's entry, add a log, do a daily review, or capture quick thoughts.
SkillAFreshness: A★ 102Claude Code +9 - 0.649score
vault
thoreinstein
Use when the user wants to set, change, or create their Obsidian vault, or says "vault", "set vault", "change vault", "create vault", or "new vault".
SkillAFreshness: A★ 102Claude Code +9 - 0.597score
vault-lint
thoreinstein
Use when the user wants a health audit of the vault — stale content, provenance drift, frontmatter compliance, or MOC coverage gaps.
SkillDFreshness: D★ 102Claude Code +9 - 0.597score
moc-update
thoreinstein
Use after creating a new Engineering/ note to suggest which Maps of Content (MOCs) it belongs in.
SkillDFreshness: D★ 102Claude Code +9 - 0.597score
research
thoreinstein
Use when the user asks a question about their vault, wants to explore a topic across notes, or says "research", "find out", "what do I know about", or…
SkillDFreshness: D★ 102Claude Code +9 - 0.494score
knowledge
thoreinstein
Use when the user wants to promote cross-project knowledge to the global Engineering/ folder, or says "promote knowledge", "compound notes", "knowledge…
SkillDFreshness: D★ 102Claude Code +9
Cite this page
wiki-ingest skill. Agent Mart. https://agentmart.dev/skills/thoreinstein-wiki-ingest-c54424 (last updated 2026-10-24)