MCP.Market

firecrawl-build-search skill

by firecrawl·firecrawl/firecrawl·202k stars·AGPL-3.0

Integrate Firecrawl `/search` into product code and agent workflows. Use when an app needs discovery before extraction, when the feature starts with a query instead of a URL, or when the system should search the web and optionally hydrate result content.

A100/100content scan

Is the firecrawl-build-search skill safe?

Clean: nothing in its files matched our rules. We read 1 file in the folder on 2026-10-25.

No findings.

Install the firecrawl-build-search skill

A skill is a folder. Copy it into your agent's skills folder and the agent loads it when the task matches its description. 

git clone --depth 1 https://github.com/firecrawl/firecrawl.git /tmp/firecrawl
mkdir -p ~/.claude/skills
cp -r /tmp/firecrawl/skills/firecrawl-build-search ~/.claude/skills/firecrawl-build-search
available in every project

In the Claude apps, zip the folder and upload it from the Skills settings. The folder on GitHub

The instructions your agent would load

SKILL.md as published, without the frontmatter. Read it on GitHub

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:

  • Node / TypeScript: docs.firecrawl.dev/agent-source-of-truth/node
  • Python: docs.firecrawl.dev/agent-source-of-truth/python
  • Rust: docs.firecrawl.dev/agent-source-of-truth/rust
  • Java: docs.firecrawl.dev/agent-source-of-truth/java
  • Elixir: docs.firecrawl.dev/agent-source-of-truth/elixir
  • cURL / REST: docs.firecrawl.dev/agent-source-of-truth/curl

See Also

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

More skills from firecrawl/firecrawl

  • Afirecrawl-buildIntegrate Firecrawl into application code whenever a product, agent, or workflow needs web data inside the app — web search, live search results, page scraping, structured extraction, or browser interaction. Use when building any feature that needs data from the web in code, even if the user does not mention Firecrawl explicitly and only describes wanting web data, website content, search, scraping, or interaction in an application. Trigger for Firecrawl requests, "fire girl" shorthand, and generic app-level web-data needs that should map to `/scrape`, `/search`, or `/interact`. Do not use this skill for one-off terminal-only web tasks during the current session; use `firecrawl/cli` for those.
  • Afirecrawl-build-interactIntegrate Firecrawl `/interact` into product code for dynamic pages and browser actions after scraping. Use when a feature needs clicks, form fills, pagination, authentication-aware flows, or other multi-step interactions that plain `/scrape` cannot complete.
  • Afirecrawl-build-onboardingGet 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.
  • Afirecrawl-build-scrapeIntegrate Firecrawl `/scrape` into product code for single-page extraction. Use when an app already has a URL and needs markdown, HTML, links, screenshots, metadata, or structured page output. Prefer this skill over broader crawl patterns when the feature is page-level.

All agent skills → · MCP servers