market-exhaustion
Skill3 starsChanged 4 months agoMITView on GitHub
Detects whether a price move is about to end by composing L1 indicators: volume climax, RSI extremes, narrowing range, momentum divergence, and sentiment extremes. Classifications: CAPITULATION_BOTTOM, BLOWOFF_TOP, IMPULSE_EXHAUSTION, PULLBACK_EXHAUSTED.
In this repository47 other files it gives its agents.
- AGENTS.mdAGENTS.md
- beadsSkill
- backtest-engineSkill
- backtest-pipelineSkill
- backtest-trend-minerSkill
- bug-scanSkill
- daily-trade-pickSkill
- execution-kraken-perpsSkill
- execution-kraken-spotSkill
- l3-conviction-scanSkill
- market-accumulationSkill
- market-basisSkill
- market-breadthSkill
- market-breakoutSkill
- market-emaSkill
- market-fibonacciSkill
- market-liquidity-sweepSkill
- market-macdSkill
- market-macroSkill
- market-moversSkill
- market-notesSkill
- market-overviewSkill
- market-rsiSkill
- market-snapshotSkill
- market-squeezeSkill
- market-s-rSkill
- market-stateSkill
- market-trend-qualitySkill
- market-trendSkill
- market-valuationSkill
- market-volatilitySkill
- market-volumeSkill
- market-watchlistSkill
- portfolio-mgmtSkill
- position-watchdogSkill
- risk-engineSkill
- run-all-l2Skill
- run-all-l3Skill
- run-watchlistSkill
- strategy-accumulation-swingSkill
- strategy-breakout-confirmSkill
- strategy-exhaustion-fadeSkill
- strategy-fitness-heatmapSkill
- strategy-funding-carrySkill
- strategy-liquidity-sweepSkill
- strategy-mean-reversionSkill
- strategy-trend-followSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 19
Do not fade an exhaustion signal while the underlying trend is still strong (e.g.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
market-exhaustion
L2 pattern detection skill that composes L1 indicators to determine whether a price move is approaching exhaustion.
When NOT to use
- This is pattern detection, not a trade idea — feed a fired pattern into
strategy-exhaustion-fadeorrun-all-l3before acting. - Do not fade an exhaustion signal while the underlying trend is still strong (e.g. a
BLOWOFF_TOPin a structural uptrend) — exhaustion can extend far before reversing. Confirm withmarket-trendandmarket-s-rlevels. - An exhaustion classification is a contrarian hint, not confirmation; require a clear S/R level and reversal structure before treating it as actionable.
Quick Start
uv run skills/market-exhaustion/scripts/run.py SPY
uv run skills/market-exhaustion/scripts/run.py SPY --jsonFlags
| Flag | Default | Notes |
TICKER (positional) | — | Required. Supports provider:ticker (e.g. hl:LIT, yf:AAPL). |
--json | human | Emit JSON to stdout. |
--source=PROVIDER | auto-detect | Force a data provider (see README). |
--interval=INTERVAL | 1d | 1m/2m/5m/15m/30m/1h/2h/4h/8h/12h/1d/3d/1wk/1M. |
--period=PERIOD | 1y | 1d/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.
Sub-Signals
| Sub-signal | Weight | Source L1 |
| Volume climax (volume_ratio >= 2.5 or regime == CLIMAX) | 0.30 | market-volume |
| RSI extreme (rsi < 30 or rsi > 70) | 0.25 | computed directly via analysis.indicators |
| Narrowing range (volatility regime == LOW) | 0.20 | market-volatility |
| Momentum divergence (histogram_flip exists) | 0.15 | market-macd |
| Sentiment extreme (fear_greed < 25 or > 75) | 0.10 | market-fear-greed (optional) |
Classifications
- CAPITULATION_BOTTOM: RSI oversold + volume climax
- BLOWOFF_TOP: RSI overbought + volume climax
- IMPULSE_EXHAUSTION: momentum divergence detected
- PULLBACK_EXHAUSTED: general exhaustion pattern present
Trigger
pattern.present is True when at least 2 sub-signals are present AND their
combined weight exceeds 0.30. The previous weighted_sum / total_weight >= 0.5
threshold silently dropped 2-sub combinations at weighted_sum in
(0.30, 0.50) — e.g. rsi_extreme + momentum_divergence (0.4445) and
narrowing_range + momentum_divergence (0.3889) — into present=False
while the sub-signals were populated.
confidence is round(weighted_sum * 5), clamped to [1, 5].
Output
Returns pattern presence, confidence (1-5), classification, sub-signal states, input scores from each L1, and a one-sentence narrative.
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.
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
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.

