{"id":76916,"plugin_id":"plugin_asdk_app_6a7b250ad83c8191a519b763350af4e9","kind":"skill","collection_source":"plugin_package","comparison_source":"plugin_package","observed_at":"2026-11-03T00:11:49.045Z","digest":"c5b3ba2385eefc988495a9ae27999604343ad32de86962139ebb806edbed143c","against":40402,"payload":{"description":"Plan, schedule, or change a MoveMate workout — a session for a given day, a superset or circuit, a saved workout (\"My workouts\") created or edited, or an edit to one already on the schedule. Reads recent training, picks real exercises from the user's library, proposes the session, and writes only after the user agrees. Not for reporting on past training — use review-training for that.","included_files":[],"name":"plan-workout","skill_md_contents":"---\nname: plan-workout\ndescription: Plan, schedule, or change a MoveMate workout — a session for a given day, a superset or circuit, a saved workout (\"My workouts\") created or edited, or an edit to one already on the schedule. Reads recent training, picks real exercises from the user's library, proposes the session, and writes only after the user agrees. Not for reporting on past training — use review-training for that.\n---\n\n# Plan a workout in MoveMate\n\nScheduling writes to the user's real training calendar. Propose first, write once, and never invent an ID or a number.\n\n## 1. Read before you plan\n\nCall these first — planning without them produces a session that ignores what the user actually does:\n\n- `get_training_stats` (`period`: `last_7d` | `last_30d` | `last_90d` | `last_year` | `all_time`) — volume, frequency, streak, and which muscle groups are already covered this week.\n- `get_recent_workouts` — what the user actually managed last time, set by set. Build the next session on these numbers: add reps or a set to what they completed, not to what was on paper. Narrow with `exercise_name` to see one movement across its last few sessions, and check `completed_sets` against `planned_sets` before repeating a target they already missed. For bodyweight work this is the only source of the number that matters — total reps.\n- `list_planned_workouts` — what is already scheduled. **Never put a second workout on a day that already has one** unless the user explicitly asks for two.\n- `get_body_profile` — height, weight, age, fitness level, goals, available equipment. Takes no arguments.\n- `get_personal_records` — only when the user's request is about pushing a specific lift.\n\nIf the user named a day, resolve it against their timezone (`get_profile` returns it), not yours.\n\n## 2. Pick real exercises\n\nEvery `exercise_id` must come from `search_exercises` (`query` or `queries`, `muscle_group`, `equipment`, `limit`) or from `create_custom_exercise`. Look up all the exercises of a session in one call — pass their names together in `queries` — rather than one call per exercise. `search_exercises` shows the user nothing; use `show_exercises` only when the user asks to see exercise options. **Never write an ID from memory, and do not carry one over from an earlier conversation** — look it up again. Custom exercises in particular exist only for the user who created them.\n\nIf nothing in the library matches what the user described, create it with `create_custom_exercise` (`name`, optional `muscle_group`, `equipment`, `notes`) rather than substituting a different movement silently. If you do substitute, say so.\n\nRespect the equipment in `get_body_profile`. Do not program a barbell session for someone who has dumbbells only.\n\n## 3. Weights, reps and units\n\n- `target_weight` is **always kilograms**. If the user speaks in pounds, convert (`lb / 2.20462`) before sending, and keep speaking pounds back to them.\n- Base loads on `get_recent_workouts`, `get_exercise_progression` or `get_personal_records` for that exercise. A weight far above the user's history is rejected: the server clamps anything over 3× their last known weight and returns a warning.\n- For an unloaded movement, progress the **reps**, not the weight: send `target_reps` per set and leave `target_weight` off entirely rather than inventing a load.\n- Limits: at most 15 exercises per workout, at most 10 sets per exercise, and the date must be within 120 days.\n- Label sets with `set_type` when they are not plain working sets. `\"warmup\"` for preparatory sets, `\"failure\"` for a set meant to be taken to failure, `\"drop\"` for a set at a reduced load immediately following another. The default is `\"normal\"` and can be left off. Warm-ups and drop sets are excluded from volume, effort averages and the weight progression, so labelling them correctly is what keeps the user's numbers honest. (`is_warmup: true` still works but is deprecated — prefer `set_type: \"warmup\"`.)\n\n## 4. Supersets and circuits\n\nA superset is two or more exercises performed back-to-back with only a short changeover, then a rest. A circuit is the whole workout as one such group. Reach for them when the user is short on time, or when pairing opposing muscle groups (push/pull, quad/hamstring).\n\nGroup exercises by giving them the same `superset_group` label — `\"A\"` for the first pair, `\"B\"` for the second. Then:\n\n- **Members sharing a label MUST be adjacent in the `exercises` array, in the order they are performed.** Membership is defined by position in the list, nothing else. Never interleave (`\"A\"`, `\"B\"`, `\"A\"`) and never separate members with an ungrouped exercise. Getting this wrong does not fail the call — the members are pulled together and a warning comes back — but the resulting order is not what you intended.\n- A label used by only one exercise is not a superset and is dropped.\n- `superset_transition_seconds` is the pause **between** movements inside the group. Use `0` for a true circuit. Omit it to let the app apply its own short default. One value applies to the whole group.\n- **Whole-workout circuit:** give every exercise the same label and set `superset_transition_seconds: 0`.\n- Labels are replaced by internal IDs when saved. Never reuse a label read back from a response.\n\n## 5. Propose, then ask\n\nShow the session in chat — exercises, sets, reps, target weights, and any grouping — and **ask before scheduling it**. Do not call `create_planned_workout` on your own initiative because the user described a goal.\n\n## 6. Schedule it\n\n`create_planned_workout` with:\n\n- `scheduled_for` — local wall-clock time in the user's timezone with **no offset**: `2026-09-01` or `2026-09-01T18:00:00`. A trailing `Z` drifts the day for users west of UTC.\n- `client_request_id` — a **new** UUID for each new workout. Reuse the same value only when retrying a call you could not confirm; a repeat with the same ID returns the existing workout instead of creating a duplicate.\n\nRead the `warnings` in the response. They describe what the server changed about your input — a clamped weight, a regrouped superset — and they tell you what to do differently on the next call.\n\nReport back with the `web_url` from the response. The `deep_link` (`movemate://…`) does not render as a clickable link in chat.\n\n### Scheduling a workout that already exists\n\nIf the user names one of their saved workouts (\"schedule my chest day for Friday\") or a library workout, find it with `list_workouts` (`type: \"custom\"` for their own) and pass its `workout_id` to `create_planned_workout` with `scheduled_for` — **no** `title`, `notes` or `exercises`. The session links to that workout, as scheduling it in the app does. Do not rebuild its exercises into a new workout: that creates a duplicate in the user's saved workouts.\n\n## 7. Saved workouts (\"My workouts\")\n\nA saved workout is a reusable routine with no date. Sessions scheduled from it link to it.\n\n- `create_custom_workout` (`title`, `exercises`, optional `notes`) saves a new one. Propose it and get agreement first, as in §5.\n- `update_custom_workout` changes one of the user's own saved workouts. **Every scheduled session that uses it changes too**; the response gives the count in `upcoming_sessions`, so tell the user. Library workouts cannot be changed — save an edited copy with `create_custom_workout` instead.\n\n## 8. Changing a workout's exercises\n\nEvery tool that writes exercises — `update_custom_workout` and `update_planned_workout` — **replaces the whole list**: anything you leave out is deleted, and any superset labels you do not re-send are ungrouped.\n\nSo **always call `get_workout_details` first** and start from what it returns. It gives every exercise with its `exercise_id`, sets, targets, rest and superset letters in exactly the shape the write tools accept. Change only what the user asked for — insert the new exercise at the right position, swap or drop the one they named — and send everything else back unchanged, superset letters included. Never rebuild the list from memory or from the exercise names in `list_workouts`.\n\nTo add \"bench press after the barbell press\" to \"Chest day\": `list_workouts` → `get_workout_details` → show the user the new order → `update_custom_workout` with the full list.\n\n## 9. Changing or cancelling a scheduled session\n\n`update_planned_workout` reschedules a session or changes its reminder; only that session moves. Its `title`, `notes` and `exercises` belong to the workout the session uses: for a saved workout, that changes the saved workout and all its sessions; for a library workout, the user's sessions switch to their own edited copy (use the new `workout_id` it returns from then on).\n\nThe same `workout_id` can be on the calendar several times (a weekly repeat, or a saved workout scheduled twice). Pass `session_date` — the date of the session from `list_planned_workouts` — to choose which one. Without it the next upcoming session is used, and a warning says so.\n\nOnly sessions still marked `planned` can be cancelled, and nothing already done can be changed.\n\nTo cancel, use `delete_planned_workout` (with `session_date` if needed). It removes only that session — a saved workout stays in the user's workouts. Confirm with the user first.\n\n## Limits\n\nOn a free account, chat can schedule a session only while there are fewer than 10 upcoming ones, save a workout only while the account has fewer than 10 saved workouts, and create a custom exercise only while it has fewer than 20. Every account also has a per-minute and per-hour cap on changes. A refusal for any of these says so in plain words: tell the user, and **do not retry** — the same call fails the same way until they make room or the wait passes.\n\n## Never\n\n- Invent an `exercise_id`, a personal record, or a training number the tools did not return.\n- Schedule, change, or cancel anything without the user agreeing to that specific action.\n- Give medical, injury-rehabilitation, or diagnostic advice. If the user describes pain or an injury, say plainly that this needs a professional, and offer to plan around it only if they ask.\n"},"changes":[{"path":"/skill_md_contents","type":"changed","before":"---\nname: plan-workout\ndescription: Plan, schedule, or change a MoveMate workout — a session for a given day, a superset or circuit, a saved workout (\"My workouts\") created or edited, or an edit to one already on the schedule. Reads recent training, picks real exercises from the user's library, proposes the session, and writes only after the user agrees. Not for reporting on past training — use review-training for that.\n---\n\n# Plan a workout in MoveMate\n\nScheduling writes to the user's real training calendar. Propose first, write once, and never invent an ID or a number.\n\n## 1. Read before you plan\n\nCall these first — planning without them produces a session that ignores what the user actually does:\n\n- `get_training_stats` (`period`: `last_7d` | `last_30d` | `last_90d` | `last_year` | `all_time`) — volume, frequency, streak, and which muscle groups are already covered this week.\n- `get_recent_workouts` — what the user actually managed last time, set by set. Build the next session on these numbers: add reps or a set to what they completed, not to what was on paper. Narrow with `exercise_name` to see one movement across its last few sessions, and check `completed_sets` against `planned_sets` before repeating a target they already missed. For bodyweight work this is the only source of the number that matters — total reps.\n- `list_planned_workouts` — what is already scheduled. **Never put a second workout on a day that already has one** unless the user explicitly asks for two.\n- `get_body_profile` — height, weight, age, fitness level, goals, available equipment. Takes no arguments.\n- `get_personal_records` — only when the user's request is about pushing a specific lift.\n\nIf the user named a day, resolve it against their timezone (`get_profile` returns it), not yours.\n\n## 2. Pick real exercises\n\nEvery `exercise_id` must come from `search_exercises` (`query`, `muscle_group`, `equipment`, `limit`) or from `create_custom_exercise`. **Never write an ID from memory, and do not carry one over from an earlier conversation** — look it up again. Custom exercises in particular exist only for the user who created them.\n\nIf nothing in the library matches what the user described, create it with `create_custom_exercise` (`name`, optional `muscle_group`, `equipment`, `notes`) rather than substituting a different movement silently. If you do substitute, say so.\n\nRespect the equipment in `get_body_profile`. Do not program a barbell session for someone who has dumbbells only.\n\n## 3. Weights, reps and units\n\n- `target_weight` is **always kilograms**. If the user speaks in pounds, convert (`lb / 2.20462`) before sending, and keep speaking pounds back to them.\n- Base loads on `get_recent_workouts`, `get_exercise_progression` or `get_personal_records` for that exercise. A weight far above the user's history is rejected: the server clamps anything over 3× their last known weight and returns a warning.\n- For an unloaded movement, progress the **reps**, not the weight: send `target_reps` per set and leave `target_weight` off entirely rather than inventing a load.\n- Limits: at most 15 exercises per workout, at most 10 sets per exercise, and the date must be within 120 days.\n- Label sets with `set_type` when they are not plain working sets. `\"warmup\"` for preparatory sets, `\"failure\"` for a set meant to be taken to failure, `\"drop\"` for a set at a reduced load immediately following another. The default is `\"normal\"` and can be left off. Warm-ups and drop sets are excluded from volume, effort averages and the weight progression, so labelling them correctly is what keeps the user's numbers honest. (`is_warmup: true` still works but is deprecated — prefer `set_type: \"warmup\"`.)\n\n## 4. Supersets and circuits\n\nA superset is two or more exercises performed back-to-back with only a short changeover, then a rest. A circuit is the whole workout as one such group. Reach for them when the user is short on time, or when pairing opposing muscle groups (push/pull, quad/hamstring).\n\nGroup exercises by giving them the same `superset_group` label — `\"A\"` for the first pair, `\"B\"` for the second. Then:\n\n- **Members sharing a label MUST be adjacent in the `exercises` array, in the order they are performed.** Membership is defined by position in the list, nothing else. Never interleave (`\"A\"`, `\"B\"`, `\"A\"`) and never separate members with an ungrouped exercise. Getting this wrong does not fail the call — the members are pulled together and a warning comes back — but the resulting order is not what you intended.\n- A label used by only one exercise is not a superset and is dropped.\n- `superset_transition_seconds` is the pause **between** movements inside the group. Use `0` for a true circuit. Omit it to let the app apply its own short default. One value applies to the whole group.\n- **Whole-workout circuit:** give every exercise the same label and set `superset_transition_seconds: 0`.\n- Labels are replaced by internal IDs when saved. Never reuse a label read back from a response.\n\n## 5. Propose, then ask\n\nShow the session in chat — exercises, sets, reps, target weights, and any grouping — and **ask before scheduling it**. Do not call `create_planned_workout` on your own initiative because the user described a goal.\n\n## 6. Schedule it\n\n`create_planned_workout` with:\n\n- `scheduled_for` — local wall-clock time in the user's timezone with **no offset**: `2026-09-01` or `2026-09-01T18:00:00`. A trailing `Z` drifts the day for users west of UTC.\n- `client_request_id` — a **new** UUID for each new workout. Reuse the same value only when retrying a call you could not confirm; a repeat with the same ID returns the existing workout instead of creating a duplicate.\n\nRead the `warnings` in the response. They describe what the server changed about your input — a clamped weight, a regrouped superset — and they tell you what to do differently on the next call.\n\nReport back with the `web_url` from the response. The `deep_link` (`movemate://…`) does not render as a clickable link in chat.\n\n### Scheduling a workout that already exists\n\nIf the user names one of their saved workouts (\"schedule my chest day for Friday\") or a library workout, find it with `list_workouts` (`type: \"custom\"` for their own) and pass its `workout_id` to `create_planned_workout` with `scheduled_for` — **no** `title`, `notes` or `exercises`. The session links to that workout, as scheduling it in the app does. Do not rebuild its exercises into a new workout: that creates a duplicate in the user's saved workouts.\n\n## 7. Saved workouts (\"My workouts\")\n\nA saved workout is a reusable routine with no date. Sessions scheduled from it link to it.\n\n- `create_custom_workout` (`title`, `exercises`, optional `notes`) saves a new one. Propose it and get agreement first, as in §5.\n- `update_custom_workout` changes one of the user's own saved workouts. **Every scheduled session that uses it changes too**; the response gives the count in `upcoming_sessions`, so tell the user. Library workouts cannot be changed — save an edited copy with `create_custom_workout` instead.\n\n## 8. Changing a workout's exercises\n\nEvery tool that writes exercises — `update_custom_workout` and `update_planned_workout` — **replaces the whole list**: anything you leave out is deleted, and any superset labels you do not re-send are ungrouped.\n\nSo **always call `get_workout_details` first** and start from what it returns. It gives every exercise with its `exercise_id`, sets, targets, rest and superset letters in exactly the shape the write tools accept. Change only what the user asked for — insert the new exercise at the right position, swap or drop the one they named — and send everything else back unchanged, superset letters included. Never rebuild the list from memory or from the exercise names in `list_workouts`.\n\nTo add \"bench press after the barbell press\" to \"Chest day\": `list_workouts` → `get_workout_details` → show the user the new order → `update_custom_workout` with the full list.\n\n## 9. Changing or cancelling a scheduled session\n\n`update_planned_workout` reschedules a session or changes its reminder; only that session moves. Its `title`, `notes` and `exercises` belong to the workout the session uses: for a saved workout, that changes the saved workout and all its sessions; for a library workout, the user's sessions switch to their own edited copy (use the new `workout_id` it returns from then on).\n\nThe same `workout_id` can be on the calendar several times (a weekly repeat, or a saved workout scheduled twice). Pass `session_date` — the date of the session from `list_planned_workouts` — to choose which one. Without it the next upcoming session is used, and a warning says so.\n\nOnly sessions still marked `planned` can be cancelled, and nothing already done can be changed.\n\nTo cancel, use `delete_planned_workout` (with `session_date` if needed). It removes only that session — a saved workout stays in the user's workouts. Confirm with the user first.\n\n## Limits\n\nOn a free account, chat can schedule a session only while there are fewer than 10 upcoming ones, save a workout only while the account has fewer than 10 saved workouts, and create a custom exercise only while it has fewer than 20. Every account also has a per-minute and per-hour cap on changes. A refusal for any of these says so in plain words: tell the user, and **do not retry** — the same call fails the same way until they make room or the wait passes.\n\n## Never\n\n- Invent an `exercise_id`, a personal record, or a training number the tools did not return.\n- Schedule, change, or cancel anything without the user agreeing to that specific action.\n- Give medical, injury-rehabilitation, or diagnostic advice. If the user describes pain or an injury, say plainly that this needs a professional, and offer to plan around it only if they ask.\n","after":"---\nname: plan-workout\ndescription: Plan, schedule, or change a MoveMate workout — a session for a given day, a superset or circuit, a saved workout (\"My workouts\") created or edited, or an edit to one already on the schedule. Reads recent training, picks real exercises from the user's library, proposes the session, and writes only after the user agrees. Not for reporting on past training — use review-training for that.\n---\n\n# Plan a workout in MoveMate\n\nScheduling writes to the user's real training calendar. Propose first, write once, and never invent an ID or a number.\n\n## 1. Read before you plan\n\nCall these first — planning without them produces a session that ignores what the user actually does:\n\n- `get_training_stats` (`period`: `last_7d` | `last_30d` | `last_90d` | `last_year` | `all_time`) — volume, frequency, streak, and which muscle groups are already covered this week.\n- `get_recent_workouts` — what the user actually managed last time, set by set. Build the next session on these numbers: add reps or a set to what they completed, not to what was on paper. Narrow with `exercise_name` to see one movement across its last few sessions, and check `completed_sets` against `planned_sets` before repeating a target they already missed. For bodyweight work this is the only source of the number that matters — total reps.\n- `list_planned_workouts` — what is already scheduled. **Never put a second workout on a day that already has one** unless the user explicitly asks for two.\n- `get_body_profile` — height, weight, age, fitness level, goals, available equipment. Takes no arguments.\n- `get_personal_records` — only when the user's request is about pushing a specific lift.\n\nIf the user named a day, resolve it against their timezone (`get_profile` returns it), not yours.\n\n## 2. Pick real exercises\n\nEvery `exercise_id` must come from `search_exercises` (`query` or `queries`, `muscle_group`, `equipment`, `limit`) or from `create_custom_exercise`. Look up all the exercises of a session in one call — pass their names together in `queries` — rather than one call per exercise. `search_exercises` shows the user nothing; use `show_exercises` only when the user asks to see exercise options. **Never write an ID from memory, and do not carry one over from an earlier conversation** — look it up again. Custom exercises in particular exist only for the user who created them.\n\nIf nothing in the library matches what the user described, create it with `create_custom_exercise` (`name`, optional `muscle_group`, `equipment`, `notes`) rather than substituting a different movement silently. If you do substitute, say so.\n\nRespect the equipment in `get_body_profile`. Do not program a barbell session for someone who has dumbbells only.\n\n## 3. Weights, reps and units\n\n- `target_weight` is **always kilograms**. If the user speaks in pounds, convert (`lb / 2.20462`) before sending, and keep speaking pounds back to them.\n- Base loads on `get_recent_workouts`, `get_exercise_progression` or `get_personal_records` for that exercise. A weight far above the user's history is rejected: the server clamps anything over 3× their last known weight and returns a warning.\n- For an unloaded movement, progress the **reps**, not the weight: send `target_reps` per set and leave `target_weight` off entirely rather than inventing a load.\n- Limits: at most 15 exercises per workout, at most 10 sets per exercise, and the date must be within 120 days.\n- Label sets with `set_type` when they are not plain working sets. `\"warmup\"` for preparatory sets, `\"failure\"` for a set meant to be taken to failure, `\"drop\"` for a set at a reduced load immediately following another. The default is `\"normal\"` and can be left off. Warm-ups and drop sets are excluded from volume, effort averages and the weight progression, so labelling them correctly is what keeps the user's numbers honest. (`is_warmup: true` still works but is deprecated — prefer `set_type: \"warmup\"`.)\n\n## 4. Supersets and circuits\n\nA superset is two or more exercises performed back-to-back with only a short changeover, then a rest. A circuit is the whole workout as one such group. Reach for them when the user is short on time, or when pairing opposing muscle groups (push/pull, quad/hamstring).\n\nGroup exercises by giving them the same `superset_group` label — `\"A\"` for the first pair, `\"B\"` for the second. Then:\n\n- **Members sharing a label MUST be adjacent in the `exercises` array, in the order they are performed.** Membership is defined by position in the list, nothing else. Never interleave (`\"A\"`, `\"B\"`, `\"A\"`) and never separate members with an ungrouped exercise. Getting this wrong does not fail the call — the members are pulled together and a warning comes back — but the resulting order is not what you intended.\n- A label used by only one exercise is not a superset and is dropped.\n- `superset_transition_seconds` is the pause **between** movements inside the group. Use `0` for a true circuit. Omit it to let the app apply its own short default. One value applies to the whole group.\n- **Whole-workout circuit:** give every exercise the same label and set `superset_transition_seconds: 0`.\n- Labels are replaced by internal IDs when saved. Never reuse a label read back from a response.\n\n## 5. Propose, then ask\n\nShow the session in chat — exercises, sets, reps, target weights, and any grouping — and **ask before scheduling it**. Do not call `create_planned_workout` on your own initiative because the user described a goal.\n\n## 6. Schedule it\n\n`create_planned_workout` with:\n\n- `scheduled_for` — local wall-clock time in the user's timezone with **no offset**: `2026-09-01` or `2026-09-01T18:00:00`. A trailing `Z` drifts the day for users west of UTC.\n- `client_request_id` — a **new** UUID for each new workout. Reuse the same value only when retrying a call you could not confirm; a repeat with the same ID returns the existing workout instead of creating a duplicate.\n\nRead the `warnings` in the response. They describe what the server changed about your input — a clamped weight, a regrouped superset — and they tell you what to do differently on the next call.\n\nReport back with the `web_url` from the response. The `deep_link` (`movemate://…`) does not render as a clickable link in chat.\n\n### Scheduling a workout that already exists\n\nIf the user names one of their saved workouts (\"schedule my chest day for Friday\") or a library workout, find it with `list_workouts` (`type: \"custom\"` for their own) and pass its `workout_id` to `create_planned_workout` with `scheduled_for` — **no** `title`, `notes` or `exercises`. The session links to that workout, as scheduling it in the app does. Do not rebuild its exercises into a new workout: that creates a duplicate in the user's saved workouts.\n\n## 7. Saved workouts (\"My workouts\")\n\nA saved workout is a reusable routine with no date. Sessions scheduled from it link to it.\n\n- `create_custom_workout` (`title`, `exercises`, optional `notes`) saves a new one. Propose it and get agreement first, as in §5.\n- `update_custom_workout` changes one of the user's own saved workouts. **Every scheduled session that uses it changes too**; the response gives the count in `upcoming_sessions`, so tell the user. Library workouts cannot be changed — save an edited copy with `create_custom_workout` instead.\n\n## 8. Changing a workout's exercises\n\nEvery tool that writes exercises — `update_custom_workout` and `update_planned_workout` — **replaces the whole list**: anything you leave out is deleted, and any superset labels you do not re-send are ungrouped.\n\nSo **always call `get_workout_details` first** and start from what it returns. It gives every exercise with its `exercise_id`, sets, targets, rest and superset letters in exactly the shape the write tools accept. Change only what the user asked for — insert the new exercise at the right position, swap or drop the one they named — and send everything else back unchanged, superset letters included. Never rebuild the list from memory or from the exercise names in `list_workouts`.\n\nTo add \"bench press after the barbell press\" to \"Chest day\": `list_workouts` → `get_workout_details` → show the user the new order → `update_custom_workout` with the full list.\n\n## 9. Changing or cancelling a scheduled session\n\n`update_planned_workout` reschedules a session or changes its reminder; only that session moves. Its `title`, `notes` and `exercises` belong to the workout the session uses: for a saved workout, that changes the saved workout and all its sessions; for a library workout, the user's sessions switch to their own edited copy (use the new `workout_id` it returns from then on).\n\nThe same `workout_id` can be on the calendar several times (a weekly repeat, or a saved workout scheduled twice). Pass `session_date` — the date of the session from `list_planned_workouts` — to choose which one. Without it the next upcoming session is used, and a warning says so.\n\nOnly sessions still marked `planned` can be cancelled, and nothing already done can be changed.\n\nTo cancel, use `delete_planned_workout` (with `session_date` if needed). It removes only that session — a saved workout stays in the user's workouts. Confirm with the user first.\n\n## Limits\n\nOn a free account, chat can schedule a session only while there are fewer than 10 upcoming ones, save a workout only while the account has fewer than 10 saved workouts, and create a custom exercise only while it has fewer than 20. Every account also has a per-minute and per-hour cap on changes. A refusal for any of these says so in plain words: tell the user, and **do not retry** — the same call fails the same way until they make room or the wait passes.\n\n## Never\n\n- Invent an `exercise_id`, a personal record, or a training number the tools did not return.\n- Schedule, change, or cancel anything without the user agreeing to that specific action.\n- Give medical, injury-rehabilitation, or diagnostic advice. If the user describes pain or an injury, say plainly that this needs a professional, and offer to plan around it only if they ask.\n"}],"summary":"Fields changed: 1. /skill_md_contents.","summary_kind":"deterministic","summary_metadata":{}}