agentleFS
Sign inStart free
GabrieleDattileGabrieleDattile/agent-superpowers/skills/scraping/firecrawl-search/SKILL.md

firecrawl-build-search

Skill1 starsChanged 15 days agoMITView on GitHub

Integrate Firecrawl `/search` into product code and agent workflows.

  • Reads credentials

8 other projects use a version of this, 8 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use firecrawl-interact, firecrawl-company-directories 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 6 projects that use this

  • firecrawlSkill

    firecrawl-company-directories

    Extract structured company lists with Firecrawl from any page or site that lists companies: accelerator batches, VC portfolios, member and sponsor lists, marketplaces and app directories, YC, Crunchbase, Product Hunt or G2. Use when the user wants those companies as a CSV, JSON, CRM-ready list or research table, even without an explicit request to scrape.

    Also in 3 projects that use this

  • firecrawlSkill

    firecrawl-competitive-intel

    Monitor competitor pricing, features, changelogs, dashboards, and product changes with Firecrawl. Use for recurring competitive intelligence, pricing tier extraction, feature change tracking, or structured competitor alerts.

    Also in 3 projects that use this

  • BBTB2Skill

    firecrawl-parse

    Use this skill whenever the user is working with the Firecrawl API /parse endpoint. Triggers include: uploading local files (PDF, DOCX, XLSX, HTML) to Firecrawl, parsing documents with Firecrawl, extracting markdown or structured JSON from files using Firecrawl, choosing between /parse and /scrape, configuring PDF parsing modes (fast/auto/ocr), setting output formats, enabling zero data retention, or any question about Firecrawl document parsing. Also triggers when the user says 'parse this file with Firecrawl', 'use Firecrawl to extract', or 'Firecrawl /parse'.

    Also in 5 projects that use this

  • UtkarshDubeyGITSkill

    firecrawl-website-design-clone

    Extract any website's design system into an agent-ready DESIGN.md using Firecrawl scrape evidence. Use when the user wants colors, fonts, spacing, components, layout patterns, or brand/UI guidance from a website so AI agents can create new websites, clone a look, or build pages inspired by that design.

    Also in 3 projects that use this

  • parcadeiSkill

    firecrawl-scrape

    Scrape web pages and extract content via Firecrawl MCP

    Also in 6 projects that use this

  • +3 more from firecrawl

The file

We split this skill into the rules it gives an agent

10 rules. 7 are common, 0 are distinctive, and 3 are very specific to this project.

  • 7

    Common

    Most of the 8 edited versions we read keep these.

  • 0

    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. Common:

    Use this when the application starts with a query, not a URL.

    line 39
  2. Very specific:

    Use /search first when URL discovery is part of the product behavior.

    line 49
  3. Common:

    Keep search and extraction conceptually separate unless scraping search results is clearly required.

    line 50
  4. Common:

    Prefer selective follow-up extraction over broad hydration when cost or latency matters.

    line 51
  5. Common:

    If you already have the URL, use firecrawl-build-scrape.

    line 66
  6. Common:

    If the result page then requires clicks or form interaction, escalate to firecrawl-build-interact.

    line 67
  7. Very specific:

    If the feature answers developer questions from issues, pull requests, READMEs, or documentation pages, use the developer index instead: …

    line 69
  8. Very specific:

    Treat /search as discovery, ranking, and source selection.

    line 73
  9. Common:

    Keep the query contract stable so downstream scraping logic stays predictable.

    line 75
  10. Common:

    Read the source-of-truth page for your project language before writing integration code:

    line 79

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

Use this when the application starts with a query, not a URL.

Use This When

  • the user asks a question and the product must discover sources first
  • the feature needs current web results
  • you want to turn a search query into a shortlist of pages for later scraping

Default Recommendations

  • Use /search first when URL discovery is part of the product behavior.
  • Keep search and extraction conceptually separate unless scraping search results is clearly required.
  • Prefer selective follow-up extraction over broad hydration when cost or latency matters.

Common Product Patterns

  • answer generation with cited sources
  • company, competitor, or topic discovery
  • research workflows that produce a shortlist of web pages before deeper extraction
  • query-to-URL pipelines for later /scrape or /interact

Note that "research workflow" here means discovering web pages. If the product is searching published papers, that is a different surface — see the escalation rules below.

Escalation Rules

  • If you already have the URL, use firecrawl-build-scrape.
  • If the result page then requires clicks or form interaction, escalate to firecrawl-build-interact.
  • If the feature searches published research papers — biomedical, clinical, and life-science literature (PubMed, bioRxiv, medRxiv) or arXiv preprints — /search is the wrong surface. Use the research paper index instead: firecrawl-research-index. Passing categories: ["research"] to /search does not query that index; it filters an ordinary web search to research-affiliated websites (the list includes PubMed, bioRxiv, medRxiv, arXiv, and publisher sites) and returns page results from them — no abstract search, related-paper expansion, or full-text passages.
  • If the feature answers developer questions from issues, pull requests, READMEs, or documentation pages, use the developer index instead: firecrawl-developer-index. The same caveat applies to categories: ["developer"].

Implementation Notes

  • Treat /search as discovery, ranking, and source selection.
  • Be explicit about whether the product needs snippets, URLs, or full result content.
  • Keep the query contract stable so downstream scraping logic stays predictable.

Docs (Source of Truth)

Read the source-of-truth page for your project language before writing integration code:

See Also

  • firecrawl-build
  • firecrawl-build-scrape
  • firecrawl-build-interact
  • firecrawl-research-index
  • firecrawl-developer-index

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.

Check your setup, free