lib-docs
Skill3 starsChanged 10 months agoMITView on GitHub
Fetch library documentation and code examples. Use when user asks about library APIs, needs code examples, or says "use lib-docs", "lookup docs for X", "how does [library] work". Works with any language/framework.
In this repository13 other files it gives its agents.
- alpinejsSkill
- browser-toolsSkill
- clojure-replSkill
- clojure-symbolsSkill
- code-renameSkill
- code-searchSkill
- code-symbolsSkill
- file-navSkill
- githubSkill
- janetSkill
- plansSkill
- playwrightSkill
- skill-creatorSkill
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 8 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
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 28
Check if library has a pre-configured source in references/sources.md:
- Distinctive: line 29
Known library: Use configured URL directly
- Distinctive: line 34
Use WebFetch with a focused prompt:
- Distinctive: line 53
When no pre-configured source exists:
- Distinctive: line 63
Check sources.md → HoneySQL on cljdoc.org
- Distinctive: line 68
Check sources.md → not found
- Distinctive: line 75
Only fetch what's needed for the specific question
- Distinctive: line 76
Prefer targeted page URLs over index pages
- Distinctive: line 77
Use focused prompts to extract relevant sections
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
Library Documentation Skill
Fetch up-to-date documentation for any library using web search and pre-configured sources.
Quick Reference (Common Sources)
| Library | Primary Source |
| Clojure libs | cljdoc.org/d/{group}/{artifact} |
| HTMX | htmx.org/docs/ |
| Alpine.js | alpinejs.dev/ |
| Tailwind | tailwindcss.com/docs/ |
| DaisyUI | daisyui.com/components/ |
| React | react.dev/reference/ |
For full list: See references/sources.md
Workflow
1. Resolve Documentation Source
Check if library has a pre-configured source in references/sources.md:
- Known library: Use configured URL directly
- Unknown library: WebSearch for
"[library name] official documentation"
2. Fetch Documentation
Use WebFetch with a focused prompt:
WebFetch URL with prompt: "Extract [topic] documentation, API reference, and code examples for [library]"Tips for effective fetches:
- Target specific pages (API reference, getting started) over landing pages
- Include version if user specified one
- Request code examples explicitly
3. Summarize for User
Return:
- Relevant API/function signatures
- Code examples demonstrating usage
- Link to source for further reading
Fallback: Unknown Libraries
When no pre-configured source exists:
- WebSearch:
"[library] official documentation site" - Identify official source from results (prefer: official site > GitHub > Stack Overflow)
- WebFetch the docs page
- Offer to add the source to
references/sources.mdfor future lookups
Examples
User: "How do I use HoneySQL's where clause?"
- Check sources.md → HoneySQL on cljdoc.org
- WebFetch
https://cljdoc.org/d/com.github.seancorfield/honeysql/with prompt about where clauses - Return examples and API info
User: "lookup docs for some-obscure-lib"
- Check sources.md → not found
- WebSearch for official docs
- WebFetch from search result
- Return docs + offer to save source
Token Efficiency
- Only fetch what's needed for the specific question
- Prefer targeted page URLs over index pages
- Use focused prompts to extract relevant sections
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.

