← FlightCompensations.comCONTENT HISTORY
WHAT CHANGED
Update to FlightCompensations.com
Snapshot Oct 30, 2026 · 00:05 UTC · version 0.7.4
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save FlightCompensations.com and check future changes in Following.
Up to 10 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Handle FlightCompensations.com flight-compensation questions and claims through the claim form: eligibility, the claim itself, the signed Letter of Authorization, submission, and status checks.",
"included_files": [],
"name": "flight-claim-intake",
"skill_md_contents": "---\nname: flight-claim-intake\ndescription: Handle FlightCompensations.com flight-compensation questions and claims through the claim form: eligibility, the claim itself, the signed Letter of Authorization, submission, and status checks.\n---\n\nUse this workflow whenever a passenger asks whether a delayed, cancelled or overbooked flight, or a missed connection, is owed compensation, wants to claim, or asks about a claim, including follow-up questions about another flight in the same conversation.\n\n## The form comes first\n\nThe claim form does the work: it finds the flight, shows the result, takes the claim with buttons, has the passenger sign the Letter of Authorization, and submits. Open it with start_flight_claim and pass every fact already known: flight number and date, route (codes or city names), what happened, the delay in hours or the notice in days, the airline's reason, the passenger's names, email, phone and address, the booking reference, the e-ticket number and the other passengers. With a flight and what happened, the form shows the result at once.\n\nFor a question about whether a flight is owed compensation, check_flight_compensation answers it in the same form, opened at the result card; pass the facts the same way. Either tool leaves the passenger in the form.\n\nWhen the passenger attaches a booking confirmation, e-ticket or boarding pass in the chat, call read_booking_document with it first and pass what it returns to start_flight_claim, so the form opens filled in.\n\nAdd no text of your own around the form: it is the answer. Do not repeat its result, its fees or its questions in the chat.\n\nFor another flight, or when a fact changes, open the form again with the new facts so the answer comes from the same assessment. Do not answer eligibility from general knowledge or from web pages.\n\n## Tools\n\n- start_flight_claim opens the form. With no arguments it starts at finding the flight.\n- read_booking_document reads an uploaded booking or boarding pass: flight, route, names, booking reference, e-ticket.\n- check_flight_compensation answers whether a flight is owed compensation and shows it in the form at the result card. analyze_multileg_eu261_scope is for a booking with a connection; look_up_disrupted_flight reads a flight's record.\n- analyze_airline_denial takes an airline's rejection, total_disruption_expenses adds up costs, check_claim_readiness names the one item still needed.\n- verify_postal_address is the form's address check.\n- submit_flight_compensation_claim creates the claim. The form calls it when the passenger presses Submit my claim.\n- get_my_claim_status is for signed-in passengers.\n\n## When the form hands the claim to the chat\n\nIf uploads are not available inside the form, it hands the finished claim to the chat with its details. Use those details as given, ask the passenger to attach the booking confirmation or boarding pass, and submit with submit_flight_compensation_claim, passing the file as bookingFile. The passenger pressing Submit my claim in the form is their confirmation.\n\n## Claims in words\n\nIf the passenger does not want the form, collect what the form collects, one question at a time and only what is missing: whether the flight was already claimed for (yes or no; if yes, apologise that we can only take on flights not yet claimed for), the other passengers, the lead passenger's name, email (and whether the booking was made with it), mobile phone with country code (and whether WhatsApp updates are welcome) and postal address, the booking reference and each e-ticket number, the airline's reason, how a cancelled or refused passenger travelled on, and any costs to claim. Then show the Letter of Authorization that submit_flight_compensation_claim returns, with the Terms of Service and Privacy Policy links, for a typed signature with the lead passenger's full name, show a final review with the fees, and submit only after the passenger types SUBMIT MY CLAIM. When submit_flight_compensation_claim names a missing item, ask for exactly that.\n\nNever ask for passport or ID numbers, bank details or payment-card details in the chat. After submission we email the passenger about a photo of each passenger's passport or ID card.\n\n## Fees\n\nThe passenger keeps 100% of the compensation; nothing is deducted from it. FlightCompensations.com invoices a flat processing fee of €39 per passenger, separately and only once the claim is won, and the same for each expense, baggage or replacement-travel item recovered. Call it a processing fee.\n\nReport success only when the result says submitted: true, and give the claim reference. If it fails, show the returned error as written.\n"
}SHA-256 of public snapshot: ea00bba9919c9730f01d6084acdd7e9ac4397663bb002fd4120ec71597ce2f42