Agent skill

Library Docs Lookup with Context7

by oss-apps in oss-apps/split-pro

Looks up current documentation and code examples for any library, framework, SDK or CLI with the Context7 ctx7 command instead of relying on training data.

MITAuto-check passedDevelopment

Install Library Docs Lookup with Context7

skills CLI
$ npx skills add oss-apps/split-pro --skill find-docs -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install oss-apps/split-pro find-docs --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/oss-apps/split-pro.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.opencode/skills/find-docs .claude/skills/find-docs && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
find-docs
GitHub stars
1.5k
Used in
3 other repos
Token cost
~1.6k tokens
SKILL.md length
620 words
Files
1
Skills in repo
1
Repo updated
First seen
Licence
MIT

At a glance

Looks up current documentation and code examples for any library, framework, SDK or CLI with the Context7 ctx7 command instead of relying on training data.

  • Works in 2 steps: Resolve a Library → Query Documentation
  • Answering API syntax or configuration questions for a specific library
  • SKILL.md covers Workflow, Step 1: Resolve a Library, Step 2: Query Documentation and Authentication, plus 2 more sections
  • Calls npm and npx; needs CONTEXT7_API_KEY

What it does

The skill uses the ctx7 CLI in two steps: resolve a library name and a query into a Context7 library ID, then query the docs with that ID. Resolving is mandatory unless you already give an ID in the org/project form. Results show the ID, name, description, snippet count, source reputation, a benchmark score and versions, and a selection process prefers exact names, relevant descriptions, richer coverage and higher reputation.

A query is always required and shapes ranking; it must not contain secrets, credentials, personal data or proprietary code. Commands run at most three times per question, after which the best result so far is used. The skill is meant to be used whenever a specific library, framework, SDK or cloud service comes up, even a well-known one, since training data may miss recent API changes, and it is preferred over web search for library docs.

When your agent uses it

  • Answering API syntax or configuration questions for a specific library
  • Checking the current way to do a task after a library version upgrade
  • Finding setup instructions or CLI usage for a framework or SDK
  • Debugging behavior that depends on a particular library

Example prompts

  • “How do I define one-to-many relations with cascade delete in Prisma? Check the current docs.”
  • “Look up how to set up app router middleware in the current Next.js docs.”
  • “What changed in the latest Tailwind configuration options?”

Requirements

  • Node.js with npm to run ctx7
  • Network access to Context7

Workflow steps

2 steps, taken from the step headings in SKILL.md.

  1. Resolve a Library
  2. Query Documentation

What it can do on your machine

Read from SKILL.md and the folder at commit f336ed2. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • npm
    • npx

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use npm and npx, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • CONTEXT7_API_KEY

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Library Docs Lookup with Context7 loads about 1.6k tokens when it runs. Until then it costs about 222 tokens; SKILL.md has 620 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~222
When it runs · the whole SKILL.md, loaded when a task matches
~1.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from oss-apps/split-pro at commit f336ed2, republished under its MIT licence (© oss-apps). 620 words, ~1,631 tokens.

