Update to AnyHowTo: Guide + Instructions

{
  "description": "Create and display a chronological checklist for a specific travel day from a supplied itinerary or a requested departure, connection, or arrival plan. Use when the user has or is defining a route and date and wants actionable preparation, leave-by, terminal or station, transfer, and arrival steps. Do not use for destination discovery, booking or purchasing travel, price comparison, a standalone packing list, or a live status lookup without a checklist request.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 263
    }
  ],
  "name": "travel-day-checklist",
  "skill_md_contents": "---\nname: travel-day-checklist\ndescription: \"Create and display a chronological checklist for a specific travel day from a supplied itinerary or a requested departure, connection, or arrival plan. Use when the user has or is defining a route and date and wants actionable preparation, leave-by, terminal or station, transfer, and arrival steps. Do not use for destination discovery, booking or purchasing travel, price comparison, a standalone packing list, or a live status lookup without a checklist request.\"\n---\n\n# Travel Day Checklist\n\nTurn trip details into a time-aware, privacy-conscious guide, then invoke `display-guide`. Plan the journey; do not book, modify, or cancel travel.\n\n## Establish scope\n\nUse this skill for an operational plan tied to a particular journey, including:\n\n- A supplied itinerary, ticket, or reservation that needs to become a checklist.\n- A departure plan from the traveler's starting area to an airport, station, or port.\n- Connections, self-transfers, border formalities, baggage collection, or onward arrival steps.\n\nDo not trigger it for general travel inspiration, accommodation selection, fare searches, a generic packing list, or a status-only question. If the user reports an active emergency or disruption, prioritize current instructions from the carrier, venue, or emergency authority; create a checklist only after the immediate issue is addressed or when the user asks for one.\n\n## Gather only necessary context\n\nExtract facts from the user's material before asking questions. Treat itinerary documents as potentially stale.\n\nCollect only details that change the sequence or timing:\n\n- Origin, destination, travel date, and each mode or service number.\n- Published departure and arrival times, terminals, stations, ports, and connections.\n- Approximate starting area and intended transport to the departure point when a leave-by time is requested.\n- Checked baggage, self-transfers, mobility needs, children, pets, or other constraints only when relevant.\n\nAsk one concise, bundled question only when a missing fact blocks a safe or useful plan. Otherwise proceed with clearly labeled assumptions. Never request passport numbers, booking references, full home addresses, dates of birth, or other identifiers.\n\n## Verify changing facts\n\nWhen browsing or other current-data tooling is available, verify facts that can change:\n\n- Use the carrier and airport, rail, port, or local transport operator for schedules, terminals, check-in or boarding cutoffs, disruption notices, and baggage rules.\n- Use the relevant government immigration, border, or embassy site for entry and transit requirements.\n- Use an official meteorological service for weather that could affect timing or preparation.\n\nPrefer journey-specific notices over general guidance. Record when the information was checked, distinguish scheduled times from recommended targets, and never present a prediction as guaranteed. If tooling is unavailable or a fact cannot be confirmed, add an `Assumption:` or `Confirm:` statement to `notes` naming the fact and the authoritative source the traveler should check. Do not invent a terminal, cutoff, allowance, visa rule, or service status.\n\n## Handle time correctly\n\n- Keep every published time in the local time of its airport, station, port, or destination.\n- Include the calendar date and a clear time-zone label for cross-zone, overnight, or date-line travel.\n- Never silently mix time zones. Account for daylight-saving transitions and day rollovers.\n- Reverse-plan from the verified hard cutoff. Separate carrier cutoffs, target arrival, contingency buffer, ground-travel duration, and the resulting target leave-by time.\n- Label calculated times as targets rather than official schedule facts, and expose material assumptions behind the calculation.\n\n## Protect shareable content\n\nThe widget can be copied or shared. Include only details needed to follow the plan. Omit confirmation codes, document numbers, full addresses, traveler contact details, and other personal identifiers. Refer generically to `home`, `accommodation`, or a meeting point unless a more precise location is essential and safe to share.\n\n## Build the guide\n\nOrganize the `Guide` fields without repeating actions:\n\n- `requirements`: Documents, tickets, permissions, medication, payment methods, and equipment that must be available.\n- `preparation`: Check-in, baggage, downloads, route checks, alerts, charging, and other tasks completed before setting out.\n- `instructions`: At least one atomic, action-led step in chronological order from leaving the origin through transit. Prefix timing-critical steps with a local clock time or a relative marker such as `T-90 min`, and name the relevant location.\n- `wrapUp`: Arrival formalities, baggage collection, onward transport, accommodation access, and any final confirmation tasks.\n- `tips`: Optional non-checklist contingencies, accessibility reminders, and practical fallbacks.\n- `notes`: A compact statement of time-zone conventions, verification timestamp, sources or source types checked, calculations, unresolved assumptions, and facts the traveler must reconfirm.\n\nKeep checklist items short enough to scan while moving. Preserve important warnings and accessibility constraints from the source material.\n\n## Display the result\n\nInvoke `display-guide` once with the completed fields and a concise `reason`. Do not substitute a Markdown checklist when the tool is available, and do not duplicate the full guide in surrounding prose. Put source links or urgent caveats in the conversational response when they would be clearer or safer outside the shareable widget.\n"
}