Agent skill

Firecrawl Search Integration

by firecrawl in firecrawl/firecrawl

Guidance for adding Firecrawl's /search endpoint to product code and agent workflows when a feature starts from a query rather than a URL.

ISCAuto-check passedBackend & APIs

Install Firecrawl Search Integration

skills CLI
$ npx skills add firecrawl/firecrawl --skill firecrawl-build-search -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install firecrawl/firecrawl firecrawl-build-search --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/firecrawl/firecrawl.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/firecrawl-build-search .claude/skills/firecrawl-build-search && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
firecrawl-build-search
GitHub stars
190k
Used in
1 other repo
Token cost
~1.1k tokens
SKILL.md length
342 words
Files
1
Skills in repo
5
Repo updated
First seen
Licence
ISC

At a glance

Guidance for adding Firecrawl's /search endpoint to product code and agent workflows when a feature starts from a query rather than a URL.

  • Building a feature that starts from a user question and needs live web results
  • SKILL.md covers Use This When, Default Recommendations, Common Product Patterns and Escalation Rules, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Creating a query-to-URL pipeline before scraping

What it does

This skill guides integrating Firecrawl's `/search` endpoint into product code and agent workflows, for cases where an application starts with a query instead of a URL. It treats `/search` as discovery, ranking and source selection, and suggests keeping search and extraction conceptually separate unless scraping the results is clearly needed, preferring selective follow-up extraction over broad hydration when cost or latency matters.

Typical patterns are answer generation with cited sources, company, competitor or topic discovery, research workflows that end in a shortlist of web pages, and query-to-URL pipelines for a later scrape or interact step. Escalation rules point elsewhere: to the scrape skill when a URL is known, to the interact skill when result pages need clicks or forms, and to the research or developer index skills for published papers or issues and documentation, since the `categories` option on `/search` only filters ordinary web results. The agent is told to settle whether the product needs snippets, URLs or full content and to keep the query contract stable.

When your agent uses it

  • Building a feature that starts from a user question and needs live web results
  • Creating a query-to-URL pipeline before scraping
  • Adding cited-source answer generation backed by web search
  • Choosing between search, scrape, interact and index surfaces

Example prompts

  • “Add a Firecrawl search step to our research agent so it returns a shortlist of source pages for each question.”
  • “Build an endpoint that takes a company name, searches the web and passes the top URLs to our scraper.”
  • “Should this paper-search feature use /search? It needs PubMed results.”

What it can do on your machine

Read from SKILL.md and the folder at commit e5df790. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • docs.firecrawl.dev

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Firecrawl Search Integration loads about 1.1k tokens when it runs. Until then it costs about 69 tokens; SKILL.md has 342 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~69
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from firecrawl/firecrawl at commit e5df790, republished under its ISC licence (© firecrawl). 342 words, ~1,072 tokens.

