agentleFS
brettatomsbrettatoms/agent-skills/lib-docs/SKILL.md

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.

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
  1. Very specific:

    Check if library has a pre-configured source in references/sources.md:

    line 28
  2. Distinctive:

    Known library: Use configured URL directly

    line 29
  3. Distinctive:

    Use WebFetch with a focused prompt:

    line 34
  4. Distinctive:

    When no pre-configured source exists:

    line 53
  5. Distinctive:

    Check sources.md → HoneySQL on cljdoc.org

    line 63
  6. Distinctive:

    Check sources.md → not found

    line 68
  7. Distinctive:

    Only fetch what's needed for the specific question

    line 75
  8. Distinctive:

    Prefer targeted page URLs over index pages

    line 76
  9. Distinctive:

    Use focused prompts to extract relevant sections

    line 77

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Library Documentation Skill

Fetch up-to-date documentation for any library using web search and pre-configured sources.

Quick Reference (Common Sources)

LibraryPrimary Source
Clojure libscljdoc.org/d/{group}/{artifact}
HTMXhtmx.org/docs/
Alpine.jsalpinejs.dev/
Tailwindtailwindcss.com/docs/
DaisyUIdaisyui.com/components/
Reactreact.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:

  1. WebSearch: "[library] official documentation site"
  2. Identify official source from results (prefer: official site > GitHub > Stack Overflow)
  3. WebFetch the docs page
  4. Offer to add the source to references/sources.md for future lookups

Examples

User: "How do I use HoneySQL's where clause?"

  1. Check sources.md → HoneySQL on cljdoc.org
  2. WebFetch https://cljdoc.org/d/com.github.seancorfield/honeysql/ with prompt about where clauses
  3. Return examples and API info

User: "lookup docs for some-obscure-lib"

  1. Check sources.md → not found
  2. WebSearch for official docs
  3. WebFetch from search result
  4. 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

Download now (ZIP)

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.