What problem does it solve? Plain web scraping fails when content only appears after clicks, form fills, or navigation. This Skill guides you to integrate Firecrawl's /interact endpoint into product code so your feature can perform multi-step browser actions that /scrape cannot complete. ## Core Features & Use Cases - Browser Action Integration: Add clicks, typing, pagination, and form submissions to scraping flows using the /interact endpoint. - Escalation Guidance: Start with /scrape and escalate to /interact only when the page must be manipulated, keeping browser workflows scoped to the minimum needed. - Authenticated Flows: Use persistent profiles when a feature requires login-gated dashboards or session state across requests. - Use Case: A product feature must search a faceted catalog, paginate through results, and extract listings that only render after interaction. This Skill directs you to the correct language-specific Firecrawl docs and integration pattern. ## Quick Start Ask the agent to integrate Firecrawl /interact into your feature so it can fill the search form, paginate results, and extract the dynamic content.