research-lib
Research a library and create comprehensive documentation in .claude/docs/libraries/.
pinned to #d5a3918updated 2 weeks ago
Ask your AI client: “install skills/research-lib”.
Requires the metahub MCP server installed in your client. Set up MCP.
mh install skills/research-libmetahub onboarded this repo on the author's behalf.
If you own github.com/DeL-TaiseiOzaki/claude-code-orchestra on GitHub, claim the listing to take over publishing. Your claim preserves the existing eval history and badges; only the curator label is replaced with verified-publisher on your next publish.
Stars
184
Last commit
2 weeks ago
Latest release
published
About this skill
Pulled from SKILL.md at publish time.
Research $ARGUMENTS and create documentation in `.claude/docs/libraries/`.
Evaluation report
WarningsAutomated checks the publisher passed at publish time — structure, docs, safety, and whether the artifact behaves as claimed.d5a3918· 2 weeks ago
Documentation
32Description qualitywarn
9 words · 85 chars — skills use the description as their trigger; aim higher
Aim for 15+ words and include trigger phrases like “use this skill when …”.
README is present and substantial
18,894 chars · 9 sections · 21 code blocks
Tags / topics declaredwarn
No manifest tags and no GitHub repo topics
Add tags to the manifest (or GitHub topics on the repo) so the registry's search and category filters surface this artifact.
README has usage / example sections
found: Quick Start
Homepage / docs URL declared
no homepage declared (registry will use the repo URL) — info-only, not blocking
Release history
1- releasecurrentd5a3918warn2 weeks ago
Contents
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 the subagent is unavailable, verify via manual 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
Reviews
No reviews yet. Be the first.
Related
Verification Before Completion
Evidence before assertions, always
Writing Plans
Turn specs into phased implementation plans
Test-Driven Development
Red → green → refactor discipline for any feature or bugfix
mh install skills/research-lib