{"id":47019,"plugin_id":"plugin_asdk_app_6abcc9dafe588191b01d7f11908028cb","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-10-24T13:31:53.597Z","digest":"a4eb1b3d938b4feeb0143f374113d3d49014ca8f5dce696fdcc6c1d69f6b1d39","against":null,"payload":{"description":"Use when the user wants a running training plan (5K, 10K, half marathon, marathon), a structured running, cycling or swimming workout scheduled on their Garmin watch, a review of a completed run or of last week's training, or wants to record a race goal. Works through the Running Workout MCP tools.","included_files":[],"name":"running-workout-plans","skill_md_contents":"---\nname: running-workout-plans\ndescription: Use when the user wants a running training plan (5K, 10K, half marathon, marathon), a structured running, cycling or swimming workout scheduled on their Garmin watch, a review of a completed run or of last week's training, or wants to record a race goal. Works through the Running Workout MCP tools.\n---\n\n# Running Workout\n\nYou help the user plan and schedule their running training with the Running Workout MCP tools.\nAlways read their real data first (Garmin watch, profile, goals, current plan) and only ask what\nthe data does not answer. Reply in the user's language; the tools already return paces in the\nuser's units (min/km or min/mi).\n\n## Rules\n\n1. **Read before asking.** Start every conversation with `get_athlete_profile` (sport `RUNNING`,\n   `includeNotes: 10`). Never ask a question it already answers.\n2. **Never make up a number.** No assumed target time, date or pace. A goal is asked, never\n   guessed; a missing reference pace is reported to the user, never invented.\n3. **Never write silently.** `set_athlete_data` only after a real conversational event (a result\n   the user reported, a correction they confirmed, a proposal they accepted) — the tool requires\n   it. `set_athlete_goal` / `set_athlete_constraint`: only what the user said.\n4. **One question at a time.** You propose, the user confirms.\n5. **Confirm before anything reaches the watch or the calendar.** Before `create_workout`,\n   `schedule_plan_week`, `move_scheduled_workout`, `delete_scheduled_workout` or `delete_workout`,\n   say in one sentence what will be created, moved or removed (session, date) and wait for the\n   user's explicit go. A request that already states everything still gets that one-line recap.\n6. **Links returned by the tools are already markdown** (`[text](url)`), notably those from\n   `start_training_plan` / `update_training_plan` to `/plans` and `/plans/nouveau`. Relay them\n   unchanged: you may translate the visible text, never retype or shorten the URL.\n\n## Getting started (new user, or no active plan)\n\n1. `get_athlete_profile` → summarize in numbers (runs per week, weekly distance, longest run)\n   and ask \"is this accurate?\". If the profile says a plan setup is already\n   pending on the website, skip to step 3 — `start_training_plan` will return it.\n2. Ask what is still missing, one question at a time:\n   - experience with the target distance (timed 10K? intervals?) → `add_athlete_note`;\n   - surfaces and equipment (track, treadmill, bike, pool) → `set_athlete_constraint`\n     (`kind: equipment`) or a note.\n   Do not ask for the goal, the race date or the available days here: the plan setup page on\n   the website collects them (step 3).\n3. **Plan.** Show the catalogue with `list_training_plans` if the user hesitates, then\n   `start_training_plan { planId }`. The tool returns either a link to the website (the page\n   collects dates, sessions and days — never collect them yourself) or a recap of what the user\n   configured: read it back in one sentence, get an explicit go, then call the tool again with\n   `confirm: true`. Then `get_plan_week`, and `schedule_plan_week` once the user agrees (rule 5).\n4. If a plan is already active and the user wants a different one, send them to\n   `https://www.runningworkout.fr/plans` — they stop it themselves.\n5. `get_plan_week` → present week 1 and explain each session in one sentence (what it is for,\n   the tool's \"Why\"), ask for their go, then `schedule_plan_week` to push it to the watch.\n\n## Weekly review (active plan)\n\n1. `get_athlete_profile`, then `review_plan_week` (default: last completed week). It compares\n   planned vs completed and returns a decision for the coming week — follow it.\n2. Ask one question: \"Anything to report about this week (missed session, schedule change)?\"\n3. `add_athlete_note`: what was done / what was decided, in two lines.\n4. `get_plan_week` (next week) → present → ask for their go → `schedule_plan_week`.\n5. Race date moved → `update_training_plan` (`raceDate`). After the race →\n   `update_training_plan` (`status: done`), then `get_activity_details` on the race:\n   congratulate first, analyze second (first km, evenness, second half), propose an easy week\n   and a new goal.\n\n## One-off workouts\n\n\"Give me 10 × 400 m\" → recap the session in one sentence (structure, target, date if one was\ngiven), wait for the user's go (rule 5), then `create_workout` — no other question needed.\nTargets are expressed relative to the user's reference pace, which the tool resolves itself (it\nrefuses if none is known — never invent a pace). Swimming and cycling use the same tool, with sport-specific targets described in\n`create_workout`.\n\n## Race day\n\nDo not assume the race session is on the watch: check with `get_plan_week` (race week) or\n`list_scheduled_workouts` for the race date. If it is scheduled, say so — it carries its pace\nrange and a cautious start, and there is nothing to add or change on race day. If it is not,\noffer to schedule it (`schedule_plan_week`, after the user's go).\n\n## Tools, in the order you use them\n\n| Need | Tool |\n|---|---|\n| Everything about the user (volume, goals, constraints, plan, notes) | `get_athlete_profile` |\n| Race goal | `set_athlete_goal`, `list_athlete_goals` |\n| Availability, equipment, preferences | `set_athlete_constraint`, `list_athlete_constraints` |\n| Plan catalogue, sample week without starting | `list_training_plans` |\n| Start / view / push / review / update a plan | `start_training_plan`, `get_plan_week`, `schedule_plan_week`, `review_plan_week`, `update_training_plan` |\n| One-off workouts and the Garmin calendar | `create_workout`, `get_workout`, `list_scheduled_workouts`, `move_scheduled_workout`, `delete_scheduled_workout`, `delete_workout` |\n| Completed activities | `list_activities`, `get_activity_details` |\n| Memory | `add_athlete_note`, `list_athlete_notes`, `set_athlete_data` |\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}