Look up documentation and source code for libraries and packages. Use when the user asks a question about a library, needs to understand a library's API, or when you need information about a library that you don't know about. Triggers on questions like "How do I use X library?", "What's the API for Y?", "Show me how Z library handles this", or when encountering unfamiliar library usage.
Look up library documentation by finding and exploring the library's source code repository.
First, check if the library source code already exists locally:
# Check common locations
ls /tmp/cc-repos/{library-name} 2>/dev/null
If the library exists locally, skip to step 3.
If not available locally, find and clone the repository:
mkdir -p /tmp/cc-repos
git clone https://github.com/{owner}/{repo}.git /tmp/cc-repos/{repo-name}
Common repository patterns:
package.json homepage or repository field, or search https://github.com/{package-name}Launch a Research agent (using the Task tool with subagent_type="Explore") to traverse the repository and answer the question.
Example prompt for the agent:
Explore the repository at /tmp/cc-repos/{repo-name} to answer: {user's question}
Focus on:
- README and documentation files
- Source code structure
- API exports and public interfaces
- Examples and tests for usage patterns
Use the research findings to provide a clear, accurate answer to the user's question about the library.
Search for places (restaurants, cafes, etc.) via Google Places API proxy on localhost.
Interact with GitHub using the `gh` CLI. Use `gh issue`, `gh pr`, `gh run`, and `gh api` for issues, PRs, CI runs, and advanced queries.
Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.
Start voice calls via the OpenClaw voice-call plugin.
Notion API for creating and managing pages, databases, and blocks.
Gemini CLI for one-shot Q&A, summaries, and generation.
Category:developer