← TeemeupCONTENT HISTORY

Update to Teemeup

Snapshot Oct 31, 2026 · 12:10 UTC · version 2.0.0

Collection source: downloaded plugin package. These snapshots do not have a confirmed matching collection source. Differences in file lists alone do not establish changes to the package.

WHAT CHANGED

Instructions updated for check-my-reservations

Full description — Now says: Opens the golfer's own upcoming or past tee-time reservations in the Teemeup app.

Observed in instructions or declared skills. Runtime behavior has not been tested.

Save Teemeup and check future changes in Following.

Up to 3 plugins free · no card required.

All fields and original values.

Full description

Before

Sep 30, 2026 · 23:07 UTC

Looks up the signed-in user's own upcoming, past, or date-ranged tee-time reservations.

After

Oct 31, 2026 · 12:10 UTC

Opens the golfer's own upcoming or past tee-time reservations in the Teemeup app.

Skill instructions

Before

Sep 30, 2026 · 23:07 UTC

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 se...

After

Oct 31, 2026 · 12:10 UTC

Opens the golfer's own upcoming or past tee-time reservations in the Teemeup app. Use when the user asks about their bookings, upcoming reservations, past rounds, or reservation history — not during a new-booking or availability search. ...

Compare saved observations

Download comparison JSON

SKILL.md text changes

− removed · + added

--- before
+++ after
@@ -1,21 +1,19 @@
 ---
 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.
+description: Opens the golfer's own upcoming or past tee-time reservations in the Teemeup app. 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.
+Reservations belong to a Teemeup account, and a tool call carries no sign-in, so they cannot be listed in the chat.
 
 ## 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.
+1. `get_my_reservations(filter)` — `upcoming` (default), `past`, `date` (with `date`), or `range` (with `from_date` and `to_date`).
+2. The result is `status=see_them_in_the_app` with a `bookings_url`. **Give the user that link.** It opens their reservations, signing them in first only if they are not already signed in.
 
 ## 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.
+- Never guess, list, or describe what the user has booked — this tool returns no reservation data.
+- Do not ask them to sign in somewhere and call the tool again; the answer would be the same.
+- Not for finding new tee times. For that, use the booking skill.
Full technical diff · 2 changed fields

changed /description

BEFORE
"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."
AFTER
"Opens the golfer's own upcoming or past tee-time reservations in the Teemeup app. Use when the user asks about their bookings, upcoming reservations, past rounds, or reservation history — not during a new-booking or availability search."

changed /skill_md_contents

BEFORE
"---\nname: check-my-reservations\ndescription: 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.\n---\n\n# Check my reservations\n\n## When to use\n\nOnly 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.\n\n## Steps\n\n1. Pick a `filter`: `upcoming` (default), `past`, `date` (pass `date`), or `range` (pass `from_date` and `to_date`).\n2. If the response is `status=sign_in_required`, tell the user to sign in at https://auth.teemeup.ai, then retry.\n3. Summarize each reservation with course name, date, time, and players. Omit `booking_status` unless the user asks for it.\n\n## Boundaries\n\n- Identity comes from the signed-in session — never pass or infer a user id as an argument.\n- Do not use this skill to start or modify a booking; it is read-only.\n"
AFTER
"---\nname: check-my-reservations\ndescription: Opens the golfer's own upcoming or past tee-time reservations in the Teemeup app. Use when the user asks about their bookings, upcoming reservations, past rounds, or reservation history — not during a new-booking or availability search.\n---\n\n# Check my reservations\n\nReservations belong to a Teemeup account, and a tool call carries no sign-in, so they cannot be listed in the chat.\n\n## Steps\n\n1. `get_my_reservations(filter)` — `upcoming` (default), `past`, `date` (with `date`), or `range` (with `from_date` and `to_date`).\n2. The result is `status=see_them_in_the_app` with a `bookings_url`. **Give the user that link.** It opens their reservations, signing them in first only if they are not already signed in.\n\n## Boundaries\n\n- Never guess, list, or describe what the user has booked — this tool returns no reservation data.\n- Do not ask them to sign in somewhere and call the tool again; the answer would be the same.\n- Not for finding new tee times. For that, use the booking skill.\n"
Full snapshot data
{
  "description": "Opens the golfer's own upcoming or past tee-time reservations in the Teemeup app. Use when the user asks about their bookings, upcoming reservations, past rounds, or reservation history — not during a new-booking or availability search.",
  "included_files": [],
  "name": "check-my-reservations",
  "skill_md_contents": "---\nname: check-my-reservations\ndescription: Opens the golfer's own upcoming or past tee-time reservations in the Teemeup app. Use when the user asks about their bookings, upcoming reservations, past rounds, or reservation history — not during a new-booking or availability search.\n---\n\n# Check my reservations\n\nReservations belong to a Teemeup account, and a tool call carries no sign-in, so they cannot be listed in the chat.\n\n## Steps\n\n1. `get_my_reservations(filter)` — `upcoming` (default), `past`, `date` (with `date`), or `range` (with `from_date` and `to_date`).\n2. The result is `status=see_them_in_the_app` with a `bookings_url`. **Give the user that link.** It opens their reservations, signing them in first only if they are not already signed in.\n\n## Boundaries\n\n- Never guess, list, or describe what the user has booked — this tool returns no reservation data.\n- Do not ask them to sign in somewhere and call the tool again; the answer would be the same.\n- Not for finding new tee times. For that, use the booking skill.\n"
}

SHA-256 of public snapshot: e7bcc0a288acfe0b315ad46c4a2abb77e11afbaee22fa248d3ed720f05e7d574