tourmind-com/Tourmind-Booking-Skills / skills/flight-booking-ai
flight-booking-ai
VerifiedUse when a user wants to resolve airports, search live flight offers, verify a selected airfare, create a flight booking, query a flight order, or safely create or query a third-party payment through TourMind.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 44.7 KB |
| agents/openai.yaml | config | 206 B |
| references/authentication.md | markdown | 5.0 KB |
| references/parameter_guide.md | markdown | 45.6 KB |
| references/passenger_details.md | markdown | 7.3 KB |
| references/response_templates.md | markdown | 24.1 KB |
references/authentication.md
View on GitHub# Authentication failure and recovery
Read this reference after an authentication rejection, after excluding a machine-readable `verify_offer` business `code == 20105`. That verification code means the token changed: keep the current credential, discard old quotations, and follow [token-change recovery](parameter_guide.md#token-change-recovery). It applies to either credential channel. Ordinary HTTP 401, `unauthorized`, or `invalid_token` results still invoke the existing authentication recovery; do not downgrade a rejected-token search to anonymous search.
## Clear the rejected credential and stop
Immediately clear the rejected credential from the recorded `{credentialFile}` from which it was loaded, whether that is the flight Skill's file or the sibling hotel Skill's file, and remove it from reusable request headers or client state. Stop the affected operation and do not retry it automatically. Do not print any credential while reading, clearing, or saving it.
Never reuse the rejected credential, send an empty or guessed header, silently switch channels, change the API host or endpoint, or fall back to the other Skill's Token during the same recovery attempt. Do not search another installation, workspace, archive, backup, environment variable, shell history, previous message, or account for replacement credentials. A request to hurry, accept risk, change the itinerary, or “try once” does not authorize another call with the rejected Token.
Public airport lookup remains available without a token. Tokenless flight search is available when no token is configured and no authentication-recovery stop is active; it must not bypass a rejected token. A public lookup or Skill update check does not prove flight authorization and does not resume the failed protected operation.
## Obtain and use a replacement token
Direct a personal-channel user to <https://auth.journione.ai> to obtain a new `uk_` token. Direct a business-channel user to <https://tourmind.com/user/skill-token> to obtain a new `sk_` token; if they do not have a business account, provide <https://tourmind.com/admin/skillSignup>. If the rejected credential's channel is unknown, present both choices without selecting one for the user.
When the user supplies a complete replacement beginning `uk_` or `sk_`, save it securely to `{baseDir}/skill_token.txt` without echoing it. The current flight Skill file becomes the primary shared credential because it is checked first. The prefix selects the channel, but receiving or saving the Token does not prove authorization and does not by itself authorize any endpoint call.
Do not invent a validation endpoint, call a server-internal verifier, or automatically issue a protected request solely because the replacement was saved. The replacement may be used for the next protected operation only when the user explicitly requests or approves that operation and its normal input validation, quotation freshness, channel, review, and confirmation requirements are satisfied. If the user explicitly asks to test the replacement, use only a documented read-only protected operation with complete valid inputs; never use `create_booking` or `create_payment` as a credential test.
Treat the official endpoint response as authoritative. First exclude verification `code == 20105`, which keeps the current credential and runs one refresh search followed by customer reselection. If the response instead returns any other HTTP 401, `unauthorized`, or `invalid_token`, clear the replacement credential and restart this recovery flow. Otherwise, handle the response under its normal success, business-error, or transport-error rules without claiming more authorization than the response establishes.
## Resume the business workflow safely
Replacing a token invalidates pre-order quotations, verification sessions, passenger/contact confirmations, and payment context as required by `SKILL.md`. Once authentication recovery permits the requested operation, a new `sk_` followed by a verification request authorizes the refresh search directly; show its new results and wait for a new selection. Otherwise obtain approval for a fresh search. Verify a newly selected quotation before any later booking. An existing order remains bound to its creation channel and requires a matching-prefix credential authorized to access it; never probe the other channel.
Never automatically replay `create_booking` or `create_payment` after authentication recovery. If an earlier creation result was ambiguous, reconcile it before considering another creation. Any later booking or payment creation must satisfy the complete current review and explicit-confirmation flow.
## Customer-facing response
Use the [authentication recovery template](response_templates.md#authentication-recovery). Select its operation outcome, authorization path, and order-state variables from actual evidence. If an existing order is known, retain its confirmed number and explain which follow-up action stopped. If an earlier creation is uncertain, retain that uncertainty. Do not show raw authentication errors or any token fragment.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |