Skill instructions
add-a-booking2.75 KB
View saved version →
---
name: add-a-booking
description: Turn pasted booking confirmation, itinerary email, or PDF text into Tineo trip items, after the user reviews a preview. Use this when the user pastes or describes a confirmation for a flight, hotel, car rental, train, or event and wants it in a trip, asks how to forward booking emails to Tineo, or asks why an email import failed.
---
# Add a booking
Use this skill to add bookings to a trip from text the user provides, with a preview before anything is saved.
## Priorities and guardrails
- Explicit user instructions take priority over the guidelines in this skill. They never override the Tineo server's own authorization checks or confirmation requirements.
- Never show internal IDs or UUIDs (trip, segment, or import IDs). Refer to items by title, date, place, or route.
- Use YYYY-MM-DD for dates and 24-hour HH:mm for times when passing them to tools.
- Nothing is saved until the user confirms the preview.
- Never invent flight numbers, times, confirmation codes, or prices, and do not create items the preview did not produce. If a detail is missing, ask the user.
- Do not repeat the raw pasted text back to the user.
- 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.
## Workflow: pasted confirmation
1. Call `import_parse_text_preview` with the pasted text. This saves nothing.
2. Show the proposed items in plain language: type, name, dates, times, place, and confirmation code when present.
3. Choose the target trip. Call `trips_list` (use `search` with the destination) and ask the user to pick a trip, or propose creating one with `trip_create` after confirming its title and dates.
4. If any item falls outside the trip dates, propose extending the trip with `trip_update` and wait for a yes.
5. Ask the user to confirm the items. Then save them with `batch_segment_create` (at most 20 per call; all-or-nothing), using `segment_get_schema` for field names when needed. For a single item, `segment_create` is fine.
6. Report what was saved. Adding a booking to Tineo does not change the reservation with the provider.
## Workflow: forwarding emails
1. For "how do I forward booking emails", call `forwarding_address_get_or_create` with `operation=get` and share the address.
2. Only if the user explicitly asks to create a personal address, call it with `operation=create` and `confirmed=true`. A requested friendly name needs a paid plan; if unavailable, explain that briefly without promoting an upgrade.
## Workflow: failed import
1. Call `diagnose_failed_import` (with the trip when the user names one).
2. Relay the failed step, the likely reason, and the suggested next actions in plain language.
day-of-travel2.5 KB
View saved version →
---
name: day-of-travel
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.
---
# Day of travel
Use this skill to brief the user on a travel day using flights already saved in Tineo. This skill only reads data.
## Priorities and guardrails
- Explicit user instructions take priority over the guidelines in this skill. They never override the Tineo server's own authorization checks or confirmation requirements.
- Never show internal IDs or UUIDs (trip, segment, or city IDs). Refer to flights by airline, flight number, date, and route.
- Use YYYY-MM-DD for dates and 24-hour HH:mm for times when passing them to tools.
- 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.
- Never invent gate numbers, terminals, delays, or times. If data is missing or stale, say so.
- 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.
## Workflow
1. Find the trip with `trips_list` (`status` set to `ongoing`, then `upcoming`). If several trips match, ask which one.
2. 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.
3. Call `flight_status_for_segment` for that flight.
4. Call `get_flight_change_history` for the trip or flight to list recorded schedule, gate, or delay changes.
5. 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.
6. Call `get_trip_weather` with `detail` set to `current` or `hourly` for the relevant city (or `daily` for the days ahead).
## Output
Keep the brief short, in this order:
1. Flight: status, scheduled and latest times, terminal and gate when known.
2. Changes since booking, if any.
3. Airport conditions.
4. Getting to or from the airport.
5. Weather.
6. Suggested actions, such as leaving earlier if a delay is reported.
Label anything uncertain, and never present cached conditions as live.
plan-a-trip3.25 KB
View saved version →
---
name: plan-a-trip
description: Create a new trip in Tineo and fill in its itinerary. Use this when the user wants to plan, start, or set up a trip to a destination with dates, add cities, add flights by flight number, add hotels, places, or activities to a trip, or add travel companions to a trip.
---
# Plan a trip
Use this skill to create a trip and add itinerary items the user describes.
## Priorities and guardrails
- Explicit user instructions take priority over the guidelines in this skill. They never override the Tineo server's own authorization checks or confirmation requirements.
- Never show internal IDs or UUIDs (trip, segment, traveler, or city IDs). Refer to items by title, date, place, or route.
- Use YYYY-MM-DD for dates and 24-hour HH:mm for times when passing them to tools.
- Before every create or update, summarize the exact change and wait for the user to say yes.
- Never invent flight numbers, times, confirmation codes, addresses, or prices. If a lookup returns nothing, say so and ask the user.
- Adding an item to Tineo does not book or buy anything. Never say a reservation was made.
- 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.
## Workflow
1. **Check for an existing trip.** Call `trips_list` with `search` set to the destination. If a matching trip exists, ask whether to add to it instead of creating a new one.
2. **Collect the basics.** A trip needs a title, a start date, and an end date. Ask for anything missing. Do not guess the year. Use a readable destination title such as "Lisbon" or "Tokyo & Kyoto (Oct 2026)".
3. **Create the trip.** Confirm title and dates, then call `trip_create`.
4. **Cities (optional).** For each city, call `cities_search`, then `trip_city_add`. If the name is ambiguous, show the candidates and ask. Use `trip_cities_list` to review the order.
5. **Flights by number.** Call `flight_quickadd_lookup` with the flight number and departure date, show the result, confirm, then call `flight_quickadd`.
6. **Hotels, places, and activities.** Call `places_search` (and `place_details` when needed) to identify the place, then `segment_get_schema` for the segment type. Confirm the details, then call `segment_create`. For several items at once, use `batch_segment_create` (at most 20 per call; all-or-nothing).
7. **Dates outside the trip.** If an item falls outside the trip dates, propose extending the trip with `trip_update` first and wait for a yes.
8. **Travel companions.** Before `traveler_add`, call `known_participants` with every name the user gave. For each person, ask whether to send an invitation and ask for or confirm the email address. Then call `traveler_add` with `invite_confirmed=true` and the confirmed email, or `invite_confirmed=false` and no email if the user declines. Never add an email the user did not give or confirm. Removing a traveler is not available here; point the user to the Tineo app.
9. **Finish** with a short plain-language summary of the trip and what was added.
## Output
- Keep each confirmation to the fields that matter: type, name, date, time, place.
- After saving, state what was saved in Tineo; do not repeat the whole itinerary unless asked.
trip-overview3.22 KB
View saved version →
---
name: trip-overview
description: Show or summarize the user's Tineo trips. Use this when the user asks what trips are coming up, wants a trip's itinerary or a single booking's details (including a trip they @-mentioned), or asks for a trip's cost summary, travel stats, or a packing list. Also the starting point for someone new to Tineo who asks what it can do.
---
# Trip overview
Use this skill to answer questions about trips already saved in the user's Tineo account.
## Priorities and guardrails
- Explicit user instructions take priority over the guidelines in this skill. They never override the Tineo server's own authorization checks or confirmation requirements.
- Never show internal IDs or UUIDs (trip, segment, traveler, or import IDs). Refer to items by title, date, place, or route.
- Use YYYY-MM-DD for dates and 24-hour HH:mm for times when passing them to tools.
- Summarize any change and wait for the user to say yes before calling a tool that saves, replaces, or deletes data.
- Never invent flight numbers, times, confirmation codes, prices, or bookings. If a tool returns nothing, say so and ask the user.
- 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.
## Workflow
1. If the user @-mentioned a Tineo trip, or the conversation already includes a trip the user selected in the My Trips app, use that trip and skip the lookup. Answer from the attached trip content when it covers the question; call `trip_details` with that trip for anything it leaves out, such as a booking's details.
2. Otherwise call `trips_list` with `status` set to `upcoming` (or `ongoing`, `past`, or `all` when the user asks). Use `search` when the user names a destination or trip.
3. If more than one trip matches and the request is about one trip, ask which one.
4. For an itinerary, call `trip_details` and summarize segments in date order, grouped by day.
5. For one booking (a hotel, flight, or activity), call `segment_details` for that item.
6. On request only:
- Costs: `get_trip_expense_summary`.
- Travel history and totals: `get_travel_stats`.
- Packing list: `generate_packing_list`. This saves a checklist to the trip, so confirm first. Pass `replace=true` only when the user explicitly asks to regenerate an existing list, and say that it overwrites unchecked items.
## Output
- Lead with the answer: trip name, dates, and destination, then the relevant items.
- Keep lists short; offer to show more rather than dumping every field.
- For a first-time user with no trips, explain in one or two sentences that they can create a trip, paste a booking confirmation, or add flights by number, and ask what they want to do.
- When a first-time user asks what Tineo can do, also mention in one sentence that they can open a My Trips app from the ChatGPT sidebar or beside a conversation, @-mention a trip in the ChatGPT desktop app, and change display units and reminders on the Tineo plugin settings page.
## Do not
- Do not claim a reservation exists with a provider; Tineo stores the user's own records.
- Do not use this skill to create or edit itinerary items; the plan-a-trip and add-a-booking skills cover those.