Download SKILL.mdSave it as .claude/skills/firecrawl-build-search/SKILL.md (or your agent's skills folder).
name
firecrawl-build-search
description
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.
license
ISC
metadata.author
firecrawl
metadata.version
0.1.0
metadata.homepage
https://www.firecrawl.dev
metadata.source
https://github.com/firecrawl/skills

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, ISC. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/firecrawl-build-search of firecrawl/firecrawl.

Open the folder on GitHubat commit e5df790

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in firecrawl/firecrawl, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Firecrawl Search Integration next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Firecrawl Search Integration compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Firecrawl Search Integration this skillfirecrawl/firecrawl190k1 repos~1.1kAutomated safety check: PassISC
Printing Press Librarymvanhorn/printing-press-library2.1k—~4.8kAutomated safety check: PassNone
Apify Integration Developmentapify/agent-skills2.4k—~3.4kAutomated safety check: PassNone
Routing Outbound API CallsPostHog/posthog40k—~2.7kAutomated safety check: PassCustom licence
Firecrawl Enterprise Rbacjeremylongshore/tons-of-skills-marketplace2.8k—~1.1kAutomated safety check: PassMIT
Firecrawl Webhooks Eventsjeremylongshore/tons-of-skills-marketplace2.8k—~1.2kAutomated safety check: PassMIT

Similar skills

  • Printing Press Library

    mvanhorn/printing-press-library

    A skill your agent uses when looking for a CLI, API wrapper, scraper, data-source tool, automation tool, or focused agent skill for a task; searches the Printing Press Library and installs matching…

    2.1k GitHub stars~4.8k tokensUpdated today
    Backend & APIsAuto-check passed
  • Official

    Guides designing and building an official Apify integration for a company's product: workflow-automation apps, AI agent plugins, AI framework packages or direct API clients.

    2.4k GitHub stars~3.4k tokensUpdated yesterday
    Backend & APIsAuto-check passed
  • Official

    Use before adding or changing Python code that calls a third-party HTTP API from PostHog (a vendor REST call, a vendor SDK client, a scraping or enrichment service), and before adding or changing a…

    40k GitHub stars~2.7k tokensUpdated today
    Backend & APIsAuto-check passed
  • Firecrawl Enterprise Rbac

    jeremylongshore/tons-of-skills-marketplace

    Design and audit Firecrawl team roles, API-key ownership, endpoint and format restrictions, IP restrictions, SSO, and separation of duties.

    2.8k GitHub stars~1.1k tokensUpdated today
    Backend & APIsAuto-check passed
  • Firecrawl Webhooks Events

    jeremylongshore/tons-of-skills-marketplace

    Receive, verify, deduplicate, process, and reconcile current Firecrawl crawl, batch, extract, agent, and monitor webhooks.

    2.8k GitHub stars~1.2k tokensUpdated today
    Backend & APIsAuto-check passed
  • Tavily Search API Integration

    andrewyng/context-hub

    Guides building Tavily integrations for web search, URL extraction, site crawling and AI-assisted research in Python or JavaScript agent and RAG projects.

    14k GitHub stars~1.1k tokensUpdated 4 mo ago
    AI & LLM EngineeringAuto-check passed

More from firecrawl/firecrawl

  • Firecrawl Build Onboarding

    firecrawl/firecrawl

    Gets Firecrawl working in a project: signs you in through the browser, saves FIRECRAWL_API_KEY to .env and picks the first SDK or REST path.

    190k GitHub starsUsed in 1 repo~1.4k tokens
    Auto-check: notes
  • Adds Firecrawl's /scrape endpoint to application code to pull markdown, HTML, links, screenshots or structured data from a single known URL.

    190k GitHub starsUsed in 1 repo~944 tokens
    Auto-check passed
  • Firecrawl App Integration

    firecrawl/firecrawl

    Adds web search, scraping, structured extraction and browser interaction to application code using Firecrawl's scrape, search and interact endpoints.

    190k GitHub stars~2.1k tokensUpdated today
    Auto-check: notes
  • Guides adding Firecrawl's /interact endpoint to product code for pages that need clicks, forms, pagination or logged-in flows beyond plain scraping.

    190k GitHub starsUsed in 1 repo~731 tokens
    Auto-check passed

Works with

Questions about Firecrawl Search Integration

What does Firecrawl Search Integration do?

Guidance for adding Firecrawl's /search endpoint to product code and agent workflows when a feature starts from a query rather than a URL. This skill guides integrating Firecrawl's `/search` endpoint into product code and agent workflows, for cases where an application starts with a query instead of a URL. It treats `/search` as discovery, ranking and source selection, and suggests keeping search and extraction conceptually separate unless scraping the results is clearly needed, preferring selective follow-up extraction over broad hydration when cost or latency matters.

When should I use Firecrawl Search Integration?

Firecrawl Search Integration fits situations like: building a feature that starts from a user question and needs live web results; creating a query-to-URL pipeline before scraping; adding cited-source answer generation backed by web search; choosing between search, scrape, interact and index surfaces.

How do I install Firecrawl Search Integration in Claude Code?

Run `npx skills add firecrawl/firecrawl --skill firecrawl-build-search -a claude-code`. Or copy the skill folder (skills/firecrawl-build-search in firecrawl/firecrawl) into .claude/skills/firecrawl-build-search in your project. Claude Code loads it when a task matches its description.

How do I install Firecrawl Search Integration in Codex?

Run `npx skills add firecrawl/firecrawl --skill firecrawl-build-search -a codex`. Or copy the skill folder (skills/firecrawl-build-search in firecrawl/firecrawl) into .agents/skills/firecrawl-build-search in your project. Codex loads it when a task matches its description.

Can I use Firecrawl Search Integration in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add firecrawl/firecrawl --skill firecrawl-build-search -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/firecrawl-build-search, .gemini/skills/firecrawl-build-search, .github/skills/firecrawl-build-search and .opencode/skills/firecrawl-build-search in your project.

What does Firecrawl Search Integration need to run?

SKILL.md names no scripts, command-line tools or credentials: Firecrawl Search Integration is instructions for the agent only.

Does Firecrawl Search Integration access the network?

SKILL.md names 1 domain. As links in the text: docs.firecrawl.dev. This is read from the text; nothing was executed.

Is Firecrawl Search Integration safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Firecrawl Search Integration use?

Firecrawl Search Integration is published under the ISC licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Firecrawl Search Integration use?

About 1.1k tokens (SKILL.md is roughly 4.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Firecrawl Search Integration?

Skills that share tags, products or a category with Firecrawl Search Integration: Printing Press Library (mvanhorn/printing-press-library, 2.1k stars), Apify Integration Development (apify/agent-skills, 2.4k stars), Routing Outbound API Calls (PostHog/posthog, 40k stars) and Firecrawl Enterprise Rbac (jeremylongshore/tons-of-skills-marketplace, 2.8k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Firecrawl Search Integration?

firecrawl (a GitHub organization) maintains it in firecrawl/firecrawl, which has 189,703 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on October 9, 2026.

Source: firecrawl/firecrawl on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.