Google Flights Search
ReviewAudited by ClawScan on May 10, 2026.
Overview
The flight-search script is purpose-aligned, but the skill tells the agent to automatically save every search for ongoing price monitoring through another skill without clear opt-in, limits, or cancellation details.
Install only if you are comfortable using SearchAPI.io and if you can control whether searches are saved for monitoring. Before use, confirm that `flight-scoring` and `flight-price-monitor` are trusted, and ask the agent not to enable price tracking unless you explicitly want ongoing monitoring.
Findings (5)
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.
A simple flight lookup could be turned into a saved, monitored search without the user explicitly asking for monitoring.
This forces extra skill use and saving behavior even when the user’s request may only be a one-time flight search.
Always pipe results through the flight-scoring skill to rank before presenting, then ALWAYS save the search via the flight-price-monitor skill for automatic price tracking.
Make scoring optional and require explicit user confirmation before saving a search or enabling price tracking.
The agent may continue tracking travel plans after the immediate task is finished.
Automatic price tracking suggests persistent or recurring activity, but the artifacts do not describe duration, retention, cancellation, or user controls.
then ALWAYS save the search via the `flight-price-monitor` skill for automatic price tracking.
Document exactly what is stored, how often monitoring runs, how long it lasts, and how the user can stop or delete it; make tracking opt-in.
Behavior depends on whatever those skill names resolve to in the user’s environment, including a monitoring skill that may store data.
The skill relies on other named skills, but the provided artifacts do not pin their owner, version, source, or installation requirements.
using the `flight-scoring` skill, then ALWAYS save the search via the `flight-price-monitor` skill
Declare and pin required skill dependencies, and advise users to verify trusted versions before enabling the workflow.
Using the skill consumes SearchAPI.io quota and exposes the API key to the local runtime environment.
The skill requires a provider API key, which is expected for SearchAPI.io but still grants access to the user’s account quota and should be handled carefully.
**SEARCHAPI_KEY** — get your API key from SearchAPI.io after registering, then add it to `.env` at the project root.
Store the key only in a local `.env`, do not paste it into chats, monitor usage, and prefer a restricted or dedicated key if available.
SearchAPI.io will receive travel search details such as route, dates, passenger count, and currency.
The script sends flight-search parameters to the external SearchAPI.io provider, which is disclosed and necessary for the stated function.
SEARCHAPI_ENDPOINT = "https://www.searchapi.io/api/v1/search"
Use the skill only for searches you are comfortable sending to SearchAPI.io and review that provider’s privacy and retention terms.