mcpField
L
looking-up-docs

looking-up-docs

github.com/julianobarbosaDevelopment14105 installsUpdated 2d ago
Repository

About looking-up-docs

looking-up-docs is a skill that uses Context7 to retrieve current, version-specific library documentation and code examples. It is for developers seeking API references or conceptual guidance grounded in source documentation.

Key features

  1. 01Resolves library names to Context7 IDs
  2. 02Retrieves documentation by topic
  3. 03Supports code and info modes
  4. 04Allows pagination for additional results
  5. 05Highlights version and alias pitfalls

Use cases

  1. 01Find API examples for a specific library version
  2. 02Look up conceptual guides for a library
  3. 03Narrow documentation results to a topic
  4. 04Compare documentation retrieved for separate versions

MCP support

The skill uses the Context7 MCP tools `mcp__context7__resolve-library-id` and `mcp__context7__get-library-docs` to identify libraries and fetch documentation.

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/julianobarbosa/claude-code-skills --skill looking-up-docs

After installing, type/looking-up-docsin Claude Code to confirm it loaded.

Details

From the project README

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

ModeUse For
codeAPI references, code examples (default)
infoConceptual 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.

Comments

Markdown supported