context7

# Context7 Fetch current library/framework/API documentation from the Context7 API, so answers cite authoritative docs instead of relying on outdated training data. This skill uses the co-located Node CLI in `context7-api.cjs`; no MCP dependency is required. ## Architecture | Piece | Role | Recommended Use | |-------|------|-----------------| | **context7** (this file) | Intent detection, library selection, answer integration | **Default path** | | [context7-fetcher](context7-fetcher.md) | Optional low-context wrapper around the same CLI | Use only if your runtime truly supports isolated workers/subtasks | The canonical execution path is to run the co-located CLI directly. Do **not** require a `Task`/`Bash`-specific subtask mechanism, and do **not** hardcode repo-relative paths like `skills/context7/context7-api.cjs` — that breaks when the skill is installed globally outside the source repo. ### Call Flow ``` User Query → context7 (detect trigger + extract library) ↓ shell / worker → node <context7-skill-dir>/context7-api.cjs search <library> <query> → JSON libraries[] (+ raw results[]) context7 (select best match: name / trustScore / version) ↓ shell / worker → node <context7-skill-dir>/context7-api.cjs context <libraryId> <query> → JSON results[] (+ raw codeSnippets[] / infoSnippets[]) context7 (integrate relevant snippets into answer) ``` ## Implementation Layout - `context7-api.cjs` - Node CLI entrypoint (H...