Update to Flight Queue

{
  "description": "Plan the day of a flight with the FlightQueue MCP server. Use when the user asks \"when should I leave for the airport\", \"what time should I get to JFK\", \"is my airport delayed today\", or which terminal or lounge to use.",
  "included_files": [],
  "name": "flightqueue-trip-day",
  "skill_md_contents": "---\nname: flightqueue-trip-day\ndescription: Plan the day of a flight with the FlightQueue MCP server. Use when the user asks \"when should I leave for the airport\", \"what time should I get to JFK\", \"is my airport delayed today\", or which terminal or lounge to use.\n---\n\n# FlightQueue trip day\n\nConnect the FlightQueue MCP server at `https://mcp.flightqueue.com/mcp`.\nEvery tool below takes `iata`, a 3-letter airport code. If the user gives a\ncity or airport name, call `search_airports` with `query` first. Never guess\nthe code.\n\n## Workflow\n\n1. `get_best_time_to_fly` — the quietest arrival window, from historical\n   patterns. Free keys get one recommendation; paid keys get the top 3 with\n   checkpoint detail.\n2. The current queue:\n   - `get_live_wait_time` **(paid)** — the freshest reading, from the\n     airport's own feed. Try it first when the user has Premium.\n   - `get_security_wait_estimate` — the free snapshot. Use it when the live\n     call fails with a Premium error, or when the user has no plan.\n3. `get_faa_delays` with `airports_only_with_delays: true` — ground stops\n   and delay programmes. US airports only.\n4. `get_aviation_weather` — METAR, TAF and flight category. Use it to explain\n   *why* a delay exists: low cloud, visibility, wind or storms.\n5. `get_terminals` with `airline` — which terminal and checkpoint the user's\n   airline uses.\n6. `get_lounges` with `terminal` — lounges airside of that checkpoint, with\n   access rules.\n\nSkip the steps the user did not ask about. A question about the queue alone\nneeds steps 1 and 2.\n\n## Present the result\n\nLead with one time: \"Leave to reach the airport by 06:10.\" Then give the\nreasons in this order: security queue, delays, weather, terminal, lounge.\n\n- Say which source each wait came from. A live reading and a free estimate are\n  different things; never present an estimate as observed.\n- Quote a range, not a single minute value, when the tool returns a confidence\n  band.\n- All times are in the airport's local time.\n\n## Paid tools\n\n`get_live_wait_time` needs a FlightQueue Premium plan. When it returns a\nPremium error, do not retry. Fall back to `get_security_wait_estimate` and\ntell the user that live waits are part of https://flightqueue.com/pricing.\n"
}