wiki-search

Searches an Obsidian wiki vault with hybrid keyword and semantic retrieval returning citation-ready paths and lines.

Updated Jul 16, 2026
One-click install
npx skills add https://github.com/ehartye/wiki-master --skill wiki-search-ehartye
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: wiki-search
Source: https://github.com/ehartye/wiki-master/tree/main/skills/wiki-search
Command: npx skills add https://github.com/ehartye/wiki-master --skill wiki-search-ehartye

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Finding the right page or passage in a large Obsidian wiki vault is slow when keyword search misses semantically related content and raw clipped evidence sits outside the normal index. This Skill performs read-only, tiered retrieval over the vault and returns exact path:line matches you can cite directly. ## Core Features & Use Cases - Hybrid retrieval: Combines Obsidian keyword lookup with an Ollama-backed chunk-level semantic index fused via Reciprocal Rank Fusion, with a stderr status line disclosing any degraded channel. - Raw evidence search: The --include-raw flag searches immutable clipped sources in raw/ alongside the synthesized wiki/ pages in one call. - Evidence resolution: Pipe results into resolve-evidence.mjs to jump from a synthesized wiki hit to the raw clipping it cites, with explicit unreachable and declared-no-provenance reporting. - Use Case: You need to locate where a specific claim lives in a 1,800-page research vault. Run the search with your terms, read the matched line, then pipe the hit to resolve-evidence to inspect the original clipped source before quoting it. ## Quick Start Ask the agent to search the wiki for your terms, for example: find pages about embedding index freshness and show the matching passages with their raw sources.

Frequently Asked Questions about wiki-search

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I search an Obsidian vault semantically?▼

Run the search.mjs helper with your terms; it fuses Obsidian keyword results with a chunk-level semantic index built from Ollama embeddings via Reciprocal Rank Fusion. Build the index first with index-embed.mjs and ensure Ollama is running with an embedding model pulled.

How do I search raw clipped sources alongside wiki pages?▼

Pass the --include-raw flag to search.mjs to query both the synthesized wiki/ pages and the immutable raw/ clippings in one call. Raw hits appear after the ranked wiki results, identified by their raw/ path prefix, with a stderr line disclosing the hit count.

Why does wiki search report lexical-only mode?▼

Lexical-only mode means the semantic channel contributed nothing, usually because Ollama is not running, the embedding model is not pulled, or the index was never built. Run search.mjs --health for the full report or --setup for exact remediation commands.

Can I trace a wiki page back to its original source clipping?▼

Yes, pipe search output into resolve-evidence.mjs, which follows the page's sources frontmatter to the raw/ clipping. Pages without a reachable citation trail are reported as unreachable, and pages with declared empty provenance are reported distinctly.

Does wiki-search modify the vault or rebuild the index?▼

No, this skill is strictly read-only: it never writes pages, refreshes the index, or creates log entries. Index refreshes happen through op-commit after bracketed operations, and synthesized answers belong to the wiki-query skill instead.