FlightClaw
PassAudited by ClawScan on May 1, 2026.
Overview
FlightClaw’s artifacts are consistent with a flight-search and price-tracking tool, but users should notice its unpinned Python dependencies, external Google Flights requests, and persistent tracked-trip data.
Before installing, be comfortable with unpinned Python dependencies, Google receiving your flight search details, and your tracked routes being stored in the skill data file. Use a virtual environment, review tracked flights periodically, and delete the tracking file when you are done.
Findings (4)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Installing the skill may bring in external Python package code that can change over time if versions are not pinned.
The setup script installs third-party Python packages without version pins. This is central to the stated flight-search and MCP purpose, but users rely on those packages and their current published versions.
pip install flights "mcp[cli]"
Install in a virtual environment, review or pin dependency versions if reproducibility matters, and verify the package names before running setup.
An agent using the MCP server could add, check, or remove tracked flights as part of a task.
The skill exposes MCP tools that can query flight data and modify the local tracked-flight list. This matches the stated purpose, but it gives an agent operational control over tracking entries.
MCP tools: `search_flights`, `search_dates`, `track_flight`, `check_prices`, `list_tracked`, `remove_tracked`
Ask the agent to confirm before adding or removing tracked flights, and periodically review the tracked list.
Flight origins, destinations, dates, passenger counts, and filters may be sent to Google when searches or price checks run.
Flight search filters are encoded and posted to a Google Flights endpoint. This external provider flow is disclosed by the skill’s purpose and is necessary for search results.
BASE_URL = "https://www.google.com/_/FlightsFrontendUi/data/travel.frontend.flights.FlightsFrontendService/GetShoppingResults"
Use the skill only for travel searches you are comfortable sending to Google Flights.
Your tracked routes, dates, targets, and price history can remain available after the original session.
The skill intentionally stores travel routes and price history persistently, and the README says that data is backed up.
Price history is stored in `skills/flightclaw/data/tracked.json` and persists via R2 backup.
Review or delete `skills/flightclaw/data/tracked.json` when you no longer need tracking, and avoid storing travel plans you consider sensitive.