load-anomaly-guard
Detects unsafe spikes in training load and emits SafetyFlags with conservative adjustments.
When & Why to Use This Skill
This Claude skill provides a robust safety guardrail for training load management, specifically designed to detect unsafe volume spikes and high monotony in athlete data. By analyzing historical training patterns and injury signals, it emits conservative 'SafetyFlags' and suggests actionable plan adjustments to prevent overtraining and mitigate injury risks, ensuring that AI-driven fitness recommendations remain within safe physiological limits.
Use Cases
- Automated Overtraining Prevention: Periodically audit athlete training logs to identify week-over-week volume increases exceeding 20-30%, triggering safety alerts before the next session.
- Post-Workout Risk Assessment: Immediately evaluate high-intensity or long-duration runs to flag potential overexertion and recommend necessary recovery periods or intensity swaps.
- Injury-Aware Plan Adjustments: Automatically suggest rest days or reduced-volume substitutions when injury flags are detected, prioritizing user health and long-term performance safety.
| name | load-anomaly-guard |
|---|---|
| description | Detects unsafe spikes in training load and emits SafetyFlags with conservative adjustments. |
| short-description | Background load monitor that flags spikes and proposes protective changes. |
When Codex should use it
- Nightly background check on training data.
- Immediately after a high-intensity or long run is logged.
Invocation guidance
- Provide recent
TrainingHistory, plannedPlanwindow, and any injury flags. - Compute week-over-week changes and monotony; flag spikes > deterministic caps.
- Suggest adjustments (rest/swaps) and emit
SafetyFlag[].
Input schema
See references/input-schema.json.
Output schema
See references/output-schema.json.
Integration points
- Background job: nightly cron.
- API:
v0/app/api/plan/load-guard(new) returning flags + suggested adjustments. - UI: Badge on Plan/Today screens; push/email via
v0/lib/email.ts.
Safety & guardrails
- If spike >20–30% week-over-week, emit
load_spikeand recommend rest or reduced volume. - If injury signals present, bias toward
rest-dayadjustments. - No medical diagnosis; advise professional consult on repeated spikes or pain.
Telemetry
- Emit
ai_skill_invoked,ai_safety_flag_raised, and optionallyai_adjustment_appliedwhen suggestions are auto-applied.