
Wiki Research
- 2.4k installs
- 3.1k repo stars
- Updated August 4, 2026
- ar9av/obsidian-wiki
wiki-research is an Obsidian wiki skill for autonomous multi-round web research filed into sources, concepts, entities, and synthesis pages.
About
The wiki-research skill runs a three-round research loop on a user topic, then files results into an Obsidian vault as permanent knowledge. Setup resolves OBSIDIAN_VAULT_PATH and OBSIDIAN_LINK_FORMAT, reads index.md and optional hot.md and research-config.md, and confirms ambiguous topics with the user. Round one decomposes the topic into three to five angles with WebSearch and WebFetch extraction capturing claims, concepts, entities, and contradictions. Round two fills gaps with up to five targeted searches. Round three resolves contradictions or halts when depth suffices after at most three rounds. Filing creates sources, concepts, and entities pages with provenance frontmatter plus synthesis/Research Topic.md as the master overview. Cross-linking requires concepts to cite sources while avoiding duplicates in index.md. Updates append research entries to .manifest.json, index.md, log.md, hot.md, and optional qmd update when QMD_WIKI_COLLECTION is set.
- Three-round loop: broad survey, gap fill, synthesis check.
- Files sources, concepts, entities, and master synthesis pages.
- Reads index.md first to avoid duplicating existing wiki coverage.
- Frontmatter includes provenance scores and lifecycle draft status.
- Updates manifest, index, log, hot, and optional QMD index.
Wiki Research by the numbers
- 2,422 all-time installs (skills.sh)
- +31 installs in the week ending Aug 5, 2026 (Skillselion tracking)
- Ranked #221 of 3,282 Productivity & Planning skills by installs in the Skillselion catalog
- Security screen: HIGH risk (skills.sh audit)
- Data as of Aug 5, 2026 (Skillselion catalog sync)
wiki-research capabilities & compatibility
- Capabilities
- three round websearch and webfetch research loop · structured vault filing for sources concepts ent · provenance and lifecycle frontmatter templates · cross linking and duplicate avoidance via index. · manifest, log, hot, and optional qmd refresh upd
- Works with
- obsidian
- Use cases
- research · web search · documentation
npx skills add https://github.com/ar9av/obsidian-wiki --skill wiki-researchAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 2.4k |
|---|---|
| repo stars | ★ 3.1k |
| Security audit | 1 / 3 scanners passed |
| Last updated | August 4, 2026 |
| Repository | ar9av/obsidian-wiki ↗ |
How do I deeply research a topic on the web and store structured results in my Obsidian wiki?
Run multi-round web research on a topic and file structured sources, concepts, entities, and synthesis pages into an Obsidian wiki.
Who is it for?
Obsidian wiki users wanting agent-driven research loops with citations and cross-links.
Skip if: Skip for quick single-answer lookups without vault filing or non-Obsidian note systems.
When should I use this skill?
User says wiki-research, research X, deep dive on Y, or autonomous research into vault.
What you get
A synthesis page plus linked source, concept, and entity pages with manifest and index updates.
- Structured wiki markdown pages
- Synthesized research summary
- Permanent vault knowledge files
By the numbers
- Uses a multi-round autonomous web search research loop
- Files structured results directly into Obsidian vault markdown pages
Files
Wiki Research — Autonomous Multi-Round Research
You are running an autonomous research loop on a topic, synthesizing what you find, and filing the results into the Obsidian wiki as permanent knowledge.
Before You Start
1. Resolve config — follow the Config Resolution Protocol in llm-wiki/SKILL.md (walk up CWD for .env → ~/.obsidian-wiki/config → prompt setup). This gives OBSIDIAN_VAULT_PATH and OBSIDIAN_LINK_FORMAT (default: wikilink). 2. Read $OBSIDIAN_VAULT_PATH/index.md to understand what's already in the wiki — don't re-research things the wiki covers well 3. Read $OBSIDIAN_VAULT_PATH/hot.md if it exists — it surfaces recent context 4. Check $OBSIDIAN_VAULT_PATH/references/research-config.md if it exists — it may define source preferences, domains to skip, or confidence rules for this vault
When writing internal links in generated pages, apply the link format from llm-wiki/SKILL.md (Link Format section) using the OBSIDIAN_LINK_FORMAT value.
Confirm the research topic with the user if it's ambiguous. Then proceed.
Research Configuration (optional)
If references/research-config.md exists in the vault, read it and apply any rules it defines:
- Source preferences (e.g., prefer academic sources, avoid certain domains)
- Domains to skip
- Confidence scoring adjustments
- Topic-specific constraints
If the file doesn't exist, proceed with defaults.
Round 1 — Broad Survey
Goal: Get a wide map of the topic.
1. Decompose the topic into 3-5 distinct angles (e.g., for "vector databases": what they are, when to use them, leading implementations, trade-offs, production gotchas) 2. For each angle, run 2-3 `WebSearch` queries using varied phrasing 3. For the top 2-3 results per angle, use WebFetch (or defuddle <url> if available — cleaner extraction) to get content 4. From each fetched page, extract:
- Key claims — what the source explicitly states
- Concepts — ideas, terms, frameworks introduced
- Entities — tools, people, organizations mentioned
- Contradictions — places where sources disagree with each other
Track what's covered and what's missing as you go.
Round 2 — Gap Fill
Goal: Close the holes left by Round 1.
Review what Round 1 produced:
- What questions did sources raise but not answer?
- Where do sources contradict each other?
- Which angles got thin coverage?
Run up to 5 targeted searches specifically addressing these gaps. Prefer primary sources, official documentation, and authoritative analyses over link aggregators.
Add findings to your working set. Update the contradiction list.
Round 3 — Synthesis Check
Goal: Resolve contradictions; confirm depth is sufficient.
If major contradictions remain unresolved:
- Run one final targeted pass (2-3 searches) to find authoritative resolution
- If resolution is impossible, flag the contradiction explicitly in the synthesis page
If contradictions are minor or the topic feels well-covered after Round 2, skip additional searching and proceed to filing.
Halt condition: Stop when depth is achieved or 3 rounds are complete — do not loop indefinitely.
Filing — Write Wiki Pages
Organize all findings into wiki pages across four output areas:
1. sources/ — One page per major reference
For each significant source (typically 4-8 pages total):
---
title: >-
<Source title>
category: references
tags: [<2-4 domain tags>]
sources:
- "<URL>"
source_url: "<URL>"
created: <ISO-8601 timestamp>
updated: <ISO-8601 timestamp>
summary: >-
<1-2 sentences describing what this source covers, ≤200 chars>
provenance:
extracted: 0.X
inferred: 0.X
ambiguous: 0.X
base_confidence: <0.17 + 0.5 × classify(url) for a single source>
lifecycle: draft
lifecycle_changed: <ISO date today>
---Body: title, URL, what it covers, key claims (with provenance markers), limitations.
2. concepts/ — One page per substantive concept
For each significant concept surfaced across sources:
Standard concept frontmatter + body. Link concepts to each other and to source pages.
3. entities/ — Tools, organizations, people
For each significant entity encountered (tools, libraries, companies, key authors):
Standard entity frontmatter. Link back to concepts that use the entity and sources where it appears.
4. synthesis/Research: [Topic].md — Master synthesis
The primary output: a structured synthesis of everything found.
---
title: >-
Research: <Topic>
category: synthesis
tags: [<3-5 domain tags>, research]
sources: [<list of source URLs or page paths>]
created: <ISO-8601 timestamp>
updated: <ISO-8601 timestamp>
summary: >-
Synthesis of <N>-round research on <topic>. Covers <core findings in ≤200 chars>.
provenance:
extracted: 0.X
inferred: 0.X
ambiguous: 0.X
base_confidence: <min(N_unique_sources/3,1.0)×0.5 + avg_source_quality×0.5>
lifecycle: draft
lifecycle_changed: <ISO date today>
---
# Research: <Topic>
## Overview
<2-4 sentence executive summary of what the research found>
## Key Findings
<Bulleted list of the most important claims, each with a [[source page]] citation>
## Core Concepts
<Links to concept pages created, with one-line descriptions>
## Entities & Tools
<Links to entity pages, with one-line descriptions>
## Contradictions & Open Questions
<Where sources disagree or where the research hit limits>
## Sources Consulted
<Linked list of all source pages>Cross-linking
After filing all pages:
- Every concept page should link to at least 2 source pages
- Every source page should link to the concept pages it informed
- The synthesis page should link to all concept, entity, and source pages produced
Check index.md for existing pages on the same topics — merge into existing pages rather than creating duplicates.
Update Tracking Files
`.manifest.json` — Add a research entry:
{
"type": "research",
"topic": "<topic>",
"researched_at": "TIMESTAMP",
"rounds_completed": 3,
"sources_fetched": N,
"pages_created": ["..."],
"pages_updated": ["..."]
}`index.md` — Add all new pages under their respective sections.
`log.md` — Append:
- [TIMESTAMP] WIKI_RESEARCH topic="<topic>" rounds=N sources_fetched=N pages_created=M`hot.md` — Update Recent Activity with the research topic and core finding. Update Active Threads if this is ongoing. Update updated timestamp.
Quality Checklist
- [ ] 3 rounds completed (or halted at sufficient depth)
- [ ] Synthesis page exists at
synthesis/Research: [Topic].md - [ ] Source pages written for major references
- [ ] Concept and entity pages written for significant items
- [ ] Contradictions flagged in synthesis page
- [ ] All pages cross-linked
- [ ]
index.md,log.md,hot.md,.manifest.jsonupdated
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.
${QMD_CLI:-qmd} updateIf the output says vectors are needed or embeddings may be stale, run:
${QMD_CLI:-qmd} embedVerify the collection with either:
${QMD_CLI:-qmd} ls "$QMD_WIKI_COLLECTION"or, when a specific page path is known:
${QMD_CLI:-qmd} get "qmd://$QMD_WIKI_COLLECTION/<page>.md" -l 5Record one of:
QMD refreshed: update + embed + verifiedQMD refreshed: update only + verifiedQMD skipped: QMD_WIKI_COLLECTION unsetQMD skipped: qmd CLI unavailableQMD failed: <short error summary>
Related skills
How it compares
Pick wiki-research when findings must live as linked Obsidian wiki pages; use a one-shot web search skill when no vault filing or synthesis pass is needed.
FAQ
How many research rounds run?
Up to three: broad survey, gap fill, then synthesis check or contradiction resolution.
Where does the main output live?
synthesis/Research: [Topic].md with links to sources, concepts, and entities.
Should I recreate existing wiki pages?
No. Check index.md and merge into existing pages instead of creating duplicates.
Is Wiki Research safe to install?
skills.sh reports 1 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.