← ClaudeAtlas

using-the-skill-librarianlisted

Use when starting any non-trivial task, when wondering "is there a skill for this", or after finishing work that used a librarian recommendation. Applies in every agent connected to the skill-librarian MCP server.
aka-kika/the-librarian · ★ 39 · AI & Automation · score 78
Install: claude install-skill aka-kika/the-librarian
# Using the Skill Librarian ## Overview The `skill-librarian` MCP server searches your full skill collection and recommends the best fits for a stated intent. **The librarian is the access path**: only a small curated set of skills stays installed per agent; everything else is one `librarian_find` call away. Never copy skill files into agent config directories — read recommendations in place. This is the one skill worth installing everywhere. It replaces the rest. ## Quick Reference | Tool | When to call | | --- | --- | | `librarian_find(intent, k)` | Before any non-trivial task. Plain-language intent ("package a python mcp server for distribution"), not keywords. | | `librarian_brainstorm` | Open-ended ideation — "what could I build/do here" — instead of find. | | `librarian_report(skill, worked, note)` | **Always** after acting on a recommendation — used or rejected, one line why. Success rates drive curation; this is not optional bookkeeping. | | `librarian_reindex` | After adding or editing skills in the collection. | | `librarian_stats` | Collection health and usage stats. | ## Workflow 1. `librarian_find` with your intent. Do this even if locally-installed skills look sufficient — the librarian searches the whole collection; your installed list is a tiny fraction of it. 2. Weigh each recommendation's `fit`, `why`, and `why_not`. Rejecting all of them is a valid outcome. 3. Load the chosen skill from the collection — recommendations return names, not p