context7

Solid

Fetch up-to-date, version-specific library documentation from Context7 for accurate API references, code examples, and usage patterns. Use when working with any library or framework and you need current documentation instead of relying on training data. Trigger when the user says "context7", "/context7", "look up docs for [library]", "get documentation for [library]", or when you need to validate code against current library APIs. Also use proactively when writing code that depends on external libraries to ensure correctness.

AI & Automation 10 stars 0 forks Updated today Apache-2.0

Install

View on GitHub

Quality Score: 80/100

Stars 20%
35
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Context7 - Library Documentation Fetch live, version-specific documentation for any library or framework via the Context7 REST API. Returns authoritative docs formatted for LLM consumption. > **Naming note.** A user-level Claude Code plugin also exposes a skill called `context7:context7` (namespaced form). When the user types `/context7` without the namespace, the local skill in this file wins per Claude Code's bare-name lookup precedence (local > plugin). To force the plugin variant, type the namespaced form explicitly. Both skills do similar things; the local one uses the workspace's own CONTEXT7_API_KEY and `scripts/context7.py`, the plugin uses its own MCP-style backend. ## Prerequisites `CONTEXT7_API_KEY` should be set in the workspace `.env` file. The script auto-loads it via `python-dotenv`. ``` # In the workspace root .env file: CONTEXT7_API_KEY=ctx7sk-your-key-here ``` Get a free key at: https://context7.com/dashboard The API works without a key but with lower rate limits. ## Workflow 1. Parse the user input: first word is the library name, remainder is the query. If only a library name is given, use "documentation" as the default query. 2. Run the script: ```bash python scripts/context7.py "<library_name>" "<query>" ``` Examples: - `/context7 react hooks` -> `python scripts/context7.py "react" "hooks"` - `/context7 nextjs app router middleware` -> `python scripts/context7.py "nextjs" "app router middleware"` - `/context7 python-pptx` -> `python scripts...

Details

Author
mishahanin
Repository
mishahanin/heading-os
Created
3 weeks ago
Last Updated
today
Language
Python
License
Apache-2.0

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

context7

Retrieve up-to-date documentation for software libraries, frameworks, and components via the Context7 API. This skill should be used when looking up documentation for any programming library or framework, finding code examples for specific APIs or features, verifying correct usage of library functions, or obtaining current information about library APIs that may have changed since training.

1 Updated 3 days ago
NafisRayan
Web & Frontend Solid

context7

Fetch up-to-date library/framework/API documentation from Context7, bypassing training-cutoff limits. Use when: (1) User asks how to use/configure/install a library, framework, or SDK, (2) Code examples or API reference needed for a specific package, (3) Version-specific behavior questions (e.g., "React 19", "Next.js 15"), (4) Any npm package, GitHub repo, or framework mention (React/Vue/Next/Prisma/Tailwind/Supabase/...). Triggers: "如何实现", "怎么写", "配置", "安装", "文档", "How do I", "Show me how", "generate code", library/framework names. Differentiator: Real-time authoritative docs via Context7 API, complements grok-search (real-time news) and exa (semantic web research) — use this for library/API specifics, not general web search.

64 Updated yesterday
Dianel555
Web & Frontend Listed

find-docs

Retrieves up-to-date documentation, API references, and code examples for any developer technology. Use this skill whenever the user asks about a specific library, framework, SDK, CLI tool, or cloud service -- even for well-known ones like React, Next.js, Prisma, Express, Tailwind, Django, or Spring Boot. Your training data may not reflect recent API changes or version updates. Always use for: API syntax questions, configuration options, version migration issues, "how do I" questions mentioning a library name, debugging that involves library-specific behavior, setup instructions, and CLI tool usage. Use even when you think you know the answer -- do not rely on training data for API details, signatures, or configuration options as they are frequently outdated. Always verify against current docs. Prefer this over web search for library documentation and API details.

3 Updated 3 days ago
arthjean