documentation-lookup_skill

This skill fetches up-to-date library and framework documentation and provides accurate code examples for user questions.
  • TypeScript

43.6k

GitHub Stars

1

Bundled Files

3 weeks ago

Catalog Refreshed

2 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstart where the catalogue uses aiagentskills.

npx veilstart add skill upstash/context7 --skill documentation-lookup

  • SKILL.md2.1 KB

Overview

This skill uses Context7 to fetch up-to-date library and framework documentation for code examples, setup steps, and API references. It activates when users ask about specific packages, configuration, or need code snippets tied to frameworks like Next.js, React, Prisma, or Supabase. The skill ensures responses are current, version-aware, and sourced from the best matching docs.

How this skill works

The skill first calls resolve-library-id with the library name and the user's full question to find the most relevant library entry. It selects the best match by exact name, version preference when provided, and benchmark score. Then it calls query-docs with the chosen libraryId and the user's question, and uses the returned documentation and examples to craft a precise, versioned answer.

When to use it

  • User asks how to configure or set up a framework or middleware (e.g., Next.js middleware setup).
  • User requests code involving a particular library (e.g., write a Prisma query or Supabase auth flow).
  • User asks for API references or method lists for a library (e.g., Supabase auth methods).
  • User mentions specific frameworks or packages by name or version (React 19, Next.js 15).
  • User needs authoritative code examples or migration steps based on current docs.

Best practices

  • Always pass the user's full question to resolve-library-id to improve relevance ranking.
  • Prefer exact name and version-specific library IDs when the user specifies a version.
  • Favor official/primary packages over forks when multiple matches are available.
  • Include cited version information in answers when documentation is versioned.
  • Return concise, copy-pasteable code examples from the fetched docs and note any config prerequisites.

Example use cases

  • Show a working Next.js middleware example for edge runtime and mention required Next.js version.
  • Generate a Prisma query to filter and paginate users, using the latest Prisma docs for syntax.
  • List Supabase client auth methods and show an example sign-in flow from the docs.
  • Explain how to configure Tailwind in a Vite/React project with the exact setup commands.
  • Provide React component patterns or hooks examples pulled from current official docs.

FAQ

The skill selects the best match by exact name, version preference, and benchmark score; it prefers official packages over forks.

Will answers reflect the library version I mention?

Yes. When a version is specified, the skill prefers version-specific library IDs and cites the version in the response.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational