What problem does it solve? Getting Firecrawl wired into an application requires obtaining an API key, storing it correctly in environment configuration, and choosing the right SDK, which involves several manual steps that are easy to get wrong. ## Core Features & Use Cases - Browser Auth Flow: Guides the user through a PKCE-based browser authorization flow to obtain a FIRECRAWL_API_KEY when they do not already have one. - Environment Configuration: Shows how to place FIRECRAWL_API_KEY and optional FIRECRAWL_API_URL (for self-hosted deployments) into .env files without hardcoding credentials. - SDK Selection and Installation: Provides install commands for the JavaScript/TypeScript (@mendable/firecrawl-js) and Python (firecrawl-py) SDKs, plus links to per-language source-of-truth documentation. - Use Case: A developer starting a new Node.js project that needs web scraping runs this skill to authenticate Firecrawl in the browser, save the key to .env, install the SDK, and run a first smoke-test request. ## Quick Start Set up Firecrawl in my project by getting an API key, adding it to my .env file, and installing the right SDK for my stack.