lookuplisted

Look up current library documentation, API references, and code examples via Context7 (ctx7 CLI or the Context7 MCP server — same backend). Use when: 'look up the docs for X', 'what's the API for X', 'how do I configure X', 'latest docs for X', 'check context7 for X', 'how do I migrate to X v2', or whenever a question names a library, framework, SDK, CLI tool, or cloud service — including API syntax, configuration, setup, and version-migration questions. Actions: lookup <library> <query> (default) | update (CLI upgrade + upstream drift check). For CLI/MCP setup, auth, and Windows gotchas, run /context7:setup.
melodic-software/claude-code-plugins · ★ 13 · API & Backend · score 73

Install: claude install-skill melodic-software/claude-code-plugins

## Pre-computed context Installed CLI version: !`ctx7 --version 2>/dev/null || echo "not installed (run: npm install -g ctx7@latest)"` MCP availability: check your own tool list — if `mcp__context7__resolve-library-id` / `mcp__context7__query-docs` are present, the MCP path is configured. ## Purpose A primary source of up-to-date library documentation. Two equivalent interfaces: CLI (`ctx7`) via npm, and the Context7 HTTP MCP server (`mcp__context7__*`) when the consuming project has it configured. Both read the same backend. Pick by workflow (see [When to use CLI vs MCP](#when-to-use-cli-vs-mcp)). **Philosophy**: training data is stale by the time you use it. Library APIs, framework defaults, best practices change. Before claiming how a library works, verify against Context7 — even for libraries you "know." ## Actions | Action | When | Loads | |---|---|---| | `lookup <library> <query>` (default) | User asks about a library | [context/lookup.md](context/lookup.md) | | `update` | Drift check + CLI upgrade + upstream skill changes | [context/update.md](context/update.md) | If the argument is bare (no action keyword), treat as `lookup`. First-time setup — CLI install, `CONTEXT7_API_KEY` auth, optional MCP server wiring, and the Windows Git Bash gotcha — lives in its own skill: run `/context7:setup`. ## Lookup (happy path) Two-step: resolve library name → fetch docs with resolved ID. ```bash # Step 1: name → Context7 library ID ctx7 library "<name>" "<question>" # Ste