Detects Follow-Through Day (FTD) signals for market bottom confirmation using William O'Neil's methodology. Dual-index tracking (S&P 500 + NASDAQ) with state machine for rally attempt, FTD qualification, and post-FTD health monitoring. Use when user asks about market bottom signals, follow-through days, rally attempts, re-entry timing after corrections, or whether it's safe to increase equity exposure. Complementary to market-top-detector (defensive) - this skill is offensive (bottom confirmation).
84%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
^IXIC (Composite). Use --nasdaq-symbol QQQ only for a labeled Nasdaq-100 ETF proxy. Never substitute its volume or price into an index series or claim its DD count is the Composite count. No automatic fallback.quality_score is an uncalibrated technical heuristic, not success probability. exposure_range is Not assessed in every state. Do not derive portfolio percentages from the score; assess breadth, leadership, portfolio limits and operator decisions separately.Detect Follow-Through Day (FTD) signals that confirm a market bottom, using an explicit O'Neil-style technical model. Generates a quality score (0-100) with technical health warnings; portfolio exposure is not assessed.
Complementary to Market Top Detector:
English:
Japanese:
| Aspect | FTD Detector | Market Top Detector |
|---|---|---|
| Focus | Rally-event confirmation | Market deterioration assessment |
| Trigger | Market correction (3%+ decline) | Market at/near highs |
| Signal | Rally attempt → FTD → health assessment | Distribution → deterioration evidence |
| Score | 0-100 heuristic FTD quality | Separate heuristic market-risk score |
| Action | When technical confirmation appears | When deterioration appears |
Run the FTD detector script:
python3 skills/ftd-detector/scripts/ftd_detector.py --api-key $FMP_API_KEYThe script will:
API Budget: 4 calls (well within free tier of 250/day)
Present the generated Markdown report to the user, highlighting:
Based on the market state, provide additional guidance:
If FTD Confirmed (score 60+):
If Rally Attempt (Day 1-3):
If No Correction:
NO_SIGNAL → CORRECTION → RALLY_ATTEMPT → FTD_WINDOW → FTD_CONFIRMED
↑ ↓ ↓ ↓
└── RALLY_FAILED ←─────────────┘ FTD_INVALIDATED| State | Definition |
|---|---|
| NO_SIGNAL | Uptrend, no qualifying correction |
| CORRECTION | 3%+ decline with 3+ down days |
| RALLY_ATTEMPT | Day 1-3 of rally from swing low |
| FTD_WINDOW | Day 4-10, waiting for qualifying FTD |
| FTD_CONFIRMED | Valid FTD signal detected |
| RALLY_FAILED | Rally breached the Day 1 low (or exhausted this model's FTD window) |
| FTD_INVALIDATED | Intraday low below the recorded rally Day 1 low |
| Score | Signal | Exposure |
|---|---|---|
| 80-100 | Strong FTD | Not assessed |
| 60-79 | Moderate FTD | Not assessed |
| 40-59 | Weak FTD | Not assessed |
| <40 | Very weak FTD (unless explicitly invalidated) | Not assessed |
| 0 | Unavailable: data gap | Not assessed |
FMP_API_KEY environment variable or pass via --api-key flag.requests library installed.ftd_detector_YYYY-MM-DD_HHMMSS.jsonftd_detector_YYYY-MM-DD_HHMMSS.mdA missing or non-finite close/volume (or a non-positive close) is never read as 0, and bars are never dropped. Bar fields are read through the vendored scripts/_price_bars.py helper.
data_gap (bool, every run, at the top level and in market_state): true when an index's 60-session window or a post-FTD check hit a bad bar.data_quality (every run): per index, the window check (window_sessions, bad_bars, bad_dates, latest_bad) plus sp500.power_trend_bad_bars for the power-trend input (counted only when the power trend runs, 50+ bars). Each index block also carries its own data_quality, and error when the analysis failed ("Insufficient data" or "Data gap: ...").NO_SIGNAL with current_price / lookback_high / correction_depth_pct set to null; no rally or FTD logic runs for it. With any gapped index the run's combined_state is reported as NO_SIGNAL with data_gap: true, meaning state unavailable (not an uptrend), with ftd_index: null and no post-FTD checks. The other index is never promoted, because the gap could be hiding the gapped index's own (possibly invalidated) FTD. Each index's own analysis stays in the JSON. The Markdown headline reads "State unavailable (data gap)".quality_score is total_score: 0 (always an int, never null), signal: "Unavailable: data gap", exposure_range: "Not assessed", data_gap: true. Treat this as "no usable confirmation": do not increase exposure on it. A gapped distribution check keeps distribution_count: 0 (int) with data_gap: true; a gapped invalidation check reports invalidated: null. A post-FTD gap also reports the combined state as NO_SIGNAL with data_gap: true (state unavailable), since the FTD can be neither confirmed nor invalidated.power_trend: null with a reason; this alone does not set data_gap or change the score.skills/ftd-detector/references/ftd_methodology.mdskills/ftd-detector/references/post_ftd_guide.mdskills/ftd-detector/references/ftd_methodology.md for full understandingskills/ftd-detector/references/post_ftd_guide.mdFTD-day-low pressure caps published quality at 59 (uncalibrated conservative heuristic); it does not erase the event or imply rally failure.
NO_SIGNAL with data_gap: true. Known prices and any already-established historical event evidence may remain visible; this does not mean the lifecycle is assessable.tradermonty/claude-trading-skills
a627d17
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.