Skip to content
Skills Library
Personal productivity · Automation

exercise

/exercise

Use as PLSI Coach when the user wants an exercise plan - dose exercise from their state and run-time evidence, predict it against a no-action control and propose it to PLSI for nostradamus/plan - or one next workout session, built from their recent Hevy workouts and sent to Hevy on approval.

Repository
plsi ↗
Licence
MIT
Last repository change
13.11.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 13.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Use as PLSI Coach when the user wants an exercise plan - dose exercise from their state and run-time evidence, predict it against a no-action control and propose it to PLSI for nostradamus/plan - or one next workout session, built from their recent Hevy workouts and sent to Hevy on approval.

Original author description

Use as PLSI Coach when the user wants an exercise plan - dose exercise from their state and run-time evidence, predict it against a no-action control and propose it to PLSI for nostradamus/plan - or one next workout session, built from their recent Hevy workouts and sent to Hevy on approval.

How it works

  1. When to use
  2. Steps
  3. Next session
  4. Rules
Original SKILL.md headings · 123 lines, 1,126 words
SKILL.md preview
---
name: exercise
description: Use as PLSI Coach when the user wants an exercise plan - dose exercise from their state and run-time evidence, predict it against a no-action control and propose it to PLSI for nostradamus/plan - or one next workout session, built from their recent Hevy workouts and sent to Hevy on approval.
---

# PLSI exercise plan

**Status: placeholder**.

## When to use

- "Give me a workout plan", "I want to get fitter".
- "Plan my next workout", "what should I do today?": **Next session** below, not the steps.
- An activity picked in `navigator/activities`, or a goal in `personal_context` about fitness or exercise.
- Not when the request `summary` names a `scope:` line (`orchestrator/urgent`): return a `result` that declines
  and names the care to point to.
- When the request `summary` names `caution: mood-screen-positive` (`orchestrator/urgent`): do **not** hard-decline;
  NARROW to easy/restorative work only (RPE ≤ 3 or talk-test easy), no progressive overload or progressive WHO until
  clinician ack / revision_rule; keep a clinician check as a `test` when the screen is still open.

## Steps

1. **Read the state** and the coordinates that exist now (BMI, waist, blood pressure, glucose, inflammation, clocks).
   Resting heart rate, HRV, sleep duration, daily steps, weekly exercise minutes, active days per week and VO2max
   estimates are on `sleep_activity` (wearables, `wearables/import`; without PLSI Wearables on the
   team, only what was recorded in chat). Never invent a coordinate: a marker with no map coordinate goes in your `result` as a request for
   `processor/add-map` (a measured quantity) or `processor/add-score` (a formula; PLSI routes it).

   ```bash
   plsi maps list
   plsi state show --instance <instance> --map cardiometabolic
   plsi state show --instance <instance> --map sleep_activity
   plsi state show --instance <instance> --map care_context
   plsi state show --instance <instance> --map personal_context
   ```

   A resistance or recomposition plan also reads `body_composition` (`body_fat_pct`, `grip_strength`) and predicts
   on them, not on weight alone, which can stay flat while fat falls and muscle grows.

2. **Fill gaps in ONE `question` handoff** (then wait), only for what neither the state nor the request's `Known:` block holds: current exercise routine, limitations, time and budget band.
   List the answers in your `result` as `goal`, `preference` or `condition` observations for `processor/intake`.

3. **Gather evidence at run time** and verify every identifier:

   ```bash
   plsi evidence search --source pubmed --query "<exercise type> <coordinate> randomized" --limit 10
   plsi evidence search --source europepmc --query "<exercise type> <condition> safety"
   plsi evidence verify --kind pmid --id <pmid>
   ```

   Reuse the evidence library and verify only what you cite (`shared/team`, Evidence speed).

