skills-sh:firecrawl/skills/firecrawl-build-search

firecrawl-build-search

# 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 selec

Not scanned by ClawHub
Source
firecrawl/skills
Freshness
Observed 55m ago
Path
skills/firecrawl-build-search
Commit
7ad43730e76913c4d1e9f94bf6fa6f82e38fc12b

Install

Claim

OpenClaw

openclaw skills install skills-sh:firecrawl/skills/firecrawl-build-search

ClawHub

clawhub install skills-sh:firecrawl/skills/firecrawl-build-search

Upstream checks

Upstream checks are separate from ClawHub scanning.

Gen Agent Trust Hub

pass

Checked 3mo ago

View result
Socket

pass

Checked 3mo ago

View result
Snyk

warn

Checked 3mo ago

View result

Stored SKILL.md

SKILL.md

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 version: "0.1.0" homepage: https://www.firecrawl.dev source: https://github.com/firecrawl/skills inputs:

  • name: FIRECRAWL_API_KEY description: Firecrawl API key for hosted Firecrawl requests. required: true
  • name: FIRECRAWL_API_URL description: Optional base URL for self-hosted Firecrawl deployments. required: false

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 before deeper extraction
  • query-to-URL pipelines for later /scrape or /interact

Escalation Rules

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