/workout-profile — Build the user's fitness profile
This skill interviews the user and writes a profile to
~/workout-coach/profile.md. The other workout skills (workout,
workout-log) read this file, so keep it accurate and well-structured.
Context
The user works remotely and wants short workouts that fit inside a working
day — typically 5–15 minute sets done between meetings, with limited space
and equipment. Frame every question with that in mind.
Steps
Check for an existing profile. Run cat ~/workout-coach/profile.md
(it may not exist). If it exists, this is an update — show the current
values and ask what they want to change rather than starting from scratch.
Interview the user. Ask conversationally, a few related questions at a
time — don't dump all of these at once. Cover:
- Exercise types they enjoy / want — e.g. bodyweight strength,
resistance bands, dumbbells/kettlebell, mobility & stretching, desk-based
movement, light cardio. Multiple is fine.
- Frequency — how many short sessions per day and/or days per week.
- Current fitness level — beginner / intermediate / advanced, plus a
sentence on what they can currently do (e.g. "can do 10 push-ups").
- Equipment & space — what they have at their desk/home and how much
room (e.g. "just a chair and a yoga mat", "adjustable dumbbells").
- Time per session — minutes they realistically have per break.
- Goals — e.g. counter sitting, build strength, mobility, energy.
Also ask explicitly whether they have any specific PB / measurable
targets they're chasing (e.g. "10 pull-ups in a row", "sub-6:00 mile",
"half marathon in 2:10", "100 push-ups"). Capture each with a current
best where known, so
/workout can program toward them and progress is
trackable. "None yet" is a fine answer.
- Injuries / limitations — distinguish permanent things to avoid
(e.g. a chronic bad back) from temporary niggles that should clear up
(e.g. "neck stiff this week"). The temporary ones shouldn't suppress
exercises forever.
Use sensible defaults if the user is vague, and confirm them. Don't
interrogate — 2–4 short exchanges is plenty.
Write the profile to ~/workout-coach/profile.md using the template
below. Run mkdir -p ~/workout-coach first if needed. Fill in only what
you learned; leave honest "not specified" for anything skipped.
Confirm what you saved and point to the next steps: they can pick a
coaching persona with /workout-trainer (optional), then run /workout to
get a session.
Profile template
# Workout Profile
_Last updated: <YYYY-MM-DD>_
## Fitness level
<beginner | intermediate | advanced> — <one line on current baseline>
## Preferred exercise types
- <type 1>
- <type 2>
## Frequency
<e.g. 2 short sessions per workday, ~4 days/week>
## Time per session
<e.g. 10 minutes>
## Equipment & space
<e.g. yoga mat, resistance band, ~2m of floor space, a sturdy chair>
## Goals
<e.g. break up sitting, build upper-body strength>
### PB targets
<specific measurable goals with current best where known, e.g.
"Pull-ups: 10 in a row (current best: 8)", "1 mile run: sub-6:00". "none yet" if so>
## Permanent limitations
<lasting things to always avoid, e.g. sensitive lower back — avoid heavy spinal loading. "none" if so>
## Current / temporary niggles
<short-term issues to work around for now, e.g. stiff neck this week. Clear these once resolved. "none" if so>
## Notes
<anything else worth remembering>
Get the current date from the shell with date +%F for the _Last updated_
field (don't trust a remembered date). Keep the file tidy — it's the single
source of truth.
1---2name: workout-profile3description: Gather and save a remote-worker's fitness profile — preferred exercise types, how often they want to train, current fitness level, available equipment/space, time per session, goals, and any injuries. Use when the user wants to set up, create, or update their workout profile, or says things like "set up my workout plan", "I want to start exercising at my desk", or before proposing/logging workouts if no profile exists yet.4---56# /workout-profile — Build the user's fitness profile78This skill interviews the user and writes a profile to9`~/workout-coach/profile.md`. The other workout skills (`workout`,10`workout-log`) read this file, so keep it accurate and well-structured.1112## Context1314The user works remotely and wants **short workouts that fit inside a working15day** — typically 5–15 minute sets done between meetings, with limited space16and equipment. Frame every question with that in mind.1718## Steps19201. **Check for an existing profile.** Run `cat ~/workout-coach/profile.md`21 (it may not exist). If it exists, this is an *update* — show the current22 values and ask what they want to change rather than starting from scratch.23242. **Interview the user.** Ask conversationally, a few related questions at a25 time — don't dump all of these at once. Cover:26 - **Exercise types they enjoy / want** — e.g. bodyweight strength,27 resistance bands, dumbbells/kettlebell, mobility & stretching, desk-based28 movement, light cardio. Multiple is fine.29 - **Frequency** — how many short sessions per day and/or days per week.30 - **Current fitness level** — beginner / intermediate / advanced, plus a31 sentence on what they can currently do (e.g. "can do 10 push-ups").32 - **Equipment & space** — what they have at their desk/home and how much33 room (e.g. "just a chair and a yoga mat", "adjustable dumbbells").34 - **Time per session** — minutes they realistically have per break.35 - **Goals** — e.g. counter sitting, build strength, mobility, energy.36 Also ask explicitly whether they have any **specific PB / measurable37 targets** they're chasing (e.g. "10 pull-ups in a row", "sub-6:00 mile",38 "half marathon in 2:10", "100 push-ups"). Capture each with a current39 best where known, so `/workout` can program toward them and progress is40 trackable. "None yet" is a fine answer.41 - **Injuries / limitations** — distinguish **permanent** things to avoid42 (e.g. a chronic bad back) from **temporary** niggles that should clear up43 (e.g. "neck stiff this week"). The temporary ones shouldn't suppress44 exercises forever.4546 Use sensible defaults if the user is vague, and confirm them. Don't47 interrogate — 2–4 short exchanges is plenty.48493. **Write the profile** to `~/workout-coach/profile.md` using the template50 below. Run `mkdir -p ~/workout-coach` first if needed. Fill in only what51 you learned; leave honest "not specified" for anything skipped.52534. **Confirm** what you saved and point to the next steps: they can pick a54 coaching persona with `/workout-trainer` (optional), then run `/workout` to55 get a session.5657## Profile template5859```markdown60# Workout Profile6162_Last updated: <YYYY-MM-DD>_6364## Fitness level65<beginner | intermediate | advanced> — <one line on current baseline>6667## Preferred exercise types68- <type 1>69- <type 2>7071## Frequency72<e.g. 2 short sessions per workday, ~4 days/week>7374## Time per session75<e.g. 10 minutes>7677## Equipment & space78<e.g. yoga mat, resistance band, ~2m of floor space, a sturdy chair>7980## Goals81<e.g. break up sitting, build upper-body strength>8283### PB targets84<specific measurable goals with current best where known, e.g.85"Pull-ups: 10 in a row (current best: 8)", "1 mile run: sub-6:00". "none yet" if so>8687## Permanent limitations88<lasting things to always avoid, e.g. sensitive lower back — avoid heavy spinal loading. "none" if so>8990## Current / temporary niggles91<short-term issues to work around for now, e.g. stiff neck this week. Clear these once resolved. "none" if so>9293## Notes94<anything else worth remembering>95```9697Get the current date from the shell with `date +%F` for the `_Last updated_`98field (don't trust a remembered date). Keep the file tidy — it's the single99source of truth.