Menu
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.
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
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 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.
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.
| name | propose-hotel |
| version | 1.0.0 |
| description | 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. |
| triggers | ["find a hotel","propose a hotel","where should I stay","hotel options","book a stay","accommodation in"] |
| tools | ["propose_hotel","get_current_date","compute_relative_date","convert_currency"] |
| mutating | false |
propose_hotel is registered ONLY on the Itinerary page (URL pattern /trips/<tripId>/itinerary). On every other page the tool is not in the registry and a call will silently fail.
Before calling, confirm you are on the Itinerary page. If you are NOT, do NOT call this tool. Reply: "Open the trip's Itinerary page first; I can propose hotels from there." Never invent fake results, never apologize for a tool error, never retry on a different tool name.
Call propose_hotel when the user wants accommodation options AND you are on the Itinerary page. Typical phrasings:
Do NOT call for general hotel-industry questions or for opinions about specific brands. Answer in prose for those.
compute_relative_date to convert them to
YYYY-MM-DD.propose_hotel({ destination, checkIn, checkOut, maxPricePerNight? }).
The tool mounts an inline picker in the chat with 2-4 options. The
agent loop pauses until the user picks or skips.The tool resolves with the picked option (or { skipped: true }). The
picker UI already displayed prices, ratings, and amenities, so a short
acknowledgement is enough.
propose_hotel repeatedly without user input.