docs-seeker
Fetch up-to-date documentation for any library, framework, API, or service into context. Use when the user wants to look up API references, check function signatures or required fields, find feature-specific docs, or verify how an external tool actually works. Triggers for queries about third-party libraries like Stripe, SQLAlchemy, Tailwind, FastAPI, shadcn, Drizzle, Hono, Better Auth — any time the answer lives in official docs rather than in the project codebase. Use this instead of guessing from trained knowledge, which is stale.
npx skills add majiayu000/claude-skill-registry --skill docs-seeker-avibebuilder-claude-prime --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
## Why fetch instead of recall Trained knowledge rots. Library APIs rename fields, deprecate hooks, restructure auth flows, and change defaults between minor versions. Answering from memory is how you get confidently wrong code. Replace memory with retrieval — cheaply, from sources designed for AI consumption. ## The source hierarchy (and why) Prefer sources in this order. The ranking is about *signal per token*, not just availability. 1. **`llms.txt` on the official docs site** — hand-curated by the project, AI-optimized, token-dense, always current. This is the ideal source when it exists. Try `{official-docs-url}/llms.txt` first for any library with a docs site; many projects ship one even if they don't advertise it. If `llms.txt` is just an index of links, follow the most relevant ones. `llms-full.txt` exists on some sites and contains the full corpus — only reach for it when the user explicitly wants comprehensive docs, since it's large. 2. **Context7** — a mirror that ingests GitHub repos and exposes them at `https://context7.com/{org}/{repo}/llms.txt`, with optional `?topic={keyword}` filtering. Use this when the project has no official `llms.txt`, or when you want to scope
- Why fetch instead of recall
- The source hierarchy (and why)
- Topic scoping
- Reading the docs you find
- Version awareness
- Gotchas
- Constraints
What does the docs-seeker skill do?
Fetch up-to-date documentation for any library, framework, API, or service into context. Use when the user wants to look up API references, check function signatures or required fields, find feature-specific docs, or verify how an external tool actually works. Triggers for queries about third-party libraries like Stripe, SQLAlchemy, Tailwind, FastAPI, shadcn, Drizzle, Hono, Better Auth — any time the answer lives in official docs rather than in the project codebase. Use this instead of guessing from trained knowledge, which is stale.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill docs-seeker-avibebuilder-claude-prime --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.