Use when the user describes or shows a CrossFit movement being performed and asks what is wrong or how to fix it – phrasings like "my squat caves at the bottom", "here's my snatch, what's the fault".
Use when the user describes or shows a CrossFit movement being performed and asks what is wrong or how to fix it - phrasings like "my squat caves at the bottom", "here's my snatch, what's the fault". Works from observation only (described video, an image where supported, or coach observation), separates observation from inference, ranks visible faults, gives cues and drills, and recommends a retest. Excludes building a skill the athlete cannot yet do (crossfit-movement-progression-builder owns that) and pure cue lists (crossfit-coaching-cue-generator).This is the skill's description: the text your AI reads to decide when the skill applies.
crossfit-movement-fault-analyzer/SKILL.md
# CrossFit Movement Fault Analyzer
Analyze a movement **from observation only** - a described video, an image where
supported, or a coach's account - and identify the **visible** faults, ranked.
This skill owns "what's wrong with this rep / how do I fix it" requests. The
discipline is honesty about evidence: separate what is **observed** from what is
**inferred**, never claim an unseen cause, and never diagnose anatomy or pathology
from a movement. Use
[../../references/movement-pattern-taxonomy.md](../../references/movement-pattern-taxonomy.md),
[../../references/gymnastics-progressions.md](../../references/gymnastics-progressions.md),
and
[../../references/weightlifting-progressions.md](../../references/weightlifting-progressions.md).
## Workflow
1. **Restate what was observed** in neutral, concrete terms (positions, bar path,
timing) - the evidence base.
2. **State what cannot be determined** from this observation (camera angle, single
rep, no load info, no internal/anatomical view).
3. **List visible faults**, separating **observation** ("knees track inward at the
bottom") from **inference** ("likely a position/control issue, not necessarily
weakness").
4. **Rank the faults** by safety first, then performance impact, then ease of
correction - in a table.
5. **Give 1-2 concise cues per priority fault** (defer long cue libraries to… load the full skill through Skill Me