runner

The problem

Running data from Garmin or Strava often remains a pile of unused metrics. Runners struggle to connect high ground contact time or low cadence to the actual pain in their shins or fatigue in their calves.

What it does

• Decodes core metrics including cadence, ground contact time, flight time, and vertical oscillation.
• Maps subjective sensations like shin soreness or hip fatigue to specific biomechanical deviations.
• Explains the physics-based root causes of efficiency loss using POSE Method principles.
• Prescribes exactly 1-2 minimal intervention cues to implement in the next training session.
• Tracks evolution signals like increasing elasticity or decreasing braking forces over time.

Why this beats prompting it yourself

General LLMs often give generic advice like "stretch more" or "run faster." This skill enforces a strict biomechanical priority logic, ensuring you don't chase speed at the expense of form, and prevents information overload by limiting feedback to two actionable cues.

Use cases

• Analyze a recent Garmin activity to explain why your calves feel unusually tight.
• Diagnose why heart rate spikes despite a perceived easy pace by checking vertical oscillation.
• Optimize running economy for a marathon build by increasing flight time and reducing ground contact.
• Troubleshoot recurring shin splints by identifying over-striding patterns in cadence data.

Known limitations

Requires specific metrics like ground contact time and vertical oscillation for full analysis. Not a medical diagnostic tool for acute injuries.