crawl-site

Crawl an entire website into local markdown files using a keyless BFS crawler or the Firecrawl API.

Updated Jun 9, 2026
One-click install
npx skills add https://github.com/timikalo7/Execute --skill crawl-site-timikalo7
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: crawl-site
Source: https://github.com/timikalo7/Execute/tree/main/.claude/skills/crawl-site
Command: npx skills add https://github.com/timikalo7/Execute --skill crawl-site-timikalo7

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Fetching one page at a time with WebFetch is too slow when research requires many pages from a single site, such as full documentation, a competitor's site, or a reference library. This Skill walks an entire site and saves every page as a readable local markdown file you can search and load on demand. ## Core Features & Use Cases - Keyless BFS crawler: Built-in same-origin link walking with plain fetch and HTML-to-text extraction, requiring no API key and producing one .md file per page plus an index.json manifest. - Firecrawl backend: When FIRECRAWL_API_KEY is set, the same command routes to the Firecrawl v1 crawl API for JS rendering and clean markdown output. - Bounded, targeted crawls: --max-pages caps the crawl size and --include limits the walk to a path prefix such as /docs, skipping irrelevant marketing pages. - Use Case: Run a crawl of a competitor's documentation with --include /docs, read index.json to see titles and page sizes, then load only the specific pages relevant to your feature comparison. ## Quick Start Ask the agent to crawl a documentation site into local markdown files, for example: crawl https://docs.expo.dev with a max of 30 pages limited to the /docs path and save the output to /tmp/crawl.

Frequently Asked Questions about crawl-site

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

FAQPage Schema
How do I crawl a whole website into markdown files?

Run node crawl.mjs with a start URL, a --max-pages limit, and an --out directory. The crawler walks same-origin links, extracts title and text from each page, and writes one markdown file per page plus an index.json manifest.

How to scrape a documentation site without an API key?

Use the built-in keyless BFS crawler, which is the default when FIRECRAWL_API_KEY is not set. It uses plain fetch with same-origin link walking and works well for static or server-rendered sites like most documentation and marketing pages.

Does the crawler work on JavaScript-rendered sites?

The keyless backend does no JS rendering, so a JS-only SPA yields empty text. Set FIRECRAWL_API_KEY to route the same command through the Firecrawl v1 API, which renders JavaScript and returns clean markdown.

Can I limit a crawl to only the docs section of a site?

Yes, pass --include with a path prefix such as /docs to restrict the link walk to that section. This skips marketing pages and keeps the crawl focused on the content you actually need.

Why does the crawler miss pages or return empty text?

The crawler only follows same-origin links and skips non-HTML responses, so external links are never fetched. Empty text usually means the page requires JavaScript rendering, which signals switching to the Firecrawl backend or a browser automation tool.