agentleFS
Sign inStart free
arvindandarvindand/agent-skills/skills/context7/SKILL.md

context7

Skill17 starsChanged 11 days agoMITView on GitHub

Documentation lookup via Context7 REST API. Use when the user needs current library APIs, framework patterns, migration guidance, or official code examples for React, Next.js, Prisma, Express, Vue, Angular, Svelte, or other npm/PyPI packages. Use when the user says 'how do I use X library', 'what's the API for Y', or asks for official documentation. Use even when you think you know the answer — training data may not reflect recent releases.

  • Reads credentials

28 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use superpowers, mermaid-diagrams and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • HK-hubSkill

    superpowers

    A complete software development methodology and skill composition system, ported from obra/superpowers. Provides structured, repeatable workflow: brainstorming, design, planning, TDD, subagent-driven dev, code review, finishing branch. Use for coding, building projects, refactoring, bug fixing, or any programming tasks.

    Also in 4 projects that use this

  • LangChainSkill

    mermaid-diagrams

    Embed Mermaid diagrams in generated wiki pages. Use whenever documenting a runtime or request flow, a call sequence, a state machine or lifecycle, a data model or entity relationships, or non-trivial control flow, since these are clearer as a diagram than as prose. Also use when an update run touches a page that already contains a mermaid fence, or a page that contains a text fence a previous run degraded.

    Also in 3 projects that use this

  • SupabaseSkill

    copywriting

    Write or audit UI copy (buttons, labels, empty states, error messages, tooltips, form text) anywhere in the monorepo. Load it before shipping or reviewing any user-facing text — including when copy is incidental to the task, like a new feature that adds buttons, toasts, dialogs, or validation messages.

    Also in 4 projects that use this

  • MicrosoftSkill

    mcp-builder

    Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).

    Also in 5 projects that use this

  • VercelSkill

    vercel-react-best-practices

    React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.

    Also in 4 projects that use this

  • StrayDragonSkill

    ui-ux-pro-max

    UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 8 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient.

    Also in 4 projects that use this

The file

Show its rules and text

We split this skill into the rules it gives an agent

13 rules. 0 are common, 10 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 24 edited versions we read keep these.

  • 10

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use ${CLAUDE_SKILL_DIR}/scripts/context7.py to fetch current library documentation without MCP tool-schema overhead.

    line 11
  2. Distinctive:

    If you already know the library ID, skip search and call:

    line 27
  3. Distinctive:

    If the library ID is unclear, search first:

    line 33
  4. Distinctive:

    Use the returned docs to answer with version-aware guidance and cite the source URL when the script provides one.

    line 40
  5. Distinctive:

    Search only when the library ID is unclear or ambiguous.

    line 44
  6. Very specific:

    Use code mode (default) for API references, function signatures, and implementation examples.

    line 45
  7. Very specific:

    Use info mode for conceptual guides, architecture, and migration-heavy questions.

    line 46
  8. Distinctive:

    Use a focused topic first.

    line 47
  9. Distinctive:

    If syntax is unclear, run:

    line 50
  10. Distinctive:

    Prefer official patterns over generic recall when the docs provide a direct answer.

    line 58
  11. Distinctive:

    Keep the answer tied to the user's requested library and version.

    line 59
  12. Distinctive:

    Call out deprecations, caveats, or migration notes when the docs surface them.

    line 60
  13. Distinctive:

    If the docs are incomplete, say so and fall back to the best available general knowledge instead of inventing specifics.

    line 61

“Common” is measured: kept by at least 6 in 10 of the 24 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Context7 Documentation Lookup

Use ${CLAUDE_SKILL_DIR}/scripts/context7.py to fetch current library documentation without MCP tool-schema overhead.

This is an execution skill. Decide whether to search or fetch directly, run the script, then use the returned docs to answer. Keep the main flow lean and load REFERENCES.md only when you need example commands, common library IDs, or troubleshooting details.

When to Use

Activate when the user asks for:

  • current library or framework APIs
  • official code examples or implementation patterns
  • version-specific docs or migration guidance
  • third-party tool setup that depends on vendor docs
  • documentation for libraries in npm, PyPI, or similar ecosystems

Core Workflow

  1. If you already know the library ID, skip search and call:

    python3 ${CLAUDE_SKILL_DIR}/scripts/context7.py docs <library-id> [topic] [mode]

  2. If the library ID is unclear, search first:

    python3 ${CLAUDE_SKILL_DIR}/scripts/context7.py search "<query>"
  3. Pick the best matching library ID, then fetch docs.
  4. Use the returned docs to answer with version-aware guidance and cite the source URL when the script provides one.

Decision Rules

  • Search only when the library ID is unclear or ambiguous.
  • Use code mode (default) for API references, function signatures, and implementation examples.
  • Use info mode for conceptual guides, architecture, and migration-heavy questions.
  • Use a focused topic first; broaden it if results are empty or off-target.
  • For version-specific docs, append the full upstream tag to the library ID (for example /vercel/next.js/v15.1.8), or include the version in the topic. A bare major such as /vercel/next.js/15 does not resolve.

If syntax is unclear, run:

python3 ${CLAUDE_SKILL_DIR}/scripts/context7.py --help

Output Rules

  • Prefer official patterns over generic recall when the docs provide a direct answer.
  • Keep the answer tied to the user's requested library and version.
  • Call out deprecations, caveats, or migration notes when the docs surface them.
  • If the docs are incomplete, say so and fall back to the best available general knowledge instead of inventing specifics.

Recovery

IssueAction
Library ID is unclearRe-run search with an alternate name, org name, or broader query.
Results are empty or irrelevantBroaden the topic, then retry with the other mode (code vs info).
User needs a specific versionAdd the version to the library ID or mention it in the topic, then verify the returned docs match.
Rate limitedTell the user about CONTEXT7_API_KEY, then use best-effort fallback guidance if needed.
Script usage is unclearRun python3 ${CLAUDE_SKILL_DIR}/scripts/context7.py --help.
Script or network failureSay live docs lookup failed and continue with clearly-labeled fallback knowledge.

License: MIT See also: REFERENCES.md

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free