context7-docs-research

Solid

Resolve the correct library and retrieve a small, relevant set of version-aware official documentation before answering a technical question.

AI & Automation 6,691 stars 1288 forks Updated yesterday NOASSERTION

Install

View on GitHub

Quality Score: 84/100

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

Skill Content

# Context7 Documentation Research 1. Identify the exact library, framework, product, and version from the request or current project. 2. Resolve the library identity before querying documentation. 3. Ask focused documentation questions and keep retrieved context bounded. 4. Prefer API references, migration guides, and official examples that match the installed version. 5. Explain the answer with relevant API names and version constraints; distinguish documentation from inference. Do not mix examples from incompatible major versions or claim undocumented behavior as guaranteed.

Details

Author
Devin-AXIS
Repository
Devin-AXIS/iPolloWork
Created
1 years ago
Last Updated
yesterday
Language
TypeScript
License
NOASSERTION

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

context7

Fetch current documentation snippets and code examples for an indexed third-party library, framework, SDK, or CLI tool from the Context7 index, using the ctx7 command line tool. Use when implementation depends on a library's present API surface, configuration options, or usage patterns, training data may be stale, and a fast indexed lookup is enough. Defer Apple platform documentation to apple-docs. Escalate to deep-docs when the conclusion must be traced to an official versioned source, when the library is not indexed, or when compatibility, deprecation, or migration has to be proven. Do not use for the project's own code, general web research, product comparisons, build-versus-buy decisions, or managing skills from the Context7 registry.

1 Updated 4 weeks ago
martonpaulo
Data & Documents Listed

documentation-lookup

Fetch current library, framework, and API documentation before answering library-specific questions. Use when a request depends on up-to-date behavior, setup, migrations, configuration, or code examples for a named library or framework.

0 Updated yesterday
espensev
Code & Development Listed

context7-context7-docs

Fetch up-to-date documentation and code examples for any library, framework, SDK, CLI tool, or cloud service. Use whenever the user asks about a specific library — even well-known ones like React, Next.js, Prisma, Express, Tailwind, Django, or Spring Boot — because 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 — they are frequently out of date. Prefer this over web search for library documentation.

2 Updated 4 days ago
KornLabs