Flag Training Adjustment

VerifiedSafe

Flags adjustments or life factors affecting training, such as fatigue, injury, or schedule changes. Updates an adjustments file that other skills read to modify workouts accordingly.

Sby Skills Guide Bot
ProductivityIntermediate
606/2/2026
Claude Code
#training-adjustments#fatigue-recovery#injury#schedule#fitness

Recommended for

Our review

This skill allows users to flag training adjustments (fatigue, injury, schedule changes) that modify workout plans.

Strengths

  • Easily logs adjustments in a dedicated file.
  • Provides a clear format for tracking issues.
  • Integrates with the workout generation skill.
  • Explains the impact on upcoming workouts.

Limitations

  • Relies on manual user input.
  • Updates a single file with no versioning.
  • Does not handle complex multi-factor adjustments.
When to use it

Use this skill when you need to record a temporary training change that should affect your workouts.

When not to use it

Do not use it for permanent training plan modifications or when detailed medical advice is needed.

Security analysis

Safe
Quality score90/100

The skill only reads and writes local markdown files for workout adjustments using safe shell commands (cat, grep). No network calls, destructive actions, or data exfiltration.

No concerns found

Examples

Flag fatigue after a stressful week
I had a stressful week and feel run down. Adjust my workouts to lower intensity.
Report a minor shoulder injury
My shoulder is tweaky. I want to reduce overhead pressing and avoid movements that aggravate it.
Schedule change for next week
I can only train twice next week. Update my plan accordingly.

name: adjust description: Flag an adjustment or life factor affecting training. Use when user reports fatigue, injury, schedule changes, or anything that should modify workouts. allowed-tools:

  • Read
  • Write
  • Edit

Flag Training Adjustment

Current Context

  • Current adjustments: !cat adjustments.md 2>/dev/null || echo "No adjustments file"
  • Recent flags from workouts: !grep -h "## Flags" workouts/*.md 2>/dev/null | head -10 || echo "No recent flags"

Instructions

The user wants to note something that should affect upcoming workouts:

  • Fatigue/Recovery: "bad sleep", "stressful week", "feeling run down"
  • Minor injury/pain: "shoulder is tweaky", "lower back tight"
  • Life factors: "traveling next week", "only have dumbbells this week"
  • Training feel: "feeling strong", "ready to push", "need a deload"
  • Schedule change: "can only train 2x this week"
  • Resolved issue: "shoulder feeling better now"

Actions

  1. Acknowledge the adjustment
  2. Update adjustments.md:
    • Add new flag with date, description, impact, and expiry
    • If resolving an existing flag, remove that row
  3. Explain how this will affect upcoming workouts:
    • What modifications will be made
    • How long the adjustment applies (ask if not clear)
    • When to revisit/clear the flag

Format for adjustments.md

Add a new row to the table:

| YYYY-MM-DD | [issue] | [modification] | [when to revisit] |

Example:

| 2026-01-27 | Left shoulder tight | Reduce overhead volume, no HSPU negatives | Re-evaluate Friday |
| 2026-01-25 | Low sleep this week | Keep RPE under 7, reduce volume 20% | End of week |

The /workout skill reads this file and adapts accordingly.

Related skills