Menu
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.
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.
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.
| name | destination-catalog |
| version | 1.0.0 |
| description | 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. |
| triggers | ["where should I go","list destinations","tell me about","what is there to do in","best time to visit","destination guide"] |
| tools | ["list_destinations","describe_destination"] |
| mutating | false |
Call list_destinations when the user wants to browse what the app
offers (the wizard's destination picker, an "ideas for the year"
question, etc).
Call describe_destination when the user asks ABOUT a specific city or
when you need catalog data (best time to visit, summary, signature
neighborhoods) before you make another call.
Do NOT invent destinations not in the catalog. If a city is missing, hand off to the web-search skill explicitly: "Madrid isn't in the local catalog yet, want me to search the web for it?"
For a "browse" question:
list_destinations().For an "about" question:
describe_destination({ city }).bestTimeToVisit
if the user is in planning mode.describe_destination for 5 cities in one turn — pick the
most relevant 2 and offer the rest as a follow-up.