{"id":66655,"plugin_id":"plugin_asdk_app_6a1f5aa83f888191845b774bd2957f6c","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-10-28T12:30:34.422Z","digest":"5dc7925e5ed2c1b756115fd8631bc91c5f7fcc7081d68fc378d4678763ec66d7","against":null,"payload":{"description":"Give a day-of-travel briefing for an upcoming or ongoing Tineo trip, covering flight status, recorded schedule or gate changes, airport conditions, getting to and from the airport, and weather. Use this when the user asks whether a saved flight is on time, what they need to know for a travel day, or how to get from the airport.","included_files":[],"name":"day-of-travel","skill_md_contents":"---\r\nname: day-of-travel\r\ndescription: Give a day-of-travel briefing for an upcoming or ongoing Tineo trip, covering flight status, recorded schedule or gate changes, airport conditions, getting to and from the airport, and weather. Use this when the user asks whether a saved flight is on time, what they need to know for a travel day, or how to get from the airport.\r\n---\r\n\r\n# Day of travel\r\n\r\nUse this skill to brief the user on a travel day using flights already saved in Tineo. This skill only reads data.\r\n\r\n## Priorities and guardrails\r\n\r\n- Explicit user instructions take priority over the guidelines in this skill. They never override the Tineo server's own authorization checks or confirmation requirements.\r\n- Never show internal IDs or UUIDs (trip, segment, or city IDs). Refer to flights by airline, flight number, date, and route.\r\n- Use YYYY-MM-DD for dates and 24-hour HH:mm for times when passing them to tools.\r\n- This workflow makes no changes. If the user asks to change a flight or booking, summarize the change and wait for a yes before calling any tool that saves data.\r\n- Never invent gate numbers, terminals, delays, or times. If data is missing or stale, say so.\r\n- If a tool errors or the request is not supported, say so briefly and offer to open a support ticket. Call `support_ticket_create` only after the user agrees.\r\n\r\n## Workflow\r\n\r\n1. Find the trip with `trips_list` (`status` set to `ongoing`, then `upcoming`). If several trips match, ask which one.\r\n2. Call `trip_details` with `segment_types` set to `Flight` and pick today's or the next flight. If there is no saved flight, say so and offer to add one.\r\n3. Call `flight_status_for_segment` for that flight.\r\n4. Call `get_flight_change_history` for the trip or flight to list recorded schedule, gate, or delay changes.\r\n5. Call `get_day_of_travel_brief` for the flight to get airport and ground-transport guidance. Use `get_flight_airport_conditions` for delay and weather conditions at the airports; it reads cached data only, so say when it is empty or old.\r\n6. Call `get_trip_weather` with `detail` set to `current` or `hourly` for the relevant city (or `daily` for the days ahead).\r\n\r\n## Output\r\n\r\nKeep the brief short, in this order:\r\n\r\n1. Flight: status, scheduled and latest times, terminal and gate when known.\r\n2. Changes since booking, if any.\r\n3. Airport conditions.\r\n4. Getting to or from the airport.\r\n5. Weather.\r\n6. Suggested actions, such as leaving earlier if a delay is reported.\r\n\r\nLabel anything uncertain, and never present cached conditions as live.\r\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}