← MoveMate: Gym Workout TrackerCONTENT HISTORY
WHAT CHANGED
Update to MoveMate: Gym Workout Tracker
Snapshot Oct 24, 2026 · 12:53 UTC · version 1.2.0
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save MoveMate: Gym Workout Tracker and check future changes in Following.
Up to 3 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Report how the user's MoveMate training is going — weekly or monthly summaries, whether a lift is progressing or stalled, plateau diagnosis, and personal records. Read-only: it never schedules or changes anything. Not for planning or editing a session — use plan-workout for that.",
"included_files": [],
"name": "review-training",
"skill_md_contents": "---\nname: review-training\ndescription: Report how the user's MoveMate training is going — weekly or monthly summaries, whether a lift is progressing or stalled, plateau diagnosis, and personal records. Read-only: it never schedules or changes anything. Not for planning or editing a session — use plan-workout for that.\n---\n\n# Review training in MoveMate\n\nEvery number in the answer must come from a tool result. This skill only reads.\n\n## Pick the right tool\n\n- **\"How did I do?\" / \"How was that workout?\"** → `get_recent_workouts` with `limit: 1`. This is the only tool that returns individual sets — reps and weight of every completed set, `reps_per_set`, `total_reps`, and the planned targets the user was working against. Use it whenever the question is about a specific session rather than a period.\n- **\"How was my week/month?\"** → `get_training_stats` with `period` (`last_7d`, `last_30d`, `last_90d`, `last_year`, `all_time`) and optional `muscle_group`. Returns volume, frequency, streak and weekday distribution.\n- **\"Why has my bench stalled?\" / \"Am I getting stronger on X?\"** → `get_exercise_progression` with `exercise_name` (or `exercise_id` if you have a real one from `search_exercises`) and optional `period`. It returns the per-session trend plus `trend` and `plateau_weeks` — use those fields rather than eyeballing the series yourself. `progression_metric` tells you which series they were computed from: `estimated_1rm` for a loaded lift, `total_reps` for a bodyweight one. Report progress in those same terms.\n- **\"How does that compare to last time?\"** → `get_recent_workouts` with `exercise_name` and `limit` up to 10, which returns that movement's sets across its last few sessions. Prefer this over `get_exercise_progression` when the comparison is about reps or sets rather than load.\n- **\"What are my PRs?\"** → `get_personal_records`, optionally narrowed by `exercise_id`, with `limit` up to 100.\n- **\"Did I finish what was planned?\"** → `get_recent_workouts`. Compare `completed_sets` against `planned_sets` and `total_reps` against `planned_total_reps`. Sessions logged ad-hoc have `from_plan: false` and no targets — say there was no plan to compare against rather than treating what they did as the plan.\n- Anything about the person rather than the training (timezone, how long they have been a member, average sessions per week) → `get_profile`. Body stats and goals → `get_body_profile`.\n\nFor a plateau question, read the progression **before** offering an explanation. A stall of two weeks and a stall of three months call for different answers.\n\n## Bodyweight movements\nFor pull-ups, push-ups, dips, bodyweight squats and anything else done unloaded, **total reps and reps per set are the result** — `total_volume_kg` and `estimated_1rm` are 0 and mean nothing there. Use `get_recent_workouts` and talk in sets and reps: \"24 total pull-ups across 5 sets (4, 5, 6, 5, 4)\". Progress is more reps at the same set count, more sets at the same reps, or the same total with fewer sets — say which one you are looking at.\n\n## How to report\n\nLead with the answer in one or two sentences, then the few numbers that support it. A wall of every returned field is not a review.\n\nGive at most one concrete adjustment, tied to what the data shows — a load change, a frequency change, a rep-range change. Say what you would expect to see if it worked.\n\nState the period you are describing. \"Your volume is up\" is meaningless without \"over the last 30 days\".\n\n## Honesty rules\n\n- If a tool returns nothing — no sessions in the period, no history for that exercise — say so directly. Never fill a gap with a plausible number, an estimate, or an example.\n- Do not claim a trend the data does not support. Two sessions is not a trend.\n- Distinguish what was **planned** from what was **completed**. Stats and records come from completed workouts; a scheduled session the user skipped is not training that happened.\n- The user's own numbers are the reference point. Do not compare them to population averages or \"what most lifters do\" unless they ask.\n\n## Never\n\n- Diagnose pain, injury or illness, or suggest rehabilitation protocols. If the user describes pain, say that it needs a professional, and keep the training discussion separate.\n- Give nutrition, supplement or medication advice as part of a training review.\n- Schedule, change or cancel a workout from this skill. If the review leads somewhere — \"so should I deload next week?\" — that is a planning task: propose it and ask first.\n"
}SHA-256 of public snapshot: 689f9ae036b45c88211a5baafed7fa2e07ca201fbf163539bc05f2606220fba6