{"id":27352,"plugin_id":"plugin_asdk_app_6ac4370294108191bd78786b8081ccf6","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-10-07T00:28:34.317Z","digest":"2014415f8e96c7290b8996cb0a992e45a2a9ba61b32abd17e333ebfd339afc72","against":null,"payload":{"description":"Debrief a training session or recent block from the athlete's Fit File Forge data. Use when the user asks how a run, ride, swim or workout went, whether they hit their reps or targets, why heart rate was high, or how a session compares with similar ones.","included_files":[],"name":"training-debrief","skill_md_contents":"---\nname: training-debrief\ndescription: Debrief a training session or recent block from the athlete's Fit File Forge data. Use when the user asks how a run, ride, swim or workout went, whether they hit their reps or targets, why heart rate was high, or how a session compares with similar ones.\n---\n\nTo debrief a session:\n\n1. Find it with `find_activities` (by date, sport or name) unless the user gave one. If more than one fits, ask which.\n2. Call `get_athlete` once per conversation for the athlete's thresholds, units and what they allowed when connecting.\n3. Read it fully: `get_activity` with depth `full` (summary, laps, zones, best efforts), then `get_activity_splits` (by `km` or `mi` for steady sessions, by `lap` for intervals).\n4. If the athlete allowed detailed data, call `get_activity_series` for the channels the question needs (heart rate, pace or power, elevation) and chart heart rate against pace or power and elevation where you can. Compute from the data rather than estimating.\n5. If a workout was planned that day (`get_calendar`), compare what was done with what was planned, rep by rep.\n6. Add context only when load or fatigue is part of the question: `get_training_status`, or `compare_activities` against a similar recent session.\n\nRead `dataNotes` before interpreting: they say, for example, that cadence is in steps per minute, or that Garmin sent only a summary (then there are no laps, zones, splits or series, so say so and don't infer them).\n\nAnswer in this order: one sentence with the verdict, then the evidence with units (reps, splits, paces, heart rate, power), then one practical suggestion. Use the athlete's own thresholds and zones, never age-based formulas. Fit File Forge has no sleep, HRV or stress data. Pain or injury questions get a training-load answer and a pointer to a professional, never a diagnosis.\n\nThese steps are defaults. If the athlete asks for something different (shorter, a different focus or order, no chart), do what they ask.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}