agentsclimarketplace
Sign in

Bokun booking

Skill duongxthanh/claude-bokun-skills/skills/bokun-booking

Look up a booking on Bokun by booking code or customer name — details, passenger list, and assisted cancel/refund (always confirmed first). Use when the user asks about a specific booking or customer, or wants to cancel one.From its SKILL.md

Install
npx -y skills add duongxthanh/claude-bokun-skills --skill bokun-booking

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.1 KB, 462 tokens by cl100k_base, as published. Nobody here has run it

Look up / manage a Bokun booking

Looking up: $ARGUMENTS

Read bokun.config.md first (extranet); missing → tell the user to run /bokun-setup and stop. Read the plugin's SAFETY.md — the cancel/refund rules below come from it.

Lookup

  1. Set up the tab (tabs_context_mcp; reuse or create; login page → stop, ask the user).
  2. Ways to find it (try in order):
    • Global search: <extranet>/v2/dashboard, click the Search box (Ctrl+K) → type the booking code / customer name → pick the result.
    • Sales feed: <extranet>/v2/bookings/sales-feed — scan if recent.
    • By date: if the departure date is known → Booking Calendar → click the departure → "Bookings" section in the modal + "Passenger list".
  3. Read the details: code, customer, date, pax, sales channel (which OTA / widget / manual), value, payment status. Use get_page_text on the detail page.
  4. Return a compact summary.

Cancel / refund — MANDATORY procedure

  1. Open the booking detail page, screenshot it.
  2. List everything for the user: code, customer, date, pax, amount, sales channel — and ask explicitly: cancel WITH refund or WITHOUT?
  3. Wait for a fresh written confirmation in chat. Never infer it from the original request.
  4. Only then cancel on the UI, picking exactly the refund option the user confirmed.
  5. ⚠️ OTA bookings (Viator, GetYourGuide, ...): warn the user to cancel from the OTA side / check that channel's policy first — cancelling in Bokun may not sync back fully.
  6. Screenshot the final status and report.

Never

  • Cancel/refund without a fresh per-action confirmation in chat.
  • Touch payment details / card charges.
  • Log in yourself if the session expired — ask the user.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Keep looking

Skills are one crate of 326,970. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.