research-lib
Research a library and create comprehensive documentation in .claude/docs/libraries/.
Best use case
research-lib is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Research a library and create comprehensive documentation in .claude/docs/libraries/.
Teams using research-lib should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/research-lib/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How research-lib Compares
| Feature / Agent | research-lib | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Research a library and create comprehensive documentation in .claude/docs/libraries/.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
Best AI Skills for Claude
Explore the best AI skills for Claude and Claude Code across coding, research, workflow automation, documentation, and agent operations.
ChatGPT vs Claude for Agent Skills
Compare ChatGPT and Claude for AI agent skills across coding, writing, research, and reusable workflow execution.
AI Agents for Startups
Explore AI agent skills for startup validation, product research, growth experiments, documentation, and fast execution with small teams.
SKILL.md Source
# Research Library
Research $ARGUMENTS and create documentation in `.claude/docs/libraries/`.
## Research Items
### Primary Tool: General-Purpose Subagent (Opus)
Use a general-purpose subagent (Opus) with WebSearch/WebFetch for comprehensive library research:
```
Agent tool:
subagent_type: "general-purpose"
prompt: |
Research: {library}. Find latest version, official documentation,
key features, constraints, best practices, known issues, and usage patterns.
Use WebSearch and WebFetch to gather information.
Save results to .claude/docs/libraries/{library}.md
Return concise summary.
```
### Fallback: WebSearch/WebFetch
If Gemini unavailable, verify via manual web search:
- Official documentation
- GitHub README
- PyPI / npm page
- Latest release notes
### Content to Document
1. **Basic Information**
- Official name, version, license
- Official URL
- Installation command
2. **Core Features**
- Main features
- Basic usage (code examples)
3. **Constraints & Notes**
- Known limitations
- Conflicts with other libraries
- Performance characteristics
- Async/sync considerations
4. **Usage Patterns in This Project**
- Recommended usage
- Patterns to avoid
5. **Troubleshooting**
- Common errors and solutions
## Output Location
`.claude/docs/libraries/$ARGUMENTS.md`
## Documentation Template
```markdown
# {Library Name}
## Overview
- **Version**: {version}
- **License**: {license}
- **Official URL**: {url}
- **Installation**: `{install command}`
## Core Features
{Description of main features}
## Basic Usage
```python
{Code example}
```
## Constraints & Notes
- {Limitation 1}
- {Limitation 2}
## Recommended Patterns
### Do
```python
{Good pattern}
```
### Don't
```python
{Anti-pattern}
```
## Troubleshooting
### {Error message}
**Cause**: {cause}
**Solution**: {solution}
## References
- [Official Docs]({url})
- [GitHub]({url})
```Related Skills
context-loader
ALWAYS activate this skill at the start of every task. Load project context from .claude/ directory including coding rules, design decisions, and documentation before executing any task.
update-lib-docs
Update library documentation in .claude/docs/libraries/ with latest information from web search.
update-design
Explicitly update DESIGN.md with decisions from the current conversation. Use when you want to force a design document update.
troubleshoot
Diagnose and plan fixes for errors/bugs with Codex-first multi-agent collaboration (Codex + Opus 4.6 + Agent Teams). Codex CLI is consulted in EVERY phase for deep code reasoning, hypothesis evaluation, and fix validation. Phase 1: Error reproduction & context gathering (Opus subagent 1M context + Codex initial analysis + Claude user interaction). Phase 2: Parallel diagnosis (Agent Teams: Root Cause Analyst [Codex-driven] + Impact Investigator [Opus + Codex risk analysis]). Phase 3: Fix plan synthesis, Codex validation & user approval. Fix implementation is handled separately by /team-implement.
team-review
Parallel code review using Agent Teams. Spawns specialized reviewers (security, quality, test coverage) to review implementation from different perspectives simultaneously. Run after implementation.
team-implement
Parallel implementation using Agent Teams. Spawns teammates per module/layer, each owning separate files to avoid conflicts. Uses shared task list with dependencies for autonomous coordination. Run after /start-feature plan approval.
tdd
Implement features using Test-Driven Development (TDD) with Red-Green-Refactor cycle.
start-feature
Start a new feature with multi-agent collaboration (Opus 4.6 + Agent Teams). Phase 1: Codebase understanding (Opus subagent 1M context + Claude user interaction). Phase 2: Parallel research & design (Agent Teams: Researcher + Architect). Phase 3: Plan synthesis & user approval. Implementation is handled separately by /team-implement.
spike
Time-boxed technical investigation/feasibility study with Codex-first multi-agent collaboration (Codex + Opus 4.6 + Agent Teams). Codex CLI is consulted in EVERY phase for question framing, feasibility analysis, and final evaluation. Phase 1: Frame the investigation question & constraints (Claude user interaction + Codex question decomposition). Phase 2: Parallel investigation (Agent Teams: Researcher [Opus external research] + Feasibility Analyst [Codex deep analysis] + optional prototype). Phase 3: Codex synthesis into go/no-go recommendation & research report. Produces a DECISION DOCUMENT, NOT an implementation plan. Use /add-feature or /start-feature after a GO decision.
simplify
Simplify and refactor code while preserving functionality and library constraints.
plan
Create a detailed implementation plan for a feature or task. Use when user wants to plan before coding.
init
Analyze project structure and populate the "Repository Identity" section of CLAUDE.md (Zone B) plus AGENTS.md.