shelf-findlisted

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.
Ranveersingh1113/shelf-skills · ★ 0 · AI & Automation · score 75

Install: claude install-skill Ranveersingh1113/shelf-skills

# shelf-find Read-only search of the user's saved tool library. **This skill must never write anything.** No notes, no index, no inbox, no config file. Read only. ## Step 0 — find the library Read `~/.tool-library-path` (in the user's home directory). It holds one line: the library folder. Call it `<LIB>`. Notes live in `<LIB>/notes/`. **If the file is missing**, the library was never set up. Say so, and tell the user to run `shelf-save` to set it up. Do not create it here and do not guess a path. ## Run 1. **Restate the need in one line** — including constraints you inferred from the surrounding conversation, not just the literal question. Stage, budget, existing stack, language, self-host vs SaaS. Say what you inferred so the user can correct a wrong assumption before it skews the ranking. 2. **Map to 2–3 likely categories** from: `dev-tool` `ai-agent` `marketing` `design` `data` `fundraising` `ops` `research` `reading` `other`. This is a starting set the user is free to edit; if they change it, the same list in `shelf-save` must match, or notes land under a category recall never looks for. The list guides the search — it doesn't limit what you may find. 3. **Search the notes by content.** Plain text search, not vectors — the corpus is a few hundred small files. Use whatever search your harness gives you (`Grep` in Claude Code, `grep -r` in a shell, file search elsewhere). - by category: lines matching `^category: dev-tool` - by tag: