whiteboard-search

Solid

When the user asks you to find something in their own notes or in a shared library, search by following the correct ladder from opsidian_search to knowledge_search and summarize the results naturally.

AI & Automation 8 stars 0 forks Updated 2 days ago Apache-2.0

Install

View on GitHub

Quality Score: 84/100

Stars 20%
32
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Whiteboard Search — Searching the user's notes / library Use this skill when the user asks you to find something in their own notes or in a shared library. ## First, distinguish the two kinds of stores - **User Opsidian** (personal vault) — the raw notes the user writes and captures every day. Accessed via the `opsidian_*` tools. Categories: `inbox / daily / topics / projects / insights`. - **Curated Knowledge** (library) — the organized subset the user has explicitly shared via "Share with VTuber > Library". Accessed via the `knowledge_*` tools. **This is the most trustworthy source you have — because the user hand-picked and sent it.** ## Search Ladder If the user's request is ambiguous, try **both** and merge the results: 1. **`opsidian_search(query, max_results=5)`** — keyword search. The fastest, and best at capturing the user's raw intent. 2. If you get 0–1 results or the scores are low → use **`knowledge_search(query, max_results=5)`** for a semantic search on the curated side. 3. For the 1–3 most likely notes, confirm the contents with **`knowledge_read(filename)`** or **`opsidian_read(filename)`**. 4. Don't dump the body as-is — **summarize it in 2–3 sentences** for the user. Include only 1–2 lines of key quotes if needed. ## When the user specifies a category or tag - Category specified ("among my daily notes…") → narrow with `opsidian_browse(category="daily")`, then search within it. - Tag specified ("the ones tagged #API…") → `opsidian_browse(tag="API")`...

Details

Author
CocoRoF
Repository
CocoRoF/Geny
Created
5 months ago
Last Updated
2 days ago
Language
Python
License
Apache-2.0

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

shelf-find

Search the user's saved tool library before recommending or choosing any tool, library, service, vendor, or technique. USE THIS AGGRESSIVELY — the user rarely asks for it by name. Trigger on "what should I use for", "do I have anything saved about", "I need a tool that", "how do I approach", "any recommendations for", "is there something that does", "what's good for", "which library", "how should I build" — AND on any moment where the user is evaluating, comparing, or picking a tool/service/approach for a task, even with zero mention of saved links, notes, or a library. If the user is about to pick something, check here first. Under-triggering is the main failure mode; when in doubt, run it.

0 Updated 2 days ago
Ranveersingh1113
AI & Automation Solid

search

General vault retrieval — answers both "what" and "why" questions across MEMORY.md, memory/, session logs, project trackers, and vault notes. Uses the search tools (lex+vec+hyde) with grep fallback.

20 Updated 4 days ago
onebrain-ai
AI & Automation Solid

vault-search

Use proactively mid-task, on your own initiative, whenever past work might already cover the current step — before re-fixing a recurring or previously-seen bug, touching an unfamiliar subsystem, or making a risky/hard-to-reverse change — not only when asked. Also when the user wants to recall prior context: 'what did we decide about X', 'find everything about Y', 'что мы решили про', 'что мы знаем', 'как мы делали', 'когда последний раз', 'такое уже было', 'вспомни', 'напомни', 'посмотри в памяти', 'найди в памяти', 'как решали', 'где ещё может быть', 'что было с', or similar. Synthesizes across notes with source citations; prefer over generic memory tools when an Obsidian vault is available.

6 Updated today
jojoprison