Back to skills
extension
Category: Development & EngineeringNo API key required

Context7 API Documentation Fetcher

Fetch up-to-date library documentation via Context7 API. Use PROACTIVELY when: (1) Working with ANY external library (React, Next.js, Supabase, etc.) (2) User asks about library APIs, patterns, or best practices (3) Implementing features that rely on third-party packages (4) Debugging library-specific issues (5) Need current documentation beyond training data cutoff Always prefer this over guessing library APIs or using outdated knowledge.

personAuthor: am-willhubclawhub

Context7 Documentation Fetcher

Retrieve current library documentation via Context7 API.

Workflow

1. Search for the library

python3 ~/.claude/skills/context7/scripts/context7.py search "<library-name>"

Example:

python3 ~/.claude/skills/context7/scripts/context7.py search "next.js"

Returns library metadata including the id field needed for step 2.

2. Fetch documentation context

python3 ~/.claude/skills/context7/scripts/context7.py context "<library-id>" "<query>"

Example:

python3 ~/.claude/skills/context7/scripts/context7.py context "/vercel/next.js" "app router middleware"

Options:

  • --type txt|md - Output format (default: txt)
  • --tokens N - Limit response tokens

Quick Reference

| Task | Command | |------|---------| | Find React docs | search "react" | | Get React hooks info | context "/facebook/react" "useEffect cleanup" | | Find Supabase | search "supabase" | | Get Supabase auth | context "/supabase/supabase" "authentication row level security" |

When to Use

  • Before implementing any library-dependent feature
  • When unsure about current API signatures
  • For library version-specific behavior
  • To verify best practices and patterns