Update to Foyard

{
  "description": "Plan a trip with one or more legs and overnight stops using Foyard's tools. Use when someone wants to work out how to travel between places and where to stay, compare the options, and open a Foyard checkout for the ones they choose.",
  "included_files": [],
  "name": "plan-a-trip",
  "skill_md_contents": "---\nname: plan-a-trip\ndescription: Plan a trip with one or more legs and overnight stops using Foyard's tools. Use when someone wants to work out how to travel between places and where to stay, compare the options, and open a Foyard checkout for the ones they choose.\n---\n\n# Plan a trip\n\nUse this workflow when someone asks for help with a journey that may need several transport\nlegs, places to stay, or both. The user's explicit instructions come first: if they ask for only\none part (just a train, just a hotel) or want things done in a different order, do that and skip\nthe steps that don't apply.\n\n## 1. Work out the essentials\n\nBefore searching, work out:\n\n- every place on the route, in order, and where the traveller sleeps each night;\n- the date of each transport leg, and the check-in and check-out dates of each stay;\n- how many people are travelling, and the age of each child;\n- any constraints they gave: only trains and buses, a cabin class, refundable stays only, a\n  budget, a neighbourhood or landmark, a property type.\n\nAsk one short question only when a date a search needs cannot be worked out from the request.\nTurn relative dates into calendar dates (\"next Friday\", \"the 15th of next month\"; for \"next\nweekend\", travel on the Saturday) and say which dates you used. If the number of travellers is\nnot given, search for one adult (one `passengers` entry for `search_transport`, `adults: 1` for\n`search_stays`) and say that you assumed one adult, so they can ask again for more people. If\nchildren are mentioned without their ages, ask for the ages. Do not invent constraints the\ntraveller did not give.\n\n## 2. Search transport: one call per leg and date\n\n`search_transport` covers one route on one date. Call it once for each leg (A to B, then B to C)\nand once more for each other date the traveller wants to compare. A return journey is a leg of\nits own: search it with origin and destination swapped. Pass `modes` when the traveller rules\nout a mode, and `passengers` with one entry per traveller (ages for children).\n\n## 3. Search stays: one call per overnight stop\n\nCall `search_stays` once for each place the traveller stays, with that stop's `check_in` and\n`check_out`, `adults`, `children_ages` and `rooms`. Put the area or landmark in `location`, and\npass `refundable_only`, `accommodation_type` or `star_ratings` when the traveller asks for them.\nCheck-in at a stop should be the day the traveller arrives there. For more results at the same\nstop, call `search_stays` again with `exclude_ids` set to the previous result's\n`pagination.next_exclude_ids`.\n\n## 4. Compare and summarise\n\n- For each leg, give the cheapest and the fastest option with carrier, departure and arrival\n  times, duration, number of transfers and price.\n- For each stay, give a few options with the total price for the stay, the address, and whether\n  the rate is refundable and until when.\n- Check that the plan fits together: each leg arrives before the next one departs, with time to\n  change, and each stay covers the nights between legs.\n- When you give a price, say that Foyard's checkout adds a service fee on top: 10% on hotel stays\n  (rates with `service_fee_rate` 0.1; Foyard's own apartments and rates paid at the hotel have\n  none) and 1% on flights, trains and buses.\n- If a total is useful, label it an estimate made from the prices shown.\n- Use only offers, prices and availability that the tools returned. If a leg or stop has no\n  results, say so and offer another date or a nearby place.\n\n## 5. Open checkout only for what the traveller chooses\n\nCall `create_checkout_link` only after the traveller picks a specific offer, and only for that\noffer, using the `search_id` and `offer_id` from the result that contained it (plus `hotel_id`\nfor a stay). Each call creates a new pending order, so each chosen offer gets exactly one\ncheckout link. Do not create links for options nobody chose.\n\nHotels marked `live_rates: true` are the exception: their prices are previews, and they are\nbooked from the hotel's live rates, which the traveller opens with \"See rates\" on the hotel's\ncard in the stays results. Never call `create_checkout_link` with only `search_id`, `offer_id`\nand `hotel_id` for them. If no results view is shown, tell the traveller to book that hotel on\nfoyard.ai, or offer one of the other hotels.\n\nWhen you share a checkout link, say that:\n\n- payment and the final confirmation happen on the Foyard checkout page, and nothing is booked\n  or charged until the traveller completes that page;\n- the price and availability are checked again at checkout and can change;\n- Foyard's checkout adds its service fee to the price shown (10% on hotel stays that carry it,\n  1% on flights, trains and buses);\n- confirmations, tickets and vouchers arrive by email after payment.\n\nSearch results expire after about 30 minutes, and a checkout link works for 60 minutes. If a\ncheckout link can no longer be created for an older search, or an old link has expired, run that\nsearch again and use the new result.\n\n## Never\n\n- Never ask for, accept, repeat or pass on payment card numbers or other payment details in the\n  conversation. If someone shares them, do not repeat them; explain that payment is taken only\n  on the Foyard checkout page.\n- Never say a trip is booked or confirmed because a checkout link was created.\n- These tools cannot look up, change or cancel an existing booking. For that, suggest contacting\n  Foyard support.\n"
}