Skip to main content
Frontend Developmentdvcrn

context7

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

Stars
15
Source
dvcrn/openclaw-skills-marketplace
Updated
2026-05-29
Slug
dvcrn--openclaw-skills-marketplace--context7
View on GitHubRaw SKILL.md

// install — copy + paste into any project

mkdir -p .claude/skills && curl -fsSL https://raw.githubusercontent.com/dvcrn/openclaw-skills-marketplace/HEAD/plugins/am-will--context7-api/skills/context7/SKILL.md -o .claude/skills/context7.md

Drops the SKILL.md into .claude/skills/context7.md. Works with Claude Code, Cursor, and any agent that loads SKILL.md files from .claude/skills/.

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