Download SKILL.mdSave it as .claude/skills/find-docs/SKILL.md (or your agent's skills folder).
name
find-docs
description
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.

Documentation Lookup

Retrieve current documentation and code examples for any library using the Context7 CLI.

Make sure the CLI is up to date before running commands:

bash
npm install -g ctx7@latest

Or run directly without installing:

bash
npx ctx7@latest <command>

Workflow

Two-step process: resolve the library name to an ID, then query docs with that ID.

bash
# Step 1: Resolve library ID
ctx7 library <name> <query>

# Step 2: Query documentation
ctx7 docs <libraryId> <query>

You MUST call ctx7 library first to obtain a valid library ID UNLESS the user explicitly provides a library ID in the format /org/project or /org/project/version.

IMPORTANT: Do not run these commands more than 3 times per question. If you cannot find what you need after 3 attempts, use the best result you have.

Step 1: Resolve a Library

Resolves a package/product name to a Context7-compatible library ID and returns matching libraries.

bash
ctx7 library react "How to clean up useEffect with async operations"
ctx7 library nextjs "How to set up app router with middleware"
ctx7 library prisma "How to define one-to-many relations with cascade delete"

Always pass a query argument — it is required and directly affects result ranking. Use the user's intent to form the query, which helps disambiguate when multiple libraries share a similar name. Do not include any sensitive or confidential information such as API keys, passwords, credentials, personal data, or proprietary code in your query.

Result fields

Each result includes:

  • Library ID — Context7-compatible identifier (format: /org/project)
  • Name — Library or package name
  • Description — Short summary
  • Code Snippets — Number of available code examples
  • Source Reputation — Authority indicator (High, Medium, Low, or Unknown)
  • Benchmark Score — Quality indicator (100 is the highest score)
  • Versions — List of versions if available. Use one of those versions if the user provides a version in their query. The format is /org/project/version.
Selection process
  1. Analyze the query to understand what library/package the user is looking for
  2. Select the most relevant match based on:
    • Name similarity to the query (exact matches prioritized)
    • Description relevance to the query's intent
    • Documentation coverage (prioritize libraries with higher Code Snippet counts)
    • Source reputation (consider libraries with High or Medium reputation more authoritative)
    • Benchmark score (higher is better, 100 is the maximum)
  3. If multiple good matches exist, acknowledge this but proceed with the most relevant one
  4. If no good matches exist, clearly state this and suggest query refinements
  5. For ambiguous queries, request clarification before proceeding with a best-guess match
Version-specific IDs

If the user mentions a specific version, use a version-specific library ID:

bash
# General (latest indexed)
ctx7 docs /vercel/next.js "How to set up app router"

# Version-specific
ctx7 docs /vercel/next.js/v14.3.0-canary.87 "How to set up app router"

The available versions are listed in the ctx7 library output. Use the closest match to what the user specified.

Show full SKILL.md (241 more words)Show less

Step 2: Query Documentation

Retrieves up-to-date documentation and code examples for the resolved library.

bash
ctx7 docs /facebook/react "How to clean up useEffect with async operations"
ctx7 docs /vercel/next.js "How to add authentication middleware to app router"
ctx7 docs /prisma/prisma "How to define one-to-many relations with cascade delete"
Writing good queries

The query directly affects the quality of results. Be specific and include relevant details. Do not include any sensitive or confidential information such as API keys, passwords, credentials, personal data, or proprietary code in your query.

QualityExample
Good"How to set up authentication with JWT in Express.js"
Good"React useEffect cleanup function with async operations"
Bad"auth"
Bad"hooks"

Use the user's full question as the query when possible, vague one-word queries return generic results.

The output contains two types of content: code snippets (titled, with language-tagged blocks) and info snippets (prose explanations with breadcrumb context).

Authentication

Works without authentication. For higher rate limits:

bash
# Option A: environment variable
export CONTEXT7_API_KEY=your_key

# Option B: OAuth login
ctx7 login

Error Handling

If a command fails with a quota error ("Monthly quota reached" or "quota exceeded"):

  1. Inform the user their Context7 quota is exhausted
  2. Suggest they authenticate for higher limits: ctx7 login
  3. If they cannot or choose not to authenticate, answer from training knowledge and clearly note it may be outdated

Do not silently fall back to training data — always tell the user why Context7 was not used.

Common Mistakes

  • Library IDs require a / prefix — /facebook/react not facebook/react
  • Always run ctx7 library first — ctx7 docs react "hooks" will fail without a valid ID
  • Use descriptive queries, not single words — "React useEffect cleanup function" not "hooks"
  • Do not include sensitive information (API keys, passwords, credentials) in queries

© oss-apps, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .opencode/skills/find-docs of oss-apps/split-pro.

Open the folder on GitHubat commit f336ed2

Used in 3 other repositories

We found 3 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 3 other GitHub owners. This page covers the copy in oss-apps/split-pro, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Library Docs Lookup with Context7 next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Library Docs Lookup with Context7 compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Library Docs Lookup with Context7 this skilloss-apps/split-pro1.5k3 repos~1.6kAutomated safety check: PassMIT
Tavily Search API Integrationandrewyng/context-hub14k—~1.1kAutomated safety check: PassMIT
Browser SearchJohell1NS/browser-search528—~2.5kAutomated safety check: PassMIT
Sponsor Findergithub/awesome-copilot40k2 repos~3kAutomated safety check: PassMIT
Nx Run Tasksnomcopter/react-mosaic4.8k7 repos~613Automated safety check: PassCustom licence
Get API Docs with chubandrewyng/context-hub14k2 repos~775Automated safety check: PassMIT

Similar skills

  • Tavily Search API Integration

    andrewyng/context-hub

    Guides building Tavily integrations for web search, URL extraction, site crawling and AI-assisted research in Python or JavaScript agent and RAG projects.

    14k GitHub stars~1.1k tokensUpdated 4 mo ago
    AI & LLM EngineeringAuto-check passed
  • Browser Search

    Johell1NS/browser-search

    Multi-engine web search (SearXNG) + browsing/scraping (Camofox, CloakBrowser).

    528 GitHub stars~2.5k tokensUpdated 1 mo ago
    Productivity & AutomationAuto-check passed
  • Sponsor Finder

    github/awesome-copilot

    Official

    Find which of a GitHub repository's dependencies are sponsorable via GitHub Sponsors.

    40k GitHub starsUsed in 2 repos~3k tokens
    Productivity & AutomationAuto-check passed
  • Nx Run Tasks

    nomcopter/react-mosaic

    Helps with running tasks in an Nx workspace. An agent skill from nomcopter/react-mosaic.

    4.8k GitHub starsUsed in 7 repos~613 tokens
    DevelopmentAuto-check passed
  • Get API Docs with chub

    andrewyng/context-hub

    Fetches current documentation for third-party APIs and SDKs with the chub CLI before the agent writes code against them, instead of relying on remembered API shapes.

    14k GitHub starsUsed in 2 repos~775 tokens
    DevelopmentAuto-check passed
  • Moves a package from another TryGhost repository into Ghost as an internal workspace package while keeping its Git history, with checkpoints for the steps that need an administrator.

    55k GitHub stars~3.8k tokensUpdated today
    DevelopmentAuto-check passed

Works with

Categories

Questions about Library Docs Lookup with Context7

What does Library Docs Lookup with Context7 do?

Looks up current documentation and code examples for any library, framework, SDK or CLI with the Context7 ctx7 command instead of relying on training data. The skill uses the ctx7 CLI in two steps: resolve a library name and a query into a Context7 library ID, then query the docs with that ID. Resolving is mandatory unless you already give an ID in the org/project form.

When should I use Library Docs Lookup with Context7?

Library Docs Lookup with Context7 fits situations like: answering API syntax or configuration questions for a specific library; checking the current way to do a task after a library version upgrade; finding setup instructions or CLI usage for a framework or SDK; debugging behavior that depends on a particular library.

How do I install Library Docs Lookup with Context7 in Claude Code?

Run `npx skills add oss-apps/split-pro --skill find-docs -a claude-code`. Or copy the skill folder (.opencode/skills/find-docs in oss-apps/split-pro) into .claude/skills/find-docs in your project. Claude Code loads it when a task matches its description.

How do I install Library Docs Lookup with Context7 in Codex?

Run `npx skills add oss-apps/split-pro --skill find-docs -a codex`. Or copy the skill folder (.opencode/skills/find-docs in oss-apps/split-pro) into .agents/skills/find-docs in your project. Codex loads it when a task matches its description.

Can I use Library Docs Lookup with Context7 in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add oss-apps/split-pro --skill find-docs -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/find-docs, .gemini/skills/find-docs, .github/skills/find-docs and .opencode/skills/find-docs in your project.

What does Library Docs Lookup with Context7 need to run?

Going by SKILL.md and its folder, Library Docs Lookup with Context7 needs the command-line tools its instructions call (npm and npx) and credentials named CONTEXT7_API_KEY. Our summary lists: Node.js with npm to run ctx7; Network access to Context7.

Does Library Docs Lookup with Context7 access the network?

SKILL.md contains no URLs. Its commands use npm and npx, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Library Docs Lookup with Context7 safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Library Docs Lookup with Context7 use?

Library Docs Lookup with Context7 is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Library Docs Lookup with Context7 use?

About 1.6k tokens (SKILL.md is roughly 6.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Library Docs Lookup with Context7?

Skills that share tags, products or a category with Library Docs Lookup with Context7: Tavily Search API Integration (andrewyng/context-hub, 14k stars), Browser Search (Johell1NS/browser-search, 528 stars), Sponsor Finder (github/awesome-copilot, 40k stars) and Nx Run Tasks (nomcopter/react-mosaic, 4.8k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Library Docs Lookup with Context7?

oss-apps (a GitHub organization) maintains it in oss-apps/split-pro, which has 1,465 GitHub stars. The repository was last updated on October 5, 2026.

Source: oss-apps/split-pro on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.