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.