Agent skill
documentation-lookup
Look up library and framework documentation. Use when the user asks about API docs, library usage, framework features, or mentions specific libraries/packages by name.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/product/documentation-lookup
SKILL.md
Documentation Lookup
When to activate:
- User says "check the docs"
- User needs API documentation or code examples
- User mentions a library/framework name
- Source code of a library is not available locally
Two-step process:
Step 1: Find the library ID
Search for the library to get its context7 ID:
curl -s "https://context7.com/api/v2/search?query={library_name}" | jq '.results[:3]'
Example - searching for "react":
curl -s "https://context7.com/api/v2/search?query=react" | jq '.results[:3] | .[] | {id, title}'
This returns matching libraries. Use the id field (e.g., /facebook/react or /websites/react_dev).
Step 2: Fetch documentation
Use the library ID from step 1:
curl -s "https://context7.com/api/v2/docs/code{library_id}?topic={topic}&page=1"
Example - fetching React hooks docs:
curl -s "https://context7.com/api/v2/docs/code/facebook/react?topic=hooks&page=1"
Parameters:
topic- Focus area (e.g.,hooks,routing,authentication)page- Pagination (1-10), use if first page doesn't have enough info
Response: Returns markdown-formatted documentation snippets with code examples.
Fallback: If context7 doesn't have the library or returns errors, use web search.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?