agentleFS
PatriotAgenticLLCPatriotAgenticLLC/better_claude_skillz/skills/firecrawl/SKILL.md

firecrawl

Skill3 starsChanged 5 months agoMITView on GitHub

Web scraping, search, and crawling via the Firecrawl CLI. Use when asked to scrape a URL, fetch a page, read an article, research a topic online, look something up, search the web, find information about a website, check a competitor, pull documentation, extract data from a site, get the content of a URL, web search, or fetch any webpage. Handles JS-heavy pages, bot-protected sites (Cloudflare), PDFs, and multi-page crawls. Trigger words: scrape, fetch, search the web, read this URL, get this page, crawl, research online, competitor research, pricing page, docs page, download a site, find articles about, web research, browse, extract from this URL.

  • Reads credentials
  • Deletes or force-pushes

32 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use firecrawl-interact, firecrawl-monitor and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • RudraDudhat2509Skill

    firecrawl-interact

    Control and interact with a live browser session on any scraped page — click buttons, fill forms, navigate flows, and extract data using natural language prompts or code. Use when the user needs to interact with a webpage beyond simple scraping: logging into a site, submitting forms, clicking through pagination, handling infinite scroll, navigating multi-step checkout or wizard flows, or when a regular scrape failed because content is behind JavaScript interaction. Also useful for authenticated scraping via profiles. Triggers on "interact", "click", "fill out the form", "log in to", "sign in", "submit", "paginated", "next page", "infinite scroll", "interact with the page", "navigate to", "open a session", or "scrape failed".

    Also in 7 projects that use this

  • firecrawlSkill

    firecrawl-monitor

    Alert by webhook/email on web changes — use for "monitor/watch/track/alert me when": recurring checks on known URLs (prefer over repeated one-off scrapes) or web-wide watches for new results (queries + goal).

    Also in 5 projects that use this

  • get-proofpilotSkill

    firecrawl-crawl

    Bulk extract content from an entire website or site section. Use this skill when the user wants to crawl a site, extract all pages from a docs section, bulk-scrape multiple pages following links, or says "crawl", "get all the pages", "extract everything under /docs", "bulk extract", or needs content from many pages on the same site. Handles depth limits, path filtering, and concurrent extraction.

    Also in 7 projects that use this

  • firecrawlSkill

    firecrawl-build-onboarding

    Get Firecrawl credentials and SDK setup into a project. Use when an application needs `FIRECRAWL_API_KEY`, when an agent should add Firecrawl to `.env`, when the user wants to authenticate Firecrawl for app code, or when choosing the first SDK and docs for a new Firecrawl integration. This skill includes its own browser auth flow, so it does not depend on the website onboarding skill.

    Also in 6 projects that use this

  • get-proofpilotSkill

    firecrawl-agent

    AI-powered autonomous data extraction that navigates complex sites and returns structured JSON. Use this skill when the user wants structured data from websites, needs to extract pricing tiers, product listings, directory entries, or any data as JSON with a schema. Triggers on "extract structured data", "get all the products", "pull pricing info", "extract as JSON", or when the user provides a JSON schema for website data. More powerful than simple scraping for multi-page structured extraction.

    Also in 6 projects that use this

  • parcadeiSkill

    firecrawl-scrape

    Scrape web pages and extract content via Firecrawl MCP

    Also in 10 projects that use this

  • +4 more from get-proofpilot
  • +1 more from firecrawl

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 1 is distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 31 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Follow this order — start simple, escalate only if needed:

    line 38
  2. Very specific:

    Always write to a temp folder with -o — never dump large content inline into the conversation

    line 84
  3. Very specific:

    Use .firecrawl/ as a scratch folder for session work

    line 85
  4. Very specific:

    Never read entire large files at once — use head -100 or search for specific sections first

    line 87

“Common” is measured: kept by at least 6 in 10 of the 31 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

Firecrawl

Web scraping CLI. Turns any URL into clean LLM-ready markdown. 8 commands, all via the firecrawl CLI.

Environment

The CLI reads its API key from the FIRECRAWL_API_KEY environment variable. Set your FIRECRAWL_API_KEY (via env or your secrets manager, e.g. Doppler) before running any command. If your secrets are injected by a manager, run the CLI inside that manager's shell (for example, doppler run -- firecrawl ...).

Command Reference

CommandWhat it doesWhen to use
firecrawl scrape "<url>"Single page → clean markdownHave a URL, need its content
firecrawl search "query" --scrapeSearch + pull full page contentNo URL yet, need to find + read pages
firecrawl crawl "<url>" --limit NBulk extract entire site sectionNeed all /docs/ or all /blog/ pages
firecrawl map "<url>"Discover all URLs in a domainNeed to find a specific subpage
firecrawl agent "<url>" --prompt "..."AI-powered structured extractionNeed structured data (pricing, specs, contacts)
firecrawl browser "<url>"Interactive — clicks, forms, scrollScrape failed, content needs interaction
firecrawl download "<url>"Save entire site as local filesOffline reference, bulk archival
firecrawl credit-usageCheck credit consumptionMonitor usage

Escalation Pattern

Follow this order — start simple, escalate only if needed:

  1. No URL yet → firecrawl search "query" --scrape --limit 3
  2. Have a URL → firecrawl scrape "<url>"
  3. Large site, need a specific subpage → firecrawl map "<url>" --search "keyword" then scrape the match
  4. Need bulk content from a section → firecrawl crawl "<url>" --limit 20
  5. Scrape failed (JS gating, modals, login, pagination) → firecrawl browser "<url>"

Common Patterns

Research a topic (no URL)

firecrawl search "AI agency pricing models 2025" --scrape --limit 5 -o .firecrawl/search-results.json

Scrape a specific page

firecrawl scrape "https://competitor.com/pricing" -o .firecrawl/competitor-pricing.md

Pull all docs from a site

firecrawl crawl "https://docs.example.com" --limit 50 -o .firecrawl/docs/

Extract structured data with AI

firecrawl agent "https://example.com" --prompt "Extract: company name, pricing tiers, features per tier" -o .firecrawl/extracted.json

Find a specific subpage on a large site

firecrawl map "https://example.com" --search "pricing"
# Then scrape the matching URL

Parallel scrapes (faster)

firecrawl scrape "<url-1>" -o .firecrawl/1.md &
firecrawl scrape "<url-2>" -o .firecrawl/2.md &
firecrawl scrape "<url-3>" -o .firecrawl/3.md &
wait

Output Rules

  • Always write to a temp folder with -o — never dump large content inline into the conversation
  • Use .firecrawl/ as a scratch folder for session work
  • For content worth keeping, move it somewhere permanent when done
  • Never read entire large files at once — use head -100 or search for specific sections first
  • search --scrape already fetches full page content — don't re-scrape those same URLs
# Extract URLs from search output
jq -r '.data.web[].url' .firecrawl/search.json

# Check file size before reading
wc -l .firecrawl/file.md && head -100 .firecrawl/file.md

# Clean up temp files when done
rm -rf .firecrawl/*

Important: Always Quote URLs

URLs with ? and & characters must be quoted in bash — they're shell special characters:

# Correct
firecrawl scrape "https://example.com/page?id=123&ref=abc"

# Wrong — shell will break the URL
firecrawl scrape https://example.com/page?id=123&ref=abc

Credits

Each scrape/search/crawl costs credits. Check balance:

firecrawl --status
firecrawl credit-usage

Top up at firecrawl.dev if you run low.

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.