looking-up-docs — Claude Code skill: what it does, how to install
looking-up-docs retrieves version-specific library documentation and live API examples through Context7 inside your coding agent.
MIT 106 installs ★ 17 updated 2026-10-14
npx skills add julianobarbosa/claude-code-skills --skill looking-up-docs -a claude-codeWhat looking-up-docs does
This skill queries technical references through Context7. The agent first resolves the target package using mcp__context7__resolve-library-id, then calls mcp__context7__get-library-docs with the resolved ID and a topic parameter. Two modes are supported: code for API signatures and practical snippets, and info for architectural explanations.
Omitting the version number causes Context7 to return mixed hits across all releases, meaning a Next.js 14 query can pull Next.js 12 snippets. Context7 MCP integration is required, and exceeding daily rate limits on the free tier locks the API key until midnight UTC.
What it helps with
- fetch live API code examples directly from official documentation
- avoid hallucinated function arguments and deprecated framework patterns
- read architecture tutorials in info mode without opening a browser
- inspect version-specific package documentation during coding sessions
Example prompts for the agent
- Look up Next.js 14 middleware examples using Context7
- Check React hooks documentation via Context7 in code mode
- Find Go net/http server setup guides using Context7
How to install looking-up-docs
1Skills CLI (Vercel)
npx skills add julianobarbosa/claude-code-skills --skill looking-up-docs -a claude-code2Manually: put the files in place
~/.claude/skills/looking-up-docs/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/looking-up-docs/
1Skills CLI (Vercel)
npx skills add julianobarbosa/claude-code-skills --skill looking-up-docs -a codex2Manually: put the files in place
.agents/skills/looking-up-docs/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add julianobarbosa/claude-code-skills --skill looking-up-docs -a cursor2Manually: put the files in place
.cursor/skills/looking-up-docs/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install julianobarbosa/claude-code-skills skills/looking-up-docs2Manually: put the files in place
.github/skills/looking-up-docs/SKILL.md1Skills CLI (Vercel)
npx skills add julianobarbosa/claude-code-skills --skill looking-up-docs -a gemini-cli2Platform CLI
gemini skills install https://github.com/julianobarbosa/claude-code-skills --path skills/looking-up-docsManually: put the files in place
.devin/skills/looking-up-docs/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add julianobarbosa/claude-code-skills --skill looking-up-docs -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about looking-up-docs
How to install looking-up-docs in Claude Code?
Run npx skills add julianobarbosa/claude-code-skills --skill looking-up-docs -a claude-code in your terminal.
What does looking-up-docs do?
It equips the agent to search library documentation and API references via Context7, fetching exact code examples into context.
What happens if a query omits the library version?
Context7 searches across every indexed release, which may return legacy code samples instead of the syntax for your current stack.
Source text
SKILL.md · MIT
--- name: looking-up-docs description: Look up library documentation using Context7. Use when needing API reference, library docs, framework documentation, or technical documentation lookup. Provides up-to-date, version-specific docs and code examples. allowed-tools: Read, Grep, Glob, mcp__context7__resolve-library-id, mcp__context7__get-library-docs --- # Documentation Lookup with Context7 Context7 provides up-to-date, version-specific documentation and code examples directly from source libraries. ## Why Context7 - **Current APIs**: No hallucinated or outdated patterns - **Version-specific**: Gets docs for exact library versions - **Code examples**: Real, working code from actual documentation ## Workflow 1. **Resolve library ID**: `mcp__context7__resolve-library-id` with `libraryName` 2. **Get documentation**: `mcp__context7__get-library-docs` with `context7CompatibleLibraryID` and `topic` ## Modes | Mode | Use For | | ------ | ------------------------------------------ | | `code` | API references, code examples (default) | | `info` | Conceptual guides, architecture, tutorials | ## Examples ``` # React hooks resolve-library-id: "react" get-library-docs: context7CompatibleLibraryID="/facebook/react", topic="hooks", mode="code" # Next.js middleware resolve-library-id: "next.js" get-library-docs: context7CompatibleLibraryID="/vercel/next.js", topic="middleware" # Go net/http resolve-library-id: "go net/http" get-library-docs: context7CompatibleLibraryID="/golang/go", topic="http server" # Kubernetes API resolve-library-id: "kubernetes" get-library-docs: context7CompatibleLibraryID="/kubernetes/kubernetes", topic="deployment" ``` ## Tips - Use `topic` parameter to narrow results to specific features - Try `mode="info"` for architectural questions - Paginate with `page=2`, `page=3` if initial results insufficient --- ## Gotchas - **Context7 query without version scoping returns hits across versions** — Next.js 14 question can answer with Next.js 12 code. Always include the version. - **Library aliases (e.g., `react` vs `@types/react`) may resolve to different libraries** — use the full Context7 ID, not the npm name. - **Stale cache**: Context7 may have indexed a library version that's been yanked from npm — check upstream before trusting. - **Rate limits per API key per day** — bursting on the free tier locks the key out until midnight UTC. - **No multi-version diff**: Context7 doesn't surface what changed between versions; for migrations, dual-query and compare manually.
© julianobarbosa · MIT · julianobarbosa/claude-code-skills