documentation-lookup

documentation-lookup is a skill for Claude Code from shennawardana23/skillme. It costs 66 tokens per session (981 once invoked), scanned A, original, Apache-2.0.

A skill for fetching current documentation for libraries and frameworks through Context7, a service that provides indexed software documentation. It is intended for setup questions, API details, and version-dependent code examples.

In plain words
What is it for?
It helps answer configuration questions and produce code based on the current documented behavior of tools such as React, Next.js, Prisma, or Supabase.
Why use it?
Library behavior and API names change, so remembered information can be wrong or outdated. Looking up the current documentation reduces the chance of writing code for the wrong version.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the skillme plugin — 137 skills, 2 commands shipped together

Good fit It helps answer configuration questions and produce code based on the current documented behavior of tools such as React, Next.js, Prisma, or Supabase.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/shennawardana23/skillme/documentation-lookup
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add shennawardana23/skillme --skill documentation-lookup
Clone the repo
git clone --depth 1 https://github.com/shennawardana23/skillme

Made for: Claude Code.

Or install skillme, the plugin that ships this one along with the rest of its 137 skills, 2 commands.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for documentation-lookup

README.md
[![agentmods](https://agentmods.dev/badge/skills/shennawardana23/skillme/documentation-lookup/github.svg)](https://agentmods.dev/skills/shennawardana23/skillme/documentation-lookup)
Your own site
<a href="https://agentmods.dev/skills/shennawardana23/skillme/documentation-lookup"><img src="https://agentmods.dev/badge/skills/shennawardana23/skillme/documentation-lookup/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for documentation-lookup

Your own site · 80×15
<a href="https://agentmods.dev/skills/shennawardana23/skillme/documentation-lookup"><img src="https://agentmods.dev/badge/skills/shennawardana23/skillme/documentation-lookup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 66 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 981 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00066 $0.00981
Opus 5 $0.00033 $0.00491
Sonnet 5 $0.00013 $0.00196
Haiku 4.5 $0.00007 $0.00098

Measured 11d ago against content hash 92ef852b519e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

documentation-lookup scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/documentation-lookup/SKILL.md · 69 lines

How it starts

The opening of the file, as written. The whole thing — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Documentation Lookup (Context7)

Training data goes stale the moment a library ships a new version. When a question depends on a library's actual current behavior, fetch it live via Context7 rather than answering from memory.

Core Concepts

  • Context7: an MCP server exposing live, indexed library documentation — use it in place of training data for anything version- or API-specific.
  • resolve-library-id: returns Context7-compatible library IDs (format /org/project or /org/project/version) from a library name and query.
  • query-docs: fetches documentation and code snippets for a given library ID and question. Always call resolve-library-id first — never call query-docs with a guessed library ID.

When to Use

  • Setup or configuration questions ("how do I configure middleware in this framework?")
  • Requests for code that depends on a specific library's API ("write a query using this ORM")
  • API or reference questions ("what are this library's auth methods?")
  • The user names a specific framework or library

How It Works

Step 1: Resolve the Library ID

Call resolve-library-id with the library name taken from the question and the user's full question as the query (the full question improves relevance ranking). A valid Context7 library ID is required before calling query-docs — never skip this step.

Step 2: Select the Best Match

From the results, choose using: name match (prefer the exact or closest match to what was asked), benchmark score (higher indicates better documentation quality), source reputation (prefer high/medium reputation), and version (if the user specified one, prefer a version-specific library ID when listed).

Step 3: Fetch the Documentation

Call query-docs with the selected library ID and the user's specific question — be specific to get relevant snippets rather than a generic dump.

Limit: no more than 3 total calls to resolve-library-id/query-docs combined per question. If the answer is still unclear after 3 calls, state the uncertainty explicitly and use the best information gathered rather than guessing further.

Read the full file on GitHub · 69 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 11d ago First seen · 69 lines · 66 tokens per session scan A 92ef852b519e

Subscribe to this mod's changes

documentation-lookup is a skill published in the GitHub repository shennawardana23/skillme (2 stars, last pushed 14d ago), licensed Apache-2.0. It adds 66 tokens to every session and 981 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.