Bokun close date

Skill duongxthanh/claude-bokun-skills/skills/bokun-close-date

Stop accepting bookings (close out) one or more dates on your Bokun calendar. Use when the user wants to stop sales, close a date, lock the calendar, or block specific dates. Reversible; never cancels existing bookings.From its SKILL.md

Install

npx -y skills add duongxthanh/claude-bokun-skills --skill bokun-close-date

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.4 KB, 534 tokens by cl100k_base, as published. Nobody here has run it

Close out dates on Bokun

Dates to close: $ARGUMENTS

Read bokun.config.md in the working directory first (extranet URL, experiences, capacity). If it does not exist, tell the user to run /bokun-setup and stop. Also read the plugin's SAFETY.md.

If the config lists more than one experience and the user didn't specify which, ask before proceeding.

Steps

Parse dates from arguments into a YYYY-MM-DD list (assume the current year when omitted). No arguments → ask the user.
Set up the tab: tabs_context_mcp → reuse an existing extranet tab if present, else create one. If you land on a login page: stop and ask the user to log in — never enter credentials.
For each date: a. Navigate <extranet>/v2/bookings/calendar?date=<YYYY-MM-DD>&mode=week&capacityFilter=INCLUDE_NO_BOOKINGS → wait 4s → screenshot. b. Find the departure in that date's column (verify the column header: weekday + day number). It shows the experience name and x/<capacity>. c. If the departure already has a CLOSED badge → report "already closed", skip. d. If x > 0 (existing bookings): STOP and ask — "date D already has x booked guests. Close-out won't cancel them, but do you confirm closing this date?" Continue only on explicit yes. e. Click the departure → modal opens → click Close out (top right of the Edit availability area). f. Dialog "Are you sure you want to close the departure?" → leave the reason blank (unless the user gave one) → Confirm. g. Verify: toast "Successfully closed out departure" + Closed badge in the modal. Screenshot as evidence. h. Close the modal (X) before moving to the next date.
Report as a table: date | result | existing bookings. Remind the user that /bokun-open-date reverses this.

Never

Touch Experience editor → Calendar → "Remove this availability rule" — it permanently closes the entire calendar (SAFETY.md rule 1).
Log in yourself if the session expired — ask the user.

What ships with it

Read from the repository