Menu
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.
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.
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.
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 | preferences-management |
| version | 1.0.0 |
| description | 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. |
| triggers | ["set my","change my preference","save default","my home airport","I prefer","always use","restore demo seeds"] |
| tools | ["update_preferences"] |
| mutating | true |
update_preferences is auto-registered on the Preferences page (URL
/preferences) by usePilotState({ name: "preferences", setValue }).
On every other page it is not in the registry and a call will silently
fail.
If the user asks to change a preference from elsewhere, reply: "Open the Preferences page; I can change settings there." Do not try to mutate preferences from a trip-detail or itinerary context.
Call into this skill when the user wants to change a long-term setting that affects future trips AND you are on the Preferences page. Typical phrasings:
Do NOT use this for trip-specific edits — those go through trip-mutation
skills (add-day-item, propose-flight, etc.) and target the active trip.
For a settings change:
homeAirport, preferredCurrency, defaultTripLengthDays,
prefersAisleSeat, prefersWindowSeat.update_preferences({ field, value }). The framework pops a
confirm modal (mutating).For "restore the demo seeds":
The demo-seeds restore is a UI-only action exposed as a button on the Preferences page; it is NOT a tool the agent can call. Direct the user to the Preferences page button instead of trying to invoke a tool.
update_preferences
call; do them one at a time so each gets its own confirm gate.