← Files Onyx CoachARCHIVED FILE

SKILL.md

1.98 KB · Oct 2, 2026 · 00:14 UTC

↓ Download file

---
name: onyx-review-client-progress
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.
---

# Review Onyx Coach Client Progress

Produce a read-only coaching review grounded in the client's stored training data.

## Workflow

1. Resolve the client with `list_clients`.
    - Never guess a client id.
    - Ask the trainer to choose when a name is ambiguous.
2. Confirm the review period when it is not clear from the request.
3. Retrieve the minimum useful data:
    - `get_client_workout_history` for completed workouts;
    - `list_client_workout_plans` for active plan instances and progress;
    - `list_workout_plan_templates` only when template context is needed;
    - `list_client_notes` only when the trainer explicitly asks to include private notes.
4. Page workout history only as far back as the requested review period requires.
5. Read [references/progress-analysis.md](references/progress-analysis.md).
6. Separate:
    - observed facts;
    - calculated trends;
    - coaching interpretations;
    - missing or incomparable data.
7. Make recommendations as proposals only. Do not call write tools.

## Boundaries

- Never invent missing workouts, plan schedules, loads, or completion status.
- Compare loads only when exercise identity and units are compatible.
- Do not infer injury, diagnosis, motivation, or noncompliance from missing data.
- Do not expose private notes unless the trainer requested them for this review.
- If the trainer asks to implement a recommendation, hand off to `onyx-adjust-client-program` or `onyx-build-client-program`.

## Output

Return:

1. Review period and data coverage
2. Activity summary
3. Supported trends
4. Plan progress
5. Coaching observations
6. Suggested next actions
7. Data limitations

SHA-256: f18b97ae73e4d746bc40d92ac59240701d88163ed716e9b26b3bd911aa064dbf