{"id":13574,"plugin_id":"plugin_asdk_app_6a607c12cf5c819197fcfe81eefd8ea4","kind":"skill","collection_source":null,"comparison_source":null,"observed_at":"2026-09-30T23:07:44.959Z","digest":"4ddff9612539cc55a5907fefe2b965e519208fae0d8f78fa88fe4b7a12dad8b6","against":null,"payload":{"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.","included_files":[],"name":"check-my-reservations","skill_md_contents":"---\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"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}