ref-url-fetcher

Fetch online content and convert it into Markdown references.

Updated Mar 19, 2026
One-click install
npx skills add https://github.com/sunLeee/optimization --skill ref-url-fetcher
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ref-url-fetcher
Source: https://github.com/sunLeee/optimization/tree/main/.claude/skills/data-fetch/ref-url-fetcher
Command: npx skills add https://github.com/sunLeee/optimization --skill ref-url-fetcher

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually collecting and formatting online content for references is slow and error-prone. This skill automates fetching pages and converting them into clean Markdown references for documentation and knowledge bases.

Core Features & Use Cases

  • Fetch and normalize: Retrieve page HTML via WebFetch and handle errors gracefully.
  • HTML → Markdown: Convert content into concise, readable Markdown suitable for references.
  • Archive & metadata: Save to docs/references/external with metadata for easy retrieval, including source URL and fetch date.

Quick Start

Provide a URL to fetch and the skill will generate a Markdown reference from that page.

Frequently Asked Questions about ref-url-fetcher

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

FAQPage Schema
How do I convert web page HTML into clean Markdown for documentation?

To convert web page HTML into Markdown, fetch the online content and use a renderer to transform it into a concise, readable Markdown document. This process retrieves the page source and formats the text for knowledge bases.

What is the best way to automate fetching online content for Markdown references?

The best way to automate fetching online content for Markdown references is to provide a URL to an automated fetcher. It retrieves the HTML, normalizes the content, and saves it as a shareable Markdown file with metadata.

Can I save fetched web content directly to an external references folder?

Yes, you can save fetched web content to an external references folder. The process automatically saves the generated Markdown file under docs/references/external/, organizing it by domain and slug for easy retrieval.

Does converting web pages to Markdown include source URL and fetch date metadata?

Yes, converting web pages to Markdown includes source URL and fetch date metadata. The skill archives these details within the generated Markdown file to ensure traceability and easy retrieval for documentation.

How do I handle errors when fetching web pages for API references?

To handle errors when fetching web pages for API references, the fetching mechanism includes graceful error handling during the HTML retrieval phase. This ensures the conversion process continues smoothly despite page retrieval issues.

What format do I get when I turn a URL into a documentation reference?

When you turn a URL into a documentation reference, you get a clean Markdown file. This artifact includes the normalized content, source URL, and fetch date, saved under docs/references/external/.