upstash/context7
4 skills9.4k installs228k starsGitHub
Install
npx skills add https://github.com/upstash/context7Skills in this repo
1Find Docsfind-docs is a documentation lookup skill built on the Context7 CLI. Solo builders invoke it whenever an agent must answer questions about a library, framework, SDK, CLI, or cloud service—React, Next.js, Prisma, Tailwind, Django, Spring Boot, and less common packages alike. Training data often lags renames, deprecations, and config keys; the skill insists on verifying against current docs even when the model sounds confident. The workflow is fixed: run library resolution with a contextual query, then query documentation with the returned ID. That pattern supports setup, debugging library-specific behavior, version migrations, and integration work across Build, Ship, and Operate without maintaining local doc mirrors.3kinstalls2Context7 Clicontext7-cli teaches your agent to operate the Context7 (ctx7) command-line tool so coding assistants stop guessing stale APIs. Solo builders using Claude Code, Cursor, or OpenCode invoke it when someone says ctx7 or Context7, needs current library documentation, wants to install or search skills from GitHub-style paths, or must configure Context7 MCP. The workflow splits cleanly: resolve a library ID and query docs for signatures and patterns your training data may miss; manage skills with install, search, suggest, and generate flows; and follow setup references to point the editor at MCP. Keeping ctx7 on the latest global or npx build avoids drift against registry behavior. It is an integration skill—heavy on shell commands and light on product code—best during Build when wiring agents and during Validate when you are prototyping against unfamiliar SDKs.2.9kinstalls3Context7 Mcpcontext7-mcp is an agent skill that routes documentation questions through Context7’s MCP tools so solo builders fetch current library references while coding. When someone asks how to configure Next.js middleware, write a Prisma query, or list Supabase auth methods, the workflow resolves the best Context7 library identifier for the named stack, then queries docs with the user’s full question to improve relevance. It fits the Build phase integrations subphase first, but the same pattern helps Validate prototypes and Ship fixes whenever API shapes or config flags may have changed since model cutoff. Treat it as a documentation integration layer—not a code reviewer—best paired with your own tests and version pins in package.json. Compatible with agents that expose MCP resolve-library-id and query-docs capabilities.2.1kinstalls4Documentation LookupDocumentation Lookup is the Context7-powered skill for agents that need trustworthy, up-to-date framework and API truth. When a solo builder asks how to configure middleware, write a Prisma query, or list Supabase auth methods, the skill first calls resolve-library-id with the extracted library name and full user query for relevance ranking, then selects the best match—including version-specific IDs when mentioned—and finally calls query-docs with the chosen libraryId. It activates on setup/configuration prompts, any code task that depends on third-party libraries, and explicit mentions of ecosystems like React, Vue, Svelte, Express, or Tailwind. The payoff is faster Build and Validate cycles with fewer wrong imports and deprecated patterns, without maintaining local doc mirrors. Pair it with your coding agent whenever library behavior must match what vendors ship today, not what the model last saw in training.1.4kinstalls