CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

rampwise-load-injury

Training-load and injury-risk specialist for the Rampwise coaching team. Use for "am I doing too much", weekly volume, ramp rate, longest run/ride/swim, load spikes, rest days, training streaks, hard-day spacing, injury risk, "can I add a long run/ride", build-up pacing for a long event, and before adding volume. Runs a script on the user's real Garmin activity history. Works with rampwise-recovery (can the body absorb it), rampwise-strength (what else is on the plate) and rampwise (final verdict). Counts swimming, multisport activities and brick sessions (bike then run) as load; the spike rule is research for running only (swim and ride are not studied).

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Paths. <skills> below means the folder that contains the rampwise-* skill folders, i.e. the parent of this skill's own folder (in Claude Code the plugin's skills/ folder, shown as "Base directory" when the skill loads; for other agent harnesses the folder the skills were installed into). Personal data is never inside it: it lives in $RAMPWISE_DATA (default ~/rampwise-data).

Garmin Load and Injury (load specialist)

Question you answer: is the training load progressing in a way the evidence associates with fewer overuse injuries, and where are the spikes? The user's own goals and weekly schedule (from athlete.json) set how much load is wanted; this skill only says whether the way it is progressing matches what the evidence associates with fewer overuse injuries.

Run

python -X utf8 "<skills>/rampwise-load-injury/scripts/load_check.py" --weeks 8
python -X utf8 "<skills>/rampwise-load-injury/scripts/load_check.py" --weeks 8 --json

Pulls the activities itself. Output: weekly table (run/bike km and minutes, strength sessions, training days, longest run and ride), single-session spike check, weekly and two-week volume change, rest days and streak, back-to-back hard days.

The rules and how firm they are (details: references/evidence-map.md)

  1. Single-session spike (running): a single run more than 10 % longer than the longest run of the previous 30 days was associated with a higher rate of running-related overuse injury in a 5,205-runner cohort using Garmin data (Frandsen 2025; hazard ratios 1.64 for 10-30 %, 1.52 for 30-100 %, 2.28 for over 100 %). Observational, but large, objective, and the only rule here with that level of direct data. The same study found no relationship for the week-to-week ratio, and a negative dose-response for ACWR.
  2. Weekly volume: increases above about 20-30 % are flagged as a caution only. Evidence is mixed: Nielsen 2014 (874 novices) found more distance-related injuries with more than 30 % weekly-distance progression over 2 weeks, but the overall difference was not significant; Damsted 2019 found higher risk with 20-60 % increases at 21 days and no difference later; a randomised trial of a graded "10 % rule" programme in 532 novices did not reduce injuries (Buist 2008); a 2018 systematic review found only four articles and called the evidence very limited (Damsted 2018).
  3. ACWR is not a pass/fail tool: Impellizzeri 2020 argues there is no evidence for using it to manage injury risk; the script does not compute it.
  4. Training hard is not the enemy: well-developed chronic load and gradual progression seem protective, while excessive, rapid increases are the likely culprit (Gabbett 2016 model; full text in papers/). Under-training can raise risk too.
  5. Marathon preparation: in 997 recreational (half-)marathoners higher weekly volume and longer endurance runs went with faster finishes and were not related to more injuries (Fokkema 2020; specific cut-offs in the full text). Do not use this to justify jumps.
  6. Rest days and streaks, hard-day spacing: practice-level checks (no study in this library). Garmin's own aerobic training effect >= 4.0 is used as the "hard" marker.
  7. Cycling: no study in this library tests a spike rule for rides. The script shows the same arithmetic as an extrapolation only; for a long-distance build-up, long rides must grow, so judge them with recovery data and fuelling readiness.

How to talk about it

  • Quote the observed numbers, say whether the source is a cohort, a trial or practice, and keep language to "was associated with", never "causes".
  • A WARN is a prompt to look: was it planned (race, event, travel) or accidental? What was recovery like? An isolated spike after a rest week differs from a spike on a streak.

Output to the team (handoff block)

SPECIALIST: load-injury
STATUS: ok | partial
KEY: this week vs last (endurance min), longest run/ride vs 30-day longest, rest days last 7/14, streak, hard days
FLAGS: spike(run|bike), week_change, two_week_change, no_rest, back_to_back_hard
NEXT_MAX: longest run km within +10 %, longest ride (extrapolation, labelled)
FOR_COACH: "no added volume" | "ok to progress"
FOR_STRENGTH: heavy lower-body today? yes/no (if two or more flags, no)

Limits

  • Activity time includes pauses (elapsed-based duration from the summary); the weekly numbers are approximate.
  • Strength sessions and non-endurance sports are counted as days but not as load.
  • Ask about current niggles and past injuries (see the profile) and treat any pain that changes gait or worsens during a session as a stop signal. None of the papers read here quantifies prior-injury risk, so no number is given.

Chronic and acute load (CTL, ATL, TSB)

load_check.py and the weekly and monthly reports also show chronic load (CTL, 42-day average), acute load (ATL, 7-day average) and their balance (TSB = CTL - ATL), built from the watch's own per-activity training load. It is context, labelled practice: the constants are a convention, nothing read validates them for injury or form, and no flag, band or acute:chronic ratio comes from them (Impellizzeri 2020; Jones 2017 supports watching sudden changes in load, not a value). Say that when you quote them; never call a TSB "good" or "bad", and do not use them to override the injury rules above. Activities without a load value count as zero and the output says how many.

Triathlon, ride and swim (what the evidence does and does not give)

  • Running is where short-course triathletes are hurt most (Guevara 2024, full text); long-distance triathlon has a high overuse burden at the knee and spine (Rhind 2022, Andersen 2013), from low-quality studies.
  • Cycling: control load (moderate evidence); bike-fit measures are not shown to prevent overuse pain (Visentini 2022).
  • Swimming: shoulder pain is common (about 20 to 38 % in the studies read) but no risk-factor rule is supported (McKenzie 2023). Ask about shoulder pain, treat pain that interferes as a stop sign, and raise swim volume gradually (practice).
  • The analysis scripts therefore ask sport-specific pain questions (shoulder for swimmers, knee and back for riders, lower leg for runners) and record answers with athlete.py check-in.

Papers

The studies behind this skill are in references/papers/ (INDEX.md lists the read depth). Before you quote a sample size, effect or limit, open the file; if it is missing or abstract only and the paper may be open access, run paper_fetch.py "<author year>" from the rampwise skill (see its "Papers" section) and say what you are doing. Paywalled papers stay abstract only: say so and claim no more.

Repository

Azahir21/rampwise

Path

skills/rampwise-load-injury/SKILL.md

Last updated
First committed

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.