library-docs-fetch

Fetch and cache third-party library documentation from multiple sources.

2|Updated Jul 13, 2025

Search Tags:#automation #planning #API documentation #third-party libraries #library documentation

Ready to run

npx skills add https://github.com/krzemienski/shannon --skill library-docs-fetch

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: library-docs-fetch
Source: https://github.com/krzemienski/shannon/tree/main/skills/library-docs-fetch
Command: npx skills add https://github.com/krzemienski/shannon --skill library-docs-fetch

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of fetching documentation for third-party libraries, ensuring that planners have accurate and up-to-date information during the planning phase.

Core Features & Use Cases

Documentation Fetching: Fetches documentation for libraries from various sources, including llms.txt, library homepages, Context7 MCP, and GitHub READMEs.
Caching: Caches fetched documentation to ensure it's available for future planning tasks.
Use Case: When planning a feature that depends on a third-party library, this Skill can automatically fetch the latest documentation, ensuring the planner has all necessary information.

Quick Start

Activate the library-docs-fetch skill during the planning phase to automatically fetch and cache library documentation.

Frequently Asked Questions about library-docs-fetch

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

FAQPage Schema

How do I automate fetching API documentation for third-party libraries during project planning?▼

You can automate fetching API documentation by activating a skill that retrieves library docs from sources like llms.txt, homepages, and Context7 MCP, then caches them locally for planners.

What sources can I use to retrieve up-to-date library documentation for my project?▼

To retrieve up-to-date library documentation, you can use multiple sources including library-specific llms.txt files, library homepages, Context7 MCP, and GitHub READMEs.

How does caching library documentation help with feature planning?▼

Caching library documentation ensures that accurate and up-to-date API information remains available locally for future planning tasks, preventing repeated network fetches.

Can I automatically fetch documentation for third-party libraries without manual configuration?▼

Yes, you can automatically fetch documentation for third-party libraries by activating the library-docs-fetch skill during the planning phase to retrieve and cache docs seamlessly.

What is the best way to keep third-party library API documentation accurate for planning phases?▼

The best way to keep API documentation accurate is to use an automated fetcher that pulls from multiple sources like llms.txt and Context7 MCP, then caches the results for planners.

When do I need to fetch and cache library documentation for my project?▼

You need to fetch and cache library documentation when planning a feature that depends on third-party libraries, ensuring the planner has accurate and current API information.