outline-docs

Capture documentation sites and convert pages to markdown with source_url frontmatter.

Updated Apr 18, 2026
One-click install
npx skills add https://github.com/Xyzyx101/Frobnicate --skill outline-docs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: outline-docs
Source: https://github.com/Xyzyx101/Frobnicate/tree/main/.claude/skills/outline-docs
Command: npx skills add https://github.com/Xyzyx101/Frobnicate --skill outline-docs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Capture documentation sites and integrate them into raw/tool-docs, enabling offline access and consistent formatting.

Core Features & Use Cases

  • Map site navigation and select pages to capture with human input.
  • Fetch pages and convert them to clean markdown with source_url frontmatter.
  • Preserve image URLs as inline links for offline viewing.
  • Supports a human-in-the-loop workflow for page validation and output curation.

Quick Start

Provide the documentation site root URL and confirm which pages to capture as the agent maps navigation and saves markdown to raw/tool-docs.

Frequently Asked Questions about outline-docs

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

FAQPage Schema
How do I convert an external documentation site into local markdown files?

To convert an external documentation site into local markdown, provide the site root URL so the agent can map navigation, confirm target pages with you, and save clean markdown files with source_url frontmatter into your local directory.

Does capturing web documentation preserve image URLs for offline viewing?

Yes, capturing web documentation preserves image URLs by keeping them as inline links within the generated markdown files, ensuring images remain accessible for offline viewing and consistent formatting.

How does the human-in-the-loop workflow work when scraping documentation sites?

The human-in-the-loop workflow operates by mapping the target site's navigation structure first, then requiring your explicit confirmation to negotiate and validate exactly which pages to download before fetching and converting them.

What is the best way to archive documentation sites with source_url metadata?

The best way to archive documentation sites with source_url metadata is to map the site navigation, select pages via human confirmation, and write clean markdown into a dedicated directory like raw/tool-docs for easy indexing.

Can I select specific pages to capture when mapping site navigation?

Yes, you can select specific pages to capture because the tool maps the entire site navigation structure and negotiates the page download list with your human-in-the-loop confirmation before fetching any content.

What limitations exist when scraping documentation sites into markdown?

A key limitation is that the scraping process requires human-in-the-loop confirmation for page selection, meaning it does not support fully automated bulk downloads without user validation of the mapped navigation pages.