Update to Eventful: Make Calendar Events

{
  "description": "Turn one visible flight, train, bus, ferry, hotel, or other travel reservation into an editable Event Creator card. Use when the user provides itinerary or booking details for one segment or stay. Normalize cross-zone timing into the app's single event time zone; do not retrieve bookings, check live status, expose unnecessary sensitive data, or batch-create an itinerary.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 243
    }
  ],
  "name": "travel-reservation-event",
  "skill_md_contents": "---\nname: travel-reservation-event\ndescription: Turn one visible flight, train, bus, ferry, hotel, or other travel reservation into an editable Event Creator card. Use when the user provides itinerary or booking details for one segment or stay. Normalize cross-zone timing into the app's single event time zone; do not retrieve bookings, check live status, expose unnecessary sensitive data, or batch-create an itinerary.\n---\n\n# Travel Reservation Event\n\nTurn one supplied travel reservation into one accurate, editable event.\n\n## Inputs\n\nUse reservation or itinerary details visible in the conversation and any\npreferences the user provides. Handle one transportation segment or one lodging\nstay at a time.\n\n## Workflow\n\n1. Select the single reservation to create.\n   - If the source contains several segments or stays and the user did not\n     choose one, ask which one to use.\n   - Do not silently merge connections, return journeys, or separate bookings.\n2. Extract the supported facts.\n   - Build a concise title that identifies the journey or stay.\n   - Capture the scheduled start, scheduled end or explicit duration, and the\n     relevant IANA zones.\n   - Use the departure, boarding, or check-in place as the event location unless\n     the user prefers another location.\n   - Put useful terminal, platform, destination, check-in, or checkout context\n     in the description.\n   - Include a valid HTTP(S) booking or information URL only when it is visible\n     in the source.\n3. Protect sensitive information.\n   - Include a confirmation or booking reference only when the user asks for it\n     or clearly expects it in the calendar entry.\n   - Omit payment data, ticket barcodes, loyalty numbers, passport details, and\n     other unnecessary credentials.\n4. Normalize timing into one event time zone.\n   - For transportation, normally use the departure location's IANA zone.\n     Interpret the departure in that zone, interpret the arrival in its local\n     destination zone, then convert the arrival instant into the chosen event\n     zone for `endLocal`.\n   - Preserve the original arrival local time and destination zone in the\n     description when that context helps the traveler.\n   - For lodging, use the property's IANA zone. Use timed timing when explicit\n     check-in and checkout times are intended; otherwise use inclusive all-day\n     dates.\n   - Resolve date-line crossings, overnight arrivals, and DST before invoking\n     the tool. Confirm that the end instant is after the start instant.\n5. Ask one concise clarification when an ambiguous date, airport or station,\n   local time, time zone, or missing arrival date could change the event.\n   Do not ask about missing optional details.\n6. Invoke `display-event` once with the normalized event.\n7. Present the resulting editable card and briefly note any important zone\n   conversion used.\n\n## Output\n\nDeliver one editable Event Creator card for one travel segment or lodging stay,\nwith timing represented accurately in one IANA zone.\n\n## Boundaries\n\n- Do not retrieve reservations from email, airline, hotel, or booking services.\n- Do not look up live delays, gates, platforms, cancellations, or check-in\n  status.\n- Do not create several itinerary events in one invocation.\n- Do not add attendees, recurrence, reminders, or calendar-account writes.\n- Do not claim the reservation was changed or added to a calendar. The user\n  exports the event from the widget.\n"
}