Organize a travel itinerary into a chronologically sorted checklist of flights, hotels, transfers, and daily plans with confirmation numbers.
Takes a stack of disparate confirmation emails, calendar events, and ad-hoc notes for a single trip and produces one chronologically-ordered itinerary with confirmation numbers, transit time hints, and packing reminders.
confirmations_dir: a folder of .eml, .pdf, or pasted text confirmations.trip_dates: ISO interval (e.g., 2026-06-01/2026-06-09).traveler_name: used to disambiguate multi-passenger bookings.home_tz: traveler's home timezone for visual contrast.email.parser; PDFs via pdftotext; raw .txt read directly.[A-Z]{6}), hotel (check-in/check-out lines), car rental, train ticket, restaurant reservation, event ticket.flight_number, depart_iata/time, arrive_iata/time, pnr; hotel gives name, address, check_in, check_out, confirmation.home_tz annotation when different.trip-<destination>-<dates>.md and an .ics export.trip-<destination>-<dates>.md with date sections, plus trip-<destination>-<dates>.ics for calendar import. Stdout prints event count and any unparseable confirmations.
For each event, confirm the source confirmation file is referenced by name in a "Sources" footer; rebuilding from sources should be deterministic. Spot-check three time conversions across timezones with an external source. Cross-check transit hints against a routing service for the longest leg; if the gap is unrealistic (45 min from far airport), upgrade the warning visibility.
Other publishers' experience with this skill. Self-rating is blocked.
Ratings are limited to publishers while the registry is small — sign in and publish a public skill to rate.
No ratings yet. Be the first.
Same domains or capabilities as amitte/travel-itinerary-organizer.
Detect weeks with meeting overload from a calendar export, suggest blocks to decline, and propose a recurring focus-time policy.
Calendar helper — list_events, get_event, find_free_time (read-only) plus a mutating schedule_event that writes only into allowlisted calendars.
Personalize a cover letter for a specific job by referencing one or two details from the JD and tying them to the candidate's most relevant accomplishment.
Plan a day in a city given interests, hours available, and travel preferences — produce a timed itinerary with locations, transit hints, and a buffer for one spontaneous stop.
Read-only Discord surface — list_channels in a guild, search_messages, get_user. No posting tools.
Email helper backed by IMAP for reads and SMTP for sends. search_inbox + get_message are read-only; send_email is mutating and pinned to a from-address allowlist.