update-lib-docs
Update library documentation in .claude/docs/libraries/ with latest information from web search.
pinned to #d5a3918updated 2 weeks ago
Ask your AI client: “install skills/update-lib-docs”.
Requires the metahub MCP server installed in your client. Set up MCP.
mh install skills/update-lib-docsmetahub 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.
Update documentation in `.claude/docs/libraries/` with latest information.
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
11 words · 96 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
Update Library Documentation
Update documentation in .claude/docs/libraries/ with latest information.
Steps
1. Check Existing Documents
List current library documentation:
ls .claude/docs/libraries/
2. Web Search for Latest Info
For each documented library, search for:
- Latest version
- Breaking changes
- Deprecated features
- New features
- Security updates
3. Update Documents
For each library with changes:
- Update version information
- Add new features/constraints
- Mark deprecated APIs
- Update code examples if needed
- Record update date at the top
4. Check Impact on Code
After updating docs, verify:
- Using any deprecated APIs?
- Any breaking change impacts?
- Need to update project dependencies?
Key Items to Check
| Category | What to Look For |
|---|---|
| Security | CVEs, security patches |
| Breaking | API changes, removed features |
| Deprecated | APIs marked for removal |
| Performance | Optimization improvements |
| New Features | Useful additions |
Update Format
Add update notice at top of file:
# {Library Name}
> **Last Updated**: {Date}
> **Version Checked**: {version}
## Recent Changes
- {Change 1}
- {Change 2}
---
{Rest of documentation}
Report
After updating, report to user (in Japanese):
- Which libraries were updated
- Significant changes found
- Any action items for the project
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/update-lib-docs