Onyx Coach

View saved version →

---
name: onyx-build-client-program
description: Create a new workout template or multi-week workout-plan template for an existing Onyx Coach client. Use when a trainer asks to design, build, save, or assign a client workout or training program; do not use for general fitness questions or editing an existing program.
---

# Build an Onyx Coach Client Program

Create a structured program with verified client and exercise identifiers, then save or assign it only as requested.

## Workflow

1. Resolve the client with `list_clients`.
    - Never guess a client id.
    - If more than one client matches, ask the trainer to choose.
2. Collect only missing requirements:
    - goal;
    - experience level;
    - sessions per week;
    - session duration;
    - available equipment;
    - movement constraints or exercises to avoid;
    - single workout versus multi-week plan.
3. Read only context relevant to the request:
    - `get_client_workout_history` for recent training;
    - `list_workout_templates` for existing reusable workouts;
    - `list_workout_plan_templates` and `list_client_workout_plans` for current programming;
    - `list_client_notes` only when the trainer asks to use their private notes.
4. Read [references/program-design.md](references/program-design.md) and draft the proposed structure.
5. Resolve every exercise through `list_exercises` or `list_official_exercises`.
    - Never invent an exercise id.
    - Prefer exact matches; ask when multiple exercises could satisfy the request.
6. Present a concise draft containing session names, exercise order, sets, targets, rest, and progression assumptions.
7. Before the first write, obtain confirmation unless the trainer already approved an equally specific draft in this conversation.
8. Save the program:
    - Use `create_workout_template` for one reusable client workout.
    - Use `create_workout_plan_template` for a scheduled multi-week client program.
9. Use `assign_workout_plan` only when the trainer explicitly asks to activate the plan for the client.
10. Report what was created, identify any assumptions, and distinguish a saved template from an assigned active plan.

## Boundaries

- Do not diagnose injuries or medical conditions.
- Ask for operational movement constraints rather than medical history.
- Do not create content for an unresolved client or with guessed exercise ids.
- Do not claim a plan was assigned when only a template was created.
- Do not silently create, assign, update, or delete additional records.

## Output

Return:

1. Client
2. Program summary
3. Sessions and prescriptions
4. Saved template or plan identifier
5. Assignment status
6. Assumptions or unresolved constraints

Referenced files: 1

View saved version →

---
name: onyx-manage-client-notes
description: List, create, pin, edit, or delete the signed-in trainer's private notes for an existing Onyx Coach client. Use when a trainer explicitly asks to record or manage coaching notes; do not use for messages the client should receive or for general client-profile changes.
---

# Manage Onyx Coach Client Notes

Manage only the signed-in trainer's private notes for a clearly identified coached client.

## Workflow

1. Resolve the client with `list_clients`; never guess a client id.
2. Choose the smallest matching action:
    - `list_client_notes` to review existing notes;
    - `create_client_note` to add trainer-provided text and optional pinned status;
    - `update_client_note` to change text or pinned status on a resolved note;
    - `delete_client_note` to remove a resolved note.
3. List notes before update or deletion unless the trainer supplied an exact note id from the current conversation.
4. Ask the trainer to choose when more than one note matches.
5. Require confirmation immediately before deletion.
6. Return a minimal confirmation without unnecessarily repeating sensitive note text.

## Privacy and Safety

- Notes are private to the trainer and are not client messages.
- Do not use this skill to email, notify, or otherwise contact the client.
- Record only text the trainer supplied or explicitly approved.
- Do not solicit or store passwords, authentication codes, payment data, government identifiers, diagnoses, test results, insurance information, or unnecessary medical details.
- When medical detail is unnecessary, suggest recording only an operational constraint such as an exercise to avoid.
- Never reveal one trainer's notes to another user.

## Output

State:

1. Client
2. Note action
3. Pinned status when relevant
4. Completion or reason the action could not be completed

View saved version →

---
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

Referenced files: 1