Individual skill
documentation-lookup
Use when the user needs current library, framework, or API documentation and version-specific code examples.
bundled/skills/documentation-lookup/SKILL.md
Source commit 8af6e230d3db0f3022236e67632be6d8b9323bf0
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 11, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 3,817
- Repository last updated
- Nov 9, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai-agents Repository topic
- ai-workflow Repository topic
- automation Repository topic
- codex Repository topic
- developer-tools Repository topic
- skills Repository topic
- ai-skills Repository topic
- claude-code Repository topic
- llm Repository topic
- vibe-coding Repository topic
- docs Derived category
- docs-api Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Read excerpt
# Documentation Lookup
Use current official documentation instead of relying on memory when the answer depends on a library, framework, API, or version.
## Workflow
1. Identify the exact project, package, and version from the request or local dependency files.
2. Prefer an installed documentation set, package source, or purpose-built connector, API, or CLI that reaches the official primary source.
3. Read only the pages needed to answer the question.
4. State the version or documentation date when it affects the answer.
5. 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.
