doc-fetcher

Retrieve and structure API/SDK documentation via Context Hub MCP with web fallback.

4|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/Kit4Some/Oh-my-ClaudeClaw --skill doc-fetcher-kit4some
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-fetcher
Source: https://github.com/Kit4Some/Oh-my-ClaudeClaw/tree/main/skills/doc-fetcher
Command: npx skills add https://github.com/Kit4Some/Oh-my-ClaudeClaw --skill doc-fetcher-kit4some

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

API/SDK documentation discovery and retrieval across curated registries and the web, enabling rapid, accurate reference in context.

Core Features & Use Cases

  • Context Hub MCP-based lookup for API/SDK docs
  • Web fallback to cover missing registry docs
  • Progressive disclosure, memory caching, and persistent annotations
  • Knowledge graph linking to related documentation and projects

Quick Start

Instruct the AI to fetch and structure documentation for a given library or framework using Context Hub MCP and a web fallback.

Frequently Asked Questions about doc-fetcher

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fetch API and SDK documentation directly into my AI context?

To fetch API and SDK documentation, the Skill retrieves library or framework references using Context Hub MCP with a web fallback, structuring and caching the results in memory for fast reuse in future sessions.

Why does my AI assistant struggle to recall versioned API docs across sessions?

AI assistants struggle with versioned API docs across sessions because they lack persistent memory. This Skill solves the issue by caching retrieved documentation with memory annotations and progressive disclosure for rapid access.

Can I retrieve documentation for libraries missing from the Context Hub registry?

Yes, you can retrieve documentation for missing libraries. The Skill implements a web fallback mechanism to cover API and SDK references not found in the curated Context Hub MCP registry.

What is the best way to structure and annotate retrieved API documentation for AI?

The best way to structure and annotate API documentation is using progressive disclosure. This Skill exposes results as a compact, searchable memory entry, linking related docs and handling disambiguation decisions automatically.

Do I need to specify the library version when fetching SDK documentation?

Specifying the library version is supported when fetching SDK documentation. The Skill structures and caches versioned docs within the memory context hub, ensuring accurate reference retrieval for your specific framework iteration.