Bokun setup

Skill duongxthanh/claude-bokun-skills/skills/bokun-setup

One-time setup for the bokun-* skills — discovers your Bokun vendor account through the browser (extranet subdomain, experiences and their IDs, departure type, capacity, currency, sales channels) and writes bokun.config.md that every other bokun skill reads. Use when bokun.config.md is missing, or after adding/changing experiences.From its SKILL.md

Install

npx -y skills add duongxthanh/claude-bokun-skills --skill bokun-setup

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

3.3 KB, 775 tokens by cl100k_base, as published. Nobody here has run it

Bokun vendor setup

Goal: write bokun.config.md into the current working directory. Every other bokun-* skill reads that file instead of hardcoding vendor data.

Read the plugin's SAFETY.md before touching the browser.

Steps

Locate the extranet. Use the URL from arguments if given. Otherwise call tabs_context_mcp and look for an open *.bokun.io tab. If neither exists, ask the user for their extranet URL (https://<vendor>.bokun.io).
Verify login. Navigate to <extranet>/v2/dashboard, wait 4s, screenshot. If you land on a login page: STOP and ask the user to log in manually. Never enter credentials.
Discover experiences. Navigate to the Experiences overview at <extranet>/v2/products/activities (left menu: Experiences → Experiences overview). The list table shows each experience's Bokun ID directly in the first column (#<ID>) along with status and Public/Private labels — no need to open each one. Note Private listings as such. Skip archived/draft ones unless the user says otherwise. (Fallback: opening an experience shows its ID in the editor URL, /app/experience-creation/<ID>/....)
Per experience, read:
- Departure type — editor → Availability ("Time, date, or pass"): date-only vs timed departures.
- Capacity — the availability rule's max participants (also visible as x/<capacity> on the Booking Calendar).
- Currency — from the Pricing step or dashboard widgets.
Sales channels (optional). Ask the user which public listings sell this product (own website, GetYourGuide, Viator, ...) and collect URLs — used by /bokun-cross-check. Skippable.
Confirm. Show everything as a table and let the user correct it.
Write bokun.config.md using the exact template below. Recommend adding it to .gitignore (it contains business data).
Smoke test. Navigate to <extranet>/v2/bookings/calendar?date=<today>&mode=week&capacityFilter=INCLUDE_NO_BOOKINGS and confirm departures render with x/<capacity>. Report success.

Config template (write exactly this shape)

# Bokun vendor config
<!-- Generated by /bokun-setup on <YYYY-MM-DD>. Read by all bokun-* skills. -->
<!-- Contains business data — keep out of public repos (.gitignore). -->

| Key | Value |
|---|---|
| Extranet | https://<vendor>.bokun.io |
| Vendor name | <name> |
| Currency | <ISO code, e.g. VND> |

## Experiences

| Experience | Bokun ID | Departure type | Capacity |
|---|---|---|---|
| <name> | <numeric id> | Date-only | <n> |

## Sales channels (used by /bokun-cross-check)

| Channel | URL |
|---|---|
| Website | <url or -> |
| <OTA name> | <url> |

## Vendor notes

- <anything unusual about this account>

Never

Enter credentials or automate login.
Change anything in the extranet — this skill only reads.

What ships with it

Read from the repository

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