save-docs

Fetch library documentation from Context7 MCP and save it locally.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/cedricfressin/claude-config --skill save-docs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: save-docs
Source: https://github.com/cedricfressin/claude-config/tree/main/skills/utils-save-docs
Command: npx skills add https://github.com/cedricfressin/claude-config --skill save-docs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Fetch library documentation using Context7 MCP and save it locally for offline reference.

Core Features & Use Cases

  • Offline access: Retrieve and store API references and usage examples for libraries and topics.
  • Automatic organization: Creates .claude/output/docs and saves documents with kebab-case filenames.
  • Use Case: When onboarding a new library, run this skill to assemble a local knowledge base for quick reference.

Quick Start

Use the save-docs skill to fetch documentation for a library and topic, for example: /save-docs shadcn button

Frequently Asked Questions about save-docs

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

FAQPage Schema
How do I save library documentation locally for offline reference?

Saving library documentation locally requires the save-docs skill to fetch content from Context7 MCP and store it under .claude/output/docs with kebab-case filenames for offline reference.

What is Context7 MCP and how does it resolve library IDs?

Context7 MCP is the integration service used to resolve library IDs and fetch the corresponding documentation, enabling the save-docs skill to retrieve and store API references automatically.

Can I fetch offline docs for any library or topic?

You can fetch offline docs for libraries and topics supported by the Context7 MCP integration, which resolves the library ID and retrieves API references and usage examples for local storage.

Do I need Context7 integration to download and store API references?

Yes, Context7 integration is required to resolve library IDs and fetch documentation before the save-docs skill can save the outputs to local storage under .claude/output/docs.

What's the best way to build a local knowledge base when onboarding a new library?

The best way to build a local knowledge base for a new library is running the save-docs skill, which automatically organizes fetched documentation into .claude/output/docs using kebab-case filenames for quick reference.