TeemeupAI

View saved version →

---
name: book-a-tee-time
description: Guides a full TeemeupAI golf tee-time booking from course search through payment checkout, including course-name disambiguation and the OAuth sign-in handoff. Use when the user wants to book, reserve, or check tee time availability at a golf course.
---

# Book a tee time

## Resolve the course

Prefer `course_id` when known. If only a name is given and a tool returns `status=similar`, show the candidate `courses` list and ask the user to pick one before continuing — do not guess.

## Steps

1. `book_tee_time(type=get_tee_time_list, course_id, players, date[, time])` → list of available slots (`tee_time_id`).
2. `book_tee_time(type=get_green_fees_list, ...same context, tee_time_id)` → green fee / cart products and a `device_id`. Carry `device_id` forward unchanged.
3. `book_tee_time(type=finalize_booking, ...same context, green_fees_selected, device_id)`.

## Handling finalize_booking results

- `status=sign_in_required`: recap the chosen slot and price, then direct the user to https://auth.teemeup.ai to sign in and complete booking. Do not say it is booked.
- `status=booking_awaiting_payment`: share the returned `booking_url` as the checkout link. Do not treat the booking as confirmed until payment completes. If `split_booking_context` is present, explain each payment group separately.
- `status=booked`: confirm with course, date, time, and players.

## Boundaries

- Never invent `tee_time_id`, `device_id`, or pricing — only use values returned by the tool in the prior step.
- This skill is for creating a new booking. For "what have I already booked," use the reservations lookup instead.

View saved version →

---
name: check-my-reservations
description: Looks up the signed-in user's own upcoming, past, or date-ranged tee-time reservations. Use when the user asks about their bookings, upcoming reservations, past rounds, or reservation history — not during a new-booking or availability search.
---

# Check my reservations

## When to use

Only call `get_my_reservations` when the user explicitly asks about their own bookings or history. Never call it as part of a new booking or tee-time availability flow.

## Steps

1. Pick a `filter`: `upcoming` (default), `past`, `date` (pass `date`), or `range` (pass `from_date` and `to_date`).
2. If the response is `status=sign_in_required`, tell the user to sign in at https://auth.teemeup.ai, then retry.
3. Summarize each reservation with course name, date, time, and players. Omit `booking_status` unless the user asks for it.

## Boundaries

- Identity comes from the signed-in session — never pass or infer a user id as an argument.
- Do not use this skill to start or modify a booking; it is read-only.

View saved version →

---
name: write-a-course-review
description: Resolves a golf course and saves the user's rating and review text, handling course-name disambiguation and the sign-in requirement. Use when the user wants to write, save, leave, or update a review for a golf course.
---

# Write a course review

## Steps

1. Resolve the course: prefer `course_id`. If only `course_name` is given, call `write_course_review` with it directly.
2. If the response is `status=similar`, show the `courses` candidate list and ask the user to pick one, then retry with the chosen `course_id`.
3. If the response is `status=sign_in_required`, tell the user to sign in at https://auth.teemeup.ai, then retry the same call once they confirm sign-in.
4. On success, confirm the saved rating and course. If `action` indicates an update, tell the user their existing review was updated rather than duplicated — `write_course_review` upserts one review per user per course.

## Boundaries

- Never invent a rating or review text the user didn't provide.
- Identity for the save comes from the signed-in session, not from a tool argument.