Update to Jumpseat

{
  "description": "Find the correct scheduled flight and add it to the authenticated user's Jumpseat profile. Use when a user asks to add, log, save, or plan a flight and provides a flight number or route plus a travel date, including ambiguous or incomplete flight requests that require clarification.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 417
    }
  ],
  "name": "plan-and-add-flight",
  "skill_md_contents": "---\nname: plan-and-add-flight\ndescription: Find the correct scheduled flight and add it to the authenticated user's Jumpseat profile. Use when a user asks to add, log, save, or plan a flight and provides a flight number or route plus a travel date, including ambiguous or incomplete flight requests that require clarification.\n---\n\n# Plan and Add Flight\n\nTurn a natural-language travel request into a verified Jumpseat flight record. Search first, resolve ambiguity, obtain confirmation for the exact result, and only then add it.\n\n## Workflow\n\n1. Extract the travel date and either:\n   - airline IATA code plus flight number; or\n   - departure and arrival airport IATA codes.\n2. Resolve relative dates such as \"next Friday\" against the user's current date and timezone. State the resulting calendar date when ambiguity is possible.\n3. If an airport is given by city or name, use `search-airports` to find candidates. Ask the user to choose when multiple airports fit. Ask one concise clarification question for other missing search input. Do not guess an airline, airport, route, flight number, or date.\n4. Search with exactly one primary tool:\n   - Use `search-flights-by-number` when the airline code and flight number are known.\n   - Otherwise use `search-flights-by-route` when both airport codes are known.\n   - Leave `include_codeshares` false unless the user asks for codeshares or the primary search finds no suitable result and codeshares are a plausible explanation.\n5. Evaluate the results:\n   - If none match, report the searched criteria and ask the user to correct them. Do not add anything.\n   - If exactly one result matches, summarize its airline and flight number, date, departure and arrival airports, and scheduled airport-local times when available. Show operating airline details when provided.\n   - If multiple results match, present a compact numbered list with the distinguishing details and ask the user to select one. Do not choose silently.\n6. Ask the user to confirm adding the exact selected flight. A prior explicit instruction that identifies an unambiguous exact result, such as \"add EI105 on 2026-08-14,\" counts as confirmation; otherwise wait for an affirmative response.\n7. Call `add-flight` once, passing the selected search result's `id` as `flight_id`. Never invent or reuse a flight ID from an unrelated search.\n8. Report the result using the returned identifiers in concise text. If the flight was already on the user's profile, say so. If the user asks to see their updated list, call `get-my-upcoming-flights`.\n\n## Guardrails\n\n- Treat searches as read-only and `add-flight` as the only write in this workflow.\n- Never call `add-flight` when the selected result is uncertain or the user has not confirmed it.\n- Do not add every result from a search.\n- Do not repeat `add-flight` after an ambiguous error. Check the user's flights if read access is available; an absent result does not prove the add failed because a write may still be in progress.\n- Preserve the user's stated operating or marketing airline preference. If a codeshare creates ambiguity, show both identities and ask which result they intend.\n- Keep questions and result summaries brief. Do not expose internal search IDs before confirmation unless needed to distinguish otherwise identical results.\n"
}