agentleFS
keysersoosekeysersoose/claude-code-setup/skills/crawl4ai/SKILL.md

crawl4ai

Skill2 starsChanged 4 months agoMITView on GitHub

Crawl4AI capture - turn web pages, including JavaScript-rendered ones, into LLM-ready markdown or structured CSS/JSON extractions, with batch crawling, screenshots/PDFs, and extraction-quality checks. Use when a task needs page content beyond what a simple fetch or browser read returns, or when deep-research captures raw sources.

  • Installs packages

5 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions5 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 5

    1. brettdavies/crawl4ai-skill★ 49same name
    2. durandom/skills★ 7same name
    3. nek1987/auto-agent-harness★ 4same name
    4. inovve/homelab-agent-skills★ 1same name
    5. mj-deving/pai-skills★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository4 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

9 rules. 0 are common, 2 are distinctive, and 7 are very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 7

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use this skill to crawl web pages into inspectable markdown or structured JSON.

    line 10
  2. Very specific:

    If the crwl command is available:

    line 26
  3. Very specific:

    If the current harness uses a dedicated virtual environment, run the same commands with that environment's Python and crwl executable.

    line 32
  4. Distinctive:

    If browser setup fails:

    line 34
  5. Very specific:

    Start from URLs selected by advanced-web-search, browser inspection, or user input.

    line 48
  6. Distinctive:

    no login wall, CAPTCHA, cookie-only shell, or empty JS shell

    line 58
  7. Very specific:

    Run scripts with the Python environment that has crawl4ai installed.

    line 89
  8. Very specific:

    Do not treat result.success or HTTP 200 as enough.

    line 100
  9. Very specific:

    Create output directories before using -O.

    line 101

“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Crawl4AI

Overview

Use this skill to crawl web pages into inspectable markdown or structured JSON. In this repository, crawl4ai is a required peer for deep-research: search discovers sources, Crawl4AI captures raw/source content, and the research skill synthesizes evidence.

The skill is harness-neutral. Use the local CLI, Python SDK, Docker API, MCP bridge, or an equivalent harness-provided Crawl4AI tool.

Required Setup

Install Crawl4AI in the Python runtime used by the current agent:

python -m pip install -U crawl4ai
crawl4ai-setup
crawl4ai-doctor

Official project: https://github.com/unclecode/crawl4ai

If the crwl command is available:

crwl crawl https://example.com -o markdown --bypass-cache

If the current harness uses a dedicated virtual environment, run the same commands with that environment's Python and crwl executable. Do not hardcode another machine's venv path in reusable skills.

If browser setup fails:

python -m playwright install chromium

On Linux servers that need browser system dependencies:

python -m playwright install --with-deps chromium

Core Workflow

  1. Start from URLs selected by advanced-web-search, browser inspection, or user input.
  2. Choose the lightest adequate capture mode:
    • simple markdown for normal pages
    • scan_full_page, wait_for, or longer timeout for dynamic pages
    • CSS/JSON extraction for repeated structured pages
    • screenshot/PDF only when visual evidence matters
  3. Capture raw markdown/JSON into a durable path such as research/raw/YYYY-MM-DD/<topic>/.
  4. Inspect extraction quality before using the content:
    • non-trivial length
    • expected title/headings/entities
    • no login wall, CAPTCHA, cookie-only shell, or empty JS shell
    • relevant section present, not just boilerplate
  5. Mark each source as fetched, partial, blocked, empty, or needs_review.
  6. Pass raw paths and quality notes back to deep-research for source cards and evidence matrices.

CLI Patterns

# Markdown to a file; create the parent directory first
mkdir -p research/raw/2026-07-05/example
crwl crawl https://example.com -o markdown --bypass-cache -O research/raw/2026-07-05/example/example.md

# Dynamic page
crwl crawl https://example.com -c "wait_for=css:.content,page_timeout=60000" -o markdown

More CLI forms (JSON output, full-page scroll, browser flags, structured extraction) are in references/cli-guide.md.

On Windows consoles, prefer UTF-8 output and -O <file> if rich terminal output causes encoding issues.

Python SDK

For scripted capture, prefer the bundled scripts below. For custom SDK code — browser/run configs, arun_many batches, CSS extraction schemas — read references/sdk-guide.md.

Bundled Scripts

  • scripts/crawl_url.py - single URL markdown capture with quality checks.
  • scripts/batch_crawler.py - batch URL capture into research/raw/....
  • scripts/extraction_pipeline.py - CSS/JSON structured extraction helper.
  • scripts/google_search.py - Google result-page scraping fallback when normal search tools are unavailable.

Run scripts with the Python environment that has crawl4ai installed.

References

  • references/cli-guide.md for command-line usage.
  • references/sdk-guide.md for Python SDK usage.
  • references/quality-checks.md for extraction validation.
  • references/windows-notes.md for Windows-specific encoding/path notes.

Pitfalls

  • Do not treat result.success or HTTP 200 as enough; inspect the extracted content.
  • Create output directories before using -O.
  • result.markdown may be an object; use .raw_markdown when present.
  • markdown-fit can be empty if filters are too aggressive or the site blocks crawling.
  • For bot-protected/authenticated sites, expect partial results unless a profile/cookies/session is configured.

Download now (ZIP)

Does 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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.