Documentation Lookup

foryourhealth111-pixel/documentation-lookup

Use when the user needs current library, framework, or API documentation and version-specific code examples.

311 tokens

context cost

the whole folder, loaded on every use

files

instructions only

copies elsewhere

how many repositories repackaged it

2583

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/foryourhealth111-pixel/Vibe-Skills --skill documentation-lookup

The instruction itself

3 sections, as written by the author

Documentation Lookup

Use current official documentation instead of relying on memory when the answer depends on a library, framework, API, or version.

Workflow

Identify the exact project, package, and version from the request or local dependency files.
Prefer an installed documentation set, package source, or purpose-built connector, API, or CLI that reaches the official primary source.
Read only the pages needed to answer the question.
State the version or documentation date when it affects the answer.
Cite the official page or local source path used.

If a current official source is unavailable, say what could not be verified and do not guess. Do not install or recommend an unrelated documentation service as a workaround.

Selection Rules

Prefer the library owner's documentation over tutorials, aggregators, and community mirrors.
Match version-specific questions to the same version of the documentation.
Keep examples limited to the user's requested API and environment.
Separate verified documentation facts from implementation advice.

How to use it

Copy the folder

Take foryourhealth111-pixel/documentation-lookup from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.