4. **Dose exercise** (`category: exercise`), one plan action per type (aerobic, resistance, balance): sessions per
   week, minutes, intensity (talk test or perceived exertion; heart-rate zones only from the user's own data), progression
   and recovery weeks as the cited guideline sets them. Start from the user's own `exercise_minutes` and `active_days` when the
   state has them; the weekly minutes target comes from the cited guideline, not from memory. Limits from
   `care_context` conditions (cardiac, joint, glucose-lowering medication): lower start, warning signs that stop a
   session, and a clinician check as a `test` action where the evidence says so. Under
   `caution: mood-screen-positive`: keep intensity easy/restorative (RPE ≤ 3), drop progressive overload, and say
   NARROW in the `result` `summary` while repeating the caution line.

5. **Predict** on predictable coordinates only (e.g. `sbp`, `waist`, `bmi`, `hba1c`, `hs_crp`,
   `phenoage_acceleration`, `exercise_minutes`, `active_days` and `vo2_max`, the last as a trend of
   device estimates only): `change_from_baseline` at 90 days with an honest interval that includes adherence and
   measurement noise, effect sizes from step 3, derived values with `plsi calc derive ... --set <input>=<value>`,
   plus one no-action control (`driven_by: []`) started from `base_rate` references (`plsi refs list`). Adherence
   targets (sessions per week) go in `method` and the `revision_rule`, not as predictions.

6. **Propose to PLSI** for `nostradamus/plan` (PLSI Nostradamus) steps 2-4: write the actions, claims and
   predictions to `work/<thread>/proposal-coach.json` (`shared/team` rule 3) and return a `result` with its path; Nostradamus merges them into the one plan, screens against `care_context`, runs `plan check`,
   has PLSI hand it to `challenger/challenge` and records and adopts only after PLSI's adoption card. Never check,
   record or adopt a plan yourself.

## Next session

One workout, not a plan: no predictions and no Nostradamus. A request for a program goes to the steps above.
Only for the Hevy account's owner, the user's own instance (relation `self` in `plsi instances list`): one key is one person's log, so a session for anyone else
(family, a patient) is a plan in chat, never a Hevy routine. Cues name the exercise and its form only (tempo,
rest, range), a ladder written with commas ("50, 60, 70 kg"): never a reason drawn from the record (a
condition, an injury, a medicine, a value).

1. **Read** the ask (focus, minutes, what to leave out), an adopted exercise plan (`plsi status --instance
   <instance>`, so the session fits it), the latest sleep, resting heart rate and HRV on `sleep_activity`,
   limits in `care_context`, and the last two weeks of training:

   ```bash
   plsi hevy check
   plsi hevy workouts --since <14 days ago> > <PLSI_HOME>/work/<thread>/hevy-workouts.json
   ```

   Hevy not connected: ask in ONE `question` what was trained in the last few days, and offer "Connect Hevy?"
   (PLSI Wearables, `wearables/hevy`) when Wearables is on the team (`plsi team show`), else "Add PLSI Wearables to
   connect Hevy?"; only Wearables connects it.

2. **Compose** within the minutes, warm-up included: the muscle groups asked for, a muscle group worked hard in
   the last 48 hours only lighter, and what the user excluded never. Exercises the user has done before come
   first; their load starts from the user's own last sets of that exercise and moves up only after the last
   session's sets were all done. A new exercise gets no weight: its note says to pick one that leaves two reps.
   Sleep or recovery well below the user's own usual: a lighter session, and say why. Pick ids with:

   ```bash
   plsi hevy templates --muscle <muscle group>
   plsi hevy templates --search <exercise name>
   ```

3. **Write** `<PLSI_HOME>/work/<thread>/session.json` (`title`; `notes`; `exercises` with
   `exercise_template_id`, `rest_seconds`, short `notes` with cues and `sets` with `type`, `reps`, `weight_kg`,
   `duration_seconds`) and check it; its notes are about the exercises only, never health details:

   ```bash
   plsi hevy routine --file <PLSI_HOME>/work/<thread>/session.json
   ```

4. **Return one `result`**: the session as the user reads it (exercise, sets × reps, weight, rest, about how many
   minutes, and why it looks like this), `session.json` and its `session_hash` in `files`, and the card "Put it in
   Hevy?" (Yes / Change something / No). Without Hevy: the session only.

## Rules

- Crisis signs (self-harm or suicide thoughts, chest pain on exertion, fainting) in any input: stop planning and
  return a `result` with a `red_flag:` line (`orchestrator/urgent`) at once. Eating-disorder signs: stop and return a
  `result` with a `scope:` line (`orchestrator/urgent`) instead. Soft `caution: mood-screen-positive` is neither:
  NARROW, do not hard-decline.
- Start low for anyone inactive, older or with conditions; progress only when the previous step is tolerated.
- Sample sessions go in the `result` summary for PLSI to show; only plan actions and predictions go into `plan.json`.
- No product, brand or drug names; placeholders such as `<device>`.

Versions

RepositoryScoreLicence
This page · Insilico-org/plsi100MIT
brolag/neural-claude-code100MIT

Database snapshot: 13.11.2026 · package version ca22691f1d57 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100hevy
    Use as PLSI Wearables when PLSI asks to connect Hevy (the workout log) or check, repair or remove that connection, or to read what the user trained - the Hevy Pro API key, a check, and recent workouts for PLSI Coach.
  • 100hevy-workouts
    Use when the user asks to inspect, summarize, plan, log, or update Hevy workouts, routines, exercises, or body measurements.
  • 100iam360-workouts
    Review IAM360 exercise history, log completed training and save an approved workout routine. Use for the user's IAM360 workouts, sets, feedback or calendar plans, while keeping planned and completed sessions distinct.
  • 100setup
    Choose how CoAIch runs, your language and units, and where your training data comes from (Strong, Hevy, openGym, Apple Health or by hand), then check it works. Use when the user runs /setup, wants to add or change an integration or data source, or when onboard starts.
  • 95coach-plan
    This skill should be used when the user asks "what am I doing today", "write my workout", "plan the session", "что сегодня", "напиши тренировку", or runs /coach:plan. It writes the next workout from the athlete's program and recent history.
  • 100import
    Bring training and health data into the athlete folder from a Strong CSV export, Hevy (MCP or CSV export), an openGym backup or Apple Health (Health Auto Export JSON). Use when the user shares an export, says "import my Strong export", "sync Hevy", "pull my workouts", "sync…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.