Update to Onyx Coach

{
  "description": "Analyze an existing Onyx Coach client's workout history, active plans, and training trends without changing data. Use when a trainer asks for a progress review, adherence summary, recent-workout analysis, trend report, or evidence-based recommendations; do not use when the request is to create or modify a program.",
  "included_files": [
    {
      "relative_path": "references/progress-analysis.md",
      "size_in_bytes": 1433
    }
  ],
  "name": "onyx-review-client-progress",
  "skill_md_contents": "---\nname: onyx-review-client-progress\ndescription: Analyze an existing Onyx Coach client's workout history, active plans, and training trends without changing data. Use when a trainer asks for a progress review, adherence summary, recent-workout analysis, trend report, or evidence-based recommendations; do not use when the request is to create or modify a program.\n---\n\n# Review Onyx Coach Client Progress\n\nProduce a read-only coaching review grounded in the client's stored training data.\n\n## Workflow\n\n1. Resolve the client with `list_clients`.\n    - Never guess a client id.\n    - Ask the trainer to choose when a name is ambiguous.\n2. Confirm the review period when it is not clear from the request.\n3. Retrieve the minimum useful data:\n    - `get_client_workout_history` for completed workouts;\n    - `list_client_workout_plans` for active plan instances and progress;\n    - `list_workout_plan_templates` only when template context is needed;\n    - `list_client_notes` only when the trainer explicitly asks to include private notes.\n4. Page workout history only as far back as the requested review period requires.\n5. Read [references/progress-analysis.md](references/progress-analysis.md).\n6. Separate:\n    - observed facts;\n    - calculated trends;\n    - coaching interpretations;\n    - missing or incomparable data.\n7. Make recommendations as proposals only. Do not call write tools.\n\n## Boundaries\n\n- Never invent missing workouts, plan schedules, loads, or completion status.\n- Compare loads only when exercise identity and units are compatible.\n- Do not infer injury, diagnosis, motivation, or noncompliance from missing data.\n- Do not expose private notes unless the trainer requested them for this review.\n- If the trainer asks to implement a recommendation, hand off to `onyx-adjust-client-program` or `onyx-build-client-program`.\n\n## Output\n\nReturn:\n\n1. Review period and data coverage\n2. Activity summary\n3. Supported trends\n4. Plan progress\n5. Coaching observations\n6. Suggested next actions\n7. Data limitations\n"
}