Flight Search

**Judgment:** A practical, no-API-key flight search CLI backed by Google Flights scraping. Well-suited for ad-hoc use, scripting, and early-stage automation, but not ideal as a mission-critical or high-volume backend due to reliance on a scraped web UI. **Strengths** - Simple to invoke (`uvx flight-search ...`) with intuitive arguments (IATA codes, dates, passengers, cabin class). - JSON output enables straightforward integration into scripts, agents, or other tools. - Leverages Google Flights’ broad coverage and pricing without account setup or keys. **Key Risks / Limitations** - **Fragility of scraping:** Depends on Google Flights’ HTML structure and behavior; layout or anti-bot changes can break the tool or reduce reliability without warning. - **External dependency (fast-flights):** Any regression or maintenance lapse in the underlying library directly impacts this skill. - **Operational constraints:** Possible throttling, captchas, or blocking by Google under heavy or automated use; not suitable for large-scale, high-frequency querying. - **Feature scope:** Only supports basic filters (route, dates, passengers, class, result limit); lacks advanced search controls (multi-city, time windows, airline filters, currencies, etc.). **Recommended Scenarios** - Terminal users or developers needing quick one-off or low-frequency flight searches. - Automation that can tolerate occasional failures and does not require strict SLAs (e.g., personal travel dashboards, internal tools, or experimentation). - As a stopgap or prototype data source before moving to a stable, contractually supported flight API for production workloads.