update-lib-docs
Skill18 starsChanged 9 months agoMITView on GitHub
Update library documentation in .claude/docs/libraries/ with latest information from web search.
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 5 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 9
Update documentation in .claude/docs/libraries/ with latest information.
- Distinctive: line 36
Add new features/constraints
- Distinctive: line 38
Update code examples if needed
- Distinctive: line 43
After updating docs, verify:
- Distinctive: line 61
Add update notice at top of file:
- Distinctive: line 81
After updating, report to user (in Korean):
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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 Korean):
- Which libraries were updated
- Significant changes found
- Any action items for the project
Other versions2 projects use a version of this.
Word for word · 1
- ilhae-ai/claude-code-orchestrator★ 18100% same
Edited · 0
None found.
Wrote their own version · 1
- DeL-TaiseiOzaki/claude-code-orchestra★ 199same name
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
- research-libSkill
- simplifySkill
- startprojectSkill
- tddSkill
- update-designSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.