research-lib
Skill18 starsChanged 10 months agoMITView on GitHub
Research a library and create comprehensive documentation in .claude/docs/libraries/.
2 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- DeL-TaiseiOzaki/claude-code-orchestraedited, first seen Sep 10, 2026
- gaebalai/claude-code-orchestratorword for word, first seen Jan 31, 2026
Other versions2 projects use a version of this.
Word for word · 1
- gaebalai/claude-code-orchestrator★ 18100% same
Edited · 1
- DeL-TaiseiOzaki/claude-code-orchestra★ 19916% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository13 other files it gives its agents.
- .codex/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- checkpointingSkill
- codex-systemSkill
- design-trackerSkill
- gemini-systemSkill
- initSkill
- planSkill
- simplifySkill
- startprojectSkill
- tddSkill
- update-designSkill
- update-lib-docsSkill
The file
Files
Research Library
Research $ARGUMENTS and create documentation in .claude/docs/libraries/.
Research Items
Always Verify via Web Search
- Official documentation
- GitHub README
- PyPI / npm page
- Latest release notes
Content to Document
- Basic Information
- Official name, version, license
- Official URL
- Installation command
- Core Features
- Main features
- Basic usage (code examples)
- Constraints & Notes
- Known limitations
- Conflicts with other libraries
- Performance characteristics
- Async/sync considerations
- Usage Patterns in This Project
- Recommended usage
- Patterns to avoid
- Troubleshooting
- Common errors and solutions
Output Location
.claude/docs/libraries/$ARGUMENTS.md
Documentation Template
# {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
{Good pattern}Don't
{Anti-pattern}Troubleshooting
{Error message}
Cause: {cause} Solution: {solution}
References
- Official Docs
- GitHub
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.