Menu
Surface flight options as a picker the user chooses from. Mounts an inline UI in the chat (renderAndWait) and pauses until the user picks one or skips. Used during the Itinerary page; a flights specialist agent also exists at /agents.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | propose-flight |
| version | 1.0.0 |
| description | Surface flight options as a picker the user chooses from. Mounts an inline UI in the chat (renderAndWait) and pauses until the user picks one or skips. Used during the Itinerary page; a flights specialist agent also exists at /agents. |
| triggers | ["find me a flight","propose a flight","suggest flights from","flight options","fly to","ticket from"] |
| tools | ["propose_flight","get_current_date","compute_relative_date","convert_currency"] |
| mutating | false |
propose_flight is registered ONLY on the Itinerary page (URL pattern /trips/<tripId>/itinerary). The tool is mounted by the React component on that page; on every other page (Trips, Trip Detail, Packing, Booking, Preferences, Agents, Threads, Lab) it is NOT in the registry and a call will silently fail.
Before calling, read the registered context. If active_trip state is present and you can see the user is on the Itinerary page, proceed. If not, do NOT call. Instead reply: "Open the trip's Itinerary page first; I can propose flights from there." This redirection is the correct behavior; never invent fake results, never apologize for a tool error, never retry on a different name.
Call propose_flight when the user wants flight options AND you are on the Itinerary page. Typical phrasings:
Do NOT call when the user is asking ABOUT flights as a topic (prices in general, airline opinions). Answer in prose for those.
compute_relative_date to get a YYYY-MM-DD value. Never invent.propose_flight({ origin, destination, date, returnDate? }). The
tool mounts an inline picker in the chat with 2-4 options. The agent
loop pauses until the user picks one or skips.The tool resolves with the picked option (or { skipped: true }). You do
NOT need to emit prices, times, or details — the picker UI already showed
them and the user just made a choice. One sentence acknowledging is enough.
propose_flight twice in a row without user input between.Add an activity, meal, transit segment, or note to a specific day of the itinerary. Mutating; framework will pop a confirm modal before adding.
Manage the trip's packing list: add items, mark packed, suggest items for given conditions. The Packing page exposes the list; the agent can see and edit it via the registered packing actions.
Edit long-term user preferences: home airport, preferred currency, default trip duration, etc. Persisted across trips. Mutating; framework fires the confirm modal before any change.
Surface hotel options as a picker the user chooses from. Mounts an inline UI in the chat (renderAndWait) and pauses until the user picks one or skips. Used during the Itinerary and Trip Detail pages.
Convert an amount from one currency to another using a static rates table. Use for quick orientation only; not for live FX.
Look up cities the app knows about and pull their catalog data. The catalog is small and curated; if a destination is missing, fall back to the web-search skill rather than inventing.