agentleFS
krzysukrzysu/market-skills/skills/strategy-exhaustion-fade/SKILL.md

strategy-exhaustion-fade

Skill3 starsChanged 4 months agoMITView on GitHub

L3 contrarian strategy. Fades exhaustion patterns (blowoff, capitulation) at extreme levels. Composes exhaustion, trend, and S/R.

The file

Files
SKILL.md

strategy-exhaustion-fade

L3 contrarian strategy that fades exhaustion patterns when the trend is extended and price is at a key S/R level.

When NOT to use

  • Without a mandatory risk-engine vet before execution — this skill emits ideas, not orders. Always vet the Intent and get explicit user approval.
  • In a still-strong trend — fading exhaustion in an extended-but-intact uptrend/market-trend is a classic loss; wait for a clear S/R level and reversal structure.
  • For a single-indicator read — it composes market-exhaustion + market-s-r + market-trend; call those directly if you only want the pattern.

Quick Start

uv run skills/strategy-exhaustion-fade/scripts/run.py SPY
uv run skills/strategy-exhaustion-fade/scripts/run.py SPY --json

Flags

FlagDefaultNotes
TICKER (positional)—Required. Supports provider:ticker (e.g. hl:LIT, yf:AAPL).
--jsonhumanEmit JSON to stdout.
--source=PROVIDERauto-detectForce a data provider (see README).
--interval=INTERVAL1d1m/2m/5m/15m/30m/1h/2h/4h/8h/12h/1d/3d/1wk/1M.
--period=PERIOD1y1d/5d/1mo/3mo/6mo/1y/2y/5y/10y/ytd/max.

Both timeframe flags are validated — bad values exit 2 with a friendly error. For intraday (--interval=1h), bump --period to 6mo or 1y; yfinance caps hourly at ~2y and anything sub-hour at ~60d.

Composes

L2 SkillPurpose
market-exhaustionDetect exhaustion pattern (blowoff, capitulation, impulse)
market-s-rIdentify nearest support/resistance for reversal level
market-trendAssess trend strength for extension context

Entry Logic

  • Short: exhaustion blowoff + price above resistance + extended uptrend
  • Long: exhaustion capitulation + price below support + extended downtrend
  • Stop: beyond the extreme candle high/low (~1 ATR)
  • Targets: return to nearest EMA, 1:1 R:R

Output

  • ideas[] — trade ideas with direction, conviction, entry/stop/target, reasoning
    • Each idea carries version: "v1".."v5" derived from conviction via analysis.contracts.conviction_version()
    • Each idea carries take_profit_ideal (unrounded construction) and rr_to_tp: [rr_to_tp1, rr_to_tp2, rr_to_tp3] (precomputed R:R to each TP via analysis.contracts.compute_rr_to_tp()) so consumers can read a canonical R:R without reimplementing the direction-asymmetric formula
    • Each idea is validated against validate_l3_tp_ladder() (TP3 ≥ entry × 1.05 long, or ≤ entry × 0.95 short)
  • narrative — summary for user briefing

Output envelope (AXI)

--json output follows the canonical AXI envelope — {data, count, errors, help[]}. Default schema is the per-skill minimal fields (3-6 essentials); pass --fields=<csv> to project or --full for the full payload. count is the item count, help[] is contextual next-step command templates. Lib.py return shapes (L1Result / L2Result / L3Result / L3Idea / RegimeSignal) are unchanged — the envelope wraps them at the scripts/run.py boundary.

Home view (no-arg mode)

No-arg mode prints the home view from $XDG_DATA_HOME/market-skills/<skill>_last.json (last successful run). Errors are not cached.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.