doc-fetcher
Skill9 starsChanged 8 months agoMITView on GitHub
Fetch external documentation sites and convert to local markdown for context
In this repository5 other files it gives its agents.
- changelog-monitorSkill
- competitor-watchSkill
- content-extractorSkill
- site-auditorSkill
- visual-qaSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 39
Remove cookie banners and ads
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Doc Fetcher
Fetch and convert external documentation to local markdown files for use as context (RAG, reference, etc.).
Prerequisites
CF Browser MCP server must be configured (see the CF Browser quick start).
Workflow
Step 1: Discover Pages
browser_links(base_url) → list of all linked pages- Filter to same-domain URLs only
- Filter by documentation patterns (e.g., /docs/, /guide/, /api/, /reference/)
- Cap at
max_pages(default 20)
Step 2: Fetch Content
For each discovered page:
browser_markdown(page_url) → markdown contentProcess pages in parallel where possible (batch of 5).
Step 3: Clean Content
For each page:
- Strip navigation headers/sidebars
- Remove footer boilerplate
- Remove cookie banners and ads
- Preserve code blocks and tables
Step 4: Save to Disk
Save to docs/{source_domain}/:
docs/
└── docs.astro.build/
├── index.md ← Table of contents
├── getting-started.md
├── routing.md
└── components.mdStep 5: Generate Index
Create index.md with:
- Source URL and fetch timestamp
- Table of contents with links to each file
- Total page count and approximate token count
Step 6: Report
Output summary:
- Pages fetched successfully
- Total approximate token count
- Key topics covered
- Any failed pages
Parameters
url(required): Base URL of documentation sitemax_pages(optional, default=20): Maximum pages to fetchoutput_dir(optional, default="docs/{domain}"): Where to save filespatterns(optional): URL patterns to include (e.g., "/docs/", "/api/")
Examples
"Fetch the Hono documentation"
→ browser_links("https://hono.dev") → filter /docs/ → browser_markdown each → save
"Download Cloudflare Workers docs for reference"
→ browser_links("https://developers.cloudflare.com/workers/") → fetch up to 20 pages
"Index the Astro guide for RAG"
→ browser_links("https://docs.astro.build/") → fetch + clean + save with indexDoes it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

