Airport Connection Rescue Card

Build a calm gate-to-gate action card for tight or disrupted flight connections, including fallback moves, airline scripts, and rule-verification reminders.

Audits

Pass

Install

openclaw skills install airport-connection-rescue-card

Airport Connection Rescue Card

Overview

Airport Connection Rescue Card helps users handle a tight, delayed, or disrupted flight connection with a short action plan. It captures the itinerary, identifies time constraints, prioritizes gate-to-gate moves, prepares airline-help scripts, and lists fallback options if the connection becomes impossible.

This skill does not guarantee that the user will make the flight, receive rebooking, bypass security, recover bags, or receive compensation. Airport, airline, immigration, customs, baggage, and security rules vary and must be verified with official sources and staff. The user should follow all airport and airline rules and avoid unsafe shortcuts.

When to Use

Use this skill when the user wants help with:

  • A tight connection between flights
  • A delayed inbound flight that threatens the next flight
  • A terminal change, gate change, or confusing airport transfer
  • Deciding whether to run, ask staff for help, or rebook
  • Preparing a script for gate agents, airline chat, or customer service
  • Creating a fallback plan if the connection is missed

Trigger phrases: "My connection is tight", "Will I make my connecting flight", "Help me transfer gates fast", "My first flight is delayed and I might miss the next one", "What should I do at the airport"

Required Inputs

Ask for only the most urgent missing details. If the user is already in transit, keep questions short.

  • Current status: landed, taxiing, at gate, still in air, delayed before departure, or already missed
  • Arrival airport and connecting airport, if different
  • Airline or airlines, flight numbers if available, and whether both flights are on one ticket
  • Scheduled and updated arrival time, next departure time, and boarding cutoff if known
  • Arrival terminal/gate and departure terminal/gate, if known
  • Checked bags, mobility needs, children, pets, visas, customs, immigration, or security re-screening concerns
  • Phone battery, internet access, and whether the airline app is available

If key facts are unknown, create a plan with "verify now" steps rather than guessing.

Workflow

Step 1 - Build the Time Snapshot

Create a quick connection picture:

  • Current time and location from the user's message
  • Updated arrival or deplaning estimate
  • Next flight boarding and departure time
  • Estimated connection buffer
  • Known gate or terminal change
  • Any required immigration, customs, security, baggage claim, or shuttle step

If official times or rules are unknown, mark them as "verify with airline app, airport displays, or staff."

Step 2 - Classify the Connection

Use calm categories:

  • Green: likely manageable if the user moves directly and follows signs
  • Yellow: tight; reduce friction and ask staff for help early
  • Red: unlikely or already missed; start rebooking and fallback actions now
  • Unknown: missing critical details; verify gate, terminal, and rule constraints immediately

Avoid false certainty. State that this is a practical triage, not a guarantee.

Step 3 - Create the Gate-to-Gate Action Card

Prioritize safe, legal, rule-following moves:

  • Check updated gate and boarding status in the airline app or airport screens
  • Tell cabin crew or gate staff about the tight connection when appropriate
  • Deplane efficiently without pushing or blocking others
  • Follow official transfer signs; do not exit secure areas unless required
  • Use airport staff, information desks, or mobility assistance if needed
  • Keep boarding pass and passport or ID ready
  • Skip nonessential stops unless health, safety, or family needs require them
  • If re-screening or border control is required, follow the official queue and ask staff whether connection assistance exists

Step 4 - Prepare Help Scripts

Provide short scripts the user can read under stress:

  • Cabin crew script before landing or while taxiing
  • Arrival gate staff script
  • Transfer desk or airline app/chat script
  • Departure gate script if boarding is close
  • Rebooking script if the connection is missed

Scripts should include flight numbers, destination, current location, boarding time, checked bags, special needs, and one clear request.

Step 5 - List Fallback Moves

If the connection looks impossible or fails, list fallback actions:

  • Message or call the airline immediately, especially if still on the inbound aircraft or in a long line
  • Go to the transfer desk, customer service desk, or departure gate depending on airport layout
  • Ask whether the next flight, standby, reroute, partner airline, or overnight option is available
  • Ask what happens to checked bags and whether they are through-checked or need action
  • Save boarding passes, delay notices, receipts, and screenshots
  • Notify pickup, hotel, host, meeting contact, or onward transport
  • Check meal, hotel, transport, and compensation rules with the airline or official regulator where relevant, without assuming eligibility

Step 6 - Close with Verification and Safety

End with reminders:

  • Verify gate, terminal, boarding cutoff, transfer rules, and security requirements from official sources.
  • Follow airport and airline staff instructions.
  • Do not run through unsafe areas, bypass security, push through lines, or ignore immigration and customs requirements.
  • No plan guarantees a successful connection or rebooking outcome.

Output Format

Use this structure:

  1. Connection Snapshot - current situation and missing critical facts
  2. Triage Color - green, yellow, red, or unknown with a brief reason
  3. Next 10 Minutes - immediate gate-to-gate actions
  4. If You Reach the Departure Area - what to do at screens, gate, or transfer desk
  5. If You Miss It - rebooking and baggage fallback moves
  6. Scripts - short lines for crew, gate agent, transfer desk, airline chat, or customer service
  7. Verify Rules / No Guarantee - official-rule and safety reminders

Safety Boundaries

  • Verify airline, airport, security, customs, immigration, baggage, and boarding rules with official sources or staff.
  • Do not guarantee flight boarding, rebooking, baggage handling, compensation, hotel, meal vouchers, or any outcome.
  • Do not advise bypassing security, ignoring staff, pushing, entering restricted areas, abandoning dependents, or taking unsafe shortcuts.
  • Do not tell users to leave the secure area unless official signs or staff require it.
  • Keep urgent advice brief and prioritized when the user is in motion.
  • Treat disability access, children, pets, medication, and safety needs as higher priority than speed.

Acceptance Criteria

  1. Output captures itinerary, timing, gate or terminal, ticket, baggage, and rule-check facts when available.
  2. Output gives a time-boxed gate-to-gate action card.
  3. Output includes fallback moves for missed or impossible connections.
  4. Output includes short scripts for airline or airport staff.
  5. Output tells the user to verify airline and airport rules with official sources or staff.
  6. Output avoids guarantees and unsafe shortcuts.
  7. No web search, external API use, credentials, executable code, or file automation is required.

Example Prompts

  • "We land at 2:20 PM and my next flight boards until 2:45 PM, same airline, gate unknown. Help me build a connection rescue card right now."
  • "My inbound flight is delayed 40 minutes and I'll arrive after boarding starts for my connection. Both flights on one ticket with checked bags. What's my plan?"
  • "I have 55 minutes to go from international arrival to a domestic departure. Build me a connection card with scripts and fallback moves."

Examples

Example 1: Tight Same-Airline Connection

User says: "We land at 2:20, next flight boards until 2:45, same airline, gate unknown."

Skill guides: Create a yellow or unknown triage, tell the user to verify gate and boarding cutoff immediately, prepare to deplane efficiently, follow transfer signs, and use a short staff script.

Example 2: Delayed Inbound Flight

User says: "My inbound is delayed and I will arrive after boarding starts. Both flights are on one ticket and I checked a bag."

Skill guides: Build a red or yellow plan depending on exact timing, include airline-app rebooking steps, baggage questions, and scripts for crew and transfer desk.

Example 3: International Transfer

User says: "I have 55 minutes from international arrival to domestic departure."

Skill guides: Mark customs, immigration, baggage claim, and security re-screening as critical verification items. Do not promise feasibility; direct the user to official staff and fallback planning.