simple-flight-search

name	simple-flight-search
description	Use when the user wants Codex to do a simple assisted search for cheap flights without API keys, scraping, browser automation, or booking actions. Helps collect current flight options from public travel search pages, compare prices, dates, stops, airlines, baggage hints, practical booking advice, and summarize a short verified shortlist with source links.
metadata	{"short-description":"Search and compare cheap flights manually"}

Simple Flight Search

Use this skill to help the user find and compare flight options with ordinary web research. This skill deliberately avoids API keys, scraping, reverse-engineered endpoints, automated booking, and fragile browser automation.

Ground Rules

• Always browse/search the web because flight prices and availability change constantly.
• Do not claim direct access to Google Flights or any official airline inventory unless an actual official source is used.
• Do not book, hold, purchase, log in, bypass captchas, or enter passenger/payment data.
• Treat prices as snapshots. Tell the user to verify final price, baggage, refund rules, and payment fees before booking.
• Prefer official airline pages when available, then major aggregators such as Google Flights, Skyscanner, Kayak, Momondo, Expedia, Booking.com Flights, or airline alliance pages.
• Provide source links for the searches or pages used.

Intake

Extract these details from the user request:

• Origin city or airport
• Destination city or airport
• Departure date or date range
• Return date or trip length for round trips
• One-way, round trip, or multi-city
• Passenger count if mentioned
• Cabin class if mentioned
• Constraints: max stops, airlines to include/exclude, baggage, departure windows, airport preferences, budget

If a key detail is missing, make a conservative assumption when possible and state it. Ask one concise question only when the search cannot proceed, such as missing origin, destination, or date window.

Search Workflow

1. Normalize city names to likely airport codes when useful, but keep the original user wording visible.
2. Search at least two sources when feasible.
3. Prefer flexible-date views when the user allows flexibility.
4. Compare total trip cost, not only headline fare. Note when baggage is unclear or likely extra.
5. Filter out obviously impractical options unless the user asks for the absolute lowest price.
6. Keep a small shortlist: usually 3 to 5 options.

Output

Respond in the user's language. Keep the answer compact and practical.

Include:

• Search assumptions
• Best option overall
• Cheapest option
• Short table with price, airline/provider, route, dates/times, stops, duration, baggage note, source
• Practical advice tailored to the search
• Caveats about price freshness and final verification

Use this table shape:

Option	Price	Airline/provider	Route	Stops	Duration	Notes	Source

If exact live prices cannot be confidently found, say so clearly and provide the best next search links rather than inventing fares.

Practical Advice

After the shortlist, add a short "Consigli" section when useful. Keep it specific to the route and results, not generic travel filler.

Prioritize advice like:

• Check nearby airports when they are realistic for the user, such as MXP/LIN/BGY for Milan or JFK/EWR/LGA for New York.
• Try flexible dates if moving by 1 to 3 days may materially lower the fare.
• Watch baggage rules: low headline fares often exclude cabin bags or checked bags.
• Prefer booking directly with the airline when the price gap versus an OTA is small.
• Avoid self-transfer itineraries unless the user accepts the risk and has long layovers.
• Flag risky layovers: usually under 60 minutes for domestic, under 90 minutes for international, or longer when changing terminals/airports.
• Consider total trip cost: airport transfers, baggage, seat selection, overnight hotels, and payment fees.
• For long-haul trips, mention whether paying slightly more for fewer stops or better times is likely worth it.
• For international travel, remind the user to verify passport validity, visa/ESTA/ETA rules, and transit requirements.
• Suggest setting price alerts when dates are flexible or prices look high.
• Mention when waiting may be risky, such as peak holidays, school breaks, major events, or very close departure dates.

Avoid weak myths or overconfident claims, such as "use incognito to always get cheaper flights." If mentioning such tactics, frame them as low-confidence and not a primary strategy.

Ranking Heuristic

Rank by practical value, not price alone:

1. Total price
2. Reasonable duration
3. Fewer stops
4. Airport convenience
5. Baggage clarity
6. Booking reliability

When the cheapest option is meaningfully worse, explain the tradeoff in one sentence.

Example Prompt

Use $simple-flight-search: cerca voli economici Milano -> Tokyo, partenza tra 8 e 15 luglio, ritorno dopo 10-14 giorni, max 1 scalo, ordina per prezzo.