Menü
Add an activity, meal, transit segment, or note to a specific day of the itinerary. Mutating; framework will pop a confirm modal before adding.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
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.
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 | add-day-item |
| version | 1.0.0 |
| description | Add an activity, meal, transit segment, or note to a specific day of the itinerary. Mutating; framework will pop a confirm modal before adding. |
| triggers | ["add to my itinerary","schedule for day","plan day","add an activity","book this for","put it on day"] |
| tools | ["add_day_item","get_current_date","compute_relative_date"] |
| mutating | true |
add_day_item 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.
If the user asks to add an itinerary item from a different page, reply: "Open the trip's Itinerary page; I can add items there." Do not retry under another name; do not invent a confirmation.
Call add_day_item when the user wants to add something to a specific day
of the trip's itinerary AND you are on the Itinerary page. Typical phrasings:
Do NOT call for trip-level edits (title, dates, total budget) — those go
through update_<state> actions auto-registered by usePilotState.
compute_relative_date to a YYYY-MM-DD
value, then look up which day index that matches in the trip state.add_day_item({ dayIndex, kind, title, time?, location?, notes? }).
kind is one of: activity, meal, transit, note.kind. If unclear, default to activity.