cache-docs

Cache fetched library documentation under docs/<library-name>/ with YAML frontmatter.

1|1|Updated Jan 13, 2026
One-click install
npx skills add https://github.com/MQFacultyOfArts/PromptGrimoireTool --skill cache-docs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cache-docs
Source: https://github.com/MQFacultyOfArts/PromptGrimoireTool/tree/main/.claude/skills/cache-docs
Command: npx skills add https://github.com/MQFacultyOfArts/PromptGrimoireTool --skill cache-docs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill reduces manual overhead by automatically saving fetched library documentation into a local cache, ensuring quick offline reference and consistent access across projects.

Core Features & Use Cases

  • Automatic caching: when documentation is fetched, save a copy under docs/<library-name>/ with YAML frontmatter.
  • Slug-based organization: create library directories and maintain a centralized index at docs/_index.md.
  • Rich metadata: store source URL, fetched timestamp, library name, and a concise summary in the YAML header.
  • Offline reference: preserves essential content for future use even without network access.
  • Use Case: when onboarding a new project with external dependencies, cache their docs for future queries and reference.

Quick Start

Trigger the skill after you fetch documentation or paste library docs; verify a new directory docs/<library-name>/ is created, an appropriately slugified file is saved with frontmatter, and docs/_index.md is updated.

Frequently Asked Questions about cache-docs

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

FAQPage Schema
How do I cache library documentation for offline reference?

Caching library documentation involves saving fetched docs locally under docs/<library-name>/ with YAML frontmatter. This preserves page content, stores source URLs and timestamps, and updates a centralized docs/_index.md for offline access.

What is the best way to keep a local index of fetched library docs?

The best way to maintain a local index of fetched library docs is to save files in slug-based library directories while automatically updating a centralized docs/_index.md file. This ensures consistent organization and quick retrieval across projects.

Does this documentation caching approach work with pasted docs and new dependencies?

Yes, documentation caching works when WebFetch retrieves docs, when users paste docs manually, or when importing new dependencies lacking cached docs. It automatically creates library directories and saves files with rich YAML metadata.

How do I store source URLs and timestamps when saving webfetch documentation?

To store source URLs and timestamps when saving WebFetch documentation, the caching process embeds rich metadata in YAML frontmatter. This header captures the source URL, fetched timestamp, library name, and a concise summary.

Can I use cached docs offline without network access?

Yes, you can use cached docs offline without network access because the caching mechanism preserves essential page content locally. The fetched documentation remains available for future queries even when network connectivity is unavailable.