Opus finding
Sharp-move dedup combined with H1 percentage can suppress a second leg of a real move
lowmaintainabilitymedium
- skills/price-threshold-alert/SKILL.md:137-143
The H1 rolling window is 1 hour; the dedup window is 4 hours. A token that pumps +25% in hour 1 (alert fires), then dumps -25% in hour 3 (also a 'sharp move' per spec) would be silenced because the dedup clock is wider than the measurement window. This is a deliberate design choice but is not called out, and operators may miss exactly the reversal events the skill markets itself as catching ('liquidation cascade').
Recommendation
Either (a) separate dedup clocks per direction (`sharp_move_up`, `sharp_move_down`) or (b) document the 4h-vs-1h trade-off explicitly so operators understand reversals can be silenced.