What problem does it solve? When a product feature starts with a user query instead of a known URL, developers need a reliable way to discover relevant web pages before any extraction happens. This Skill guides the integration of the Firecrawl /search endpoint into applications and agent workflows so query-to-URL discovery becomes a predictable pipeline stage. ## Core Features & Use Cases - Query-First Discovery: Use /search to turn a natural-language query into a ranked shortlist of web pages for downstream processing. - Selective Hydration: Decide explicitly whether the product needs snippets, URLs, or full result content, and prefer selective follow-up extraction over broad hydration when cost or latency matters. - Escalation Routing: Clear rules for when to switch surfaces — firecrawl-build-scrape when you already have a URL, firecrawl-build-interact for pages requiring clicks or forms, and firecrawl-research-index or firecrawl-developer-index for paper or developer-content search. - Use Case: Build an answer-generation feature that searches the web for a user's question, shortlists cited sources, and then scrapes only the top results for full content. ## Quick Start Ask the agent to integrate Firecrawl /search into your app so a user query returns a shortlist of source URLs ready for scraping.