market-structure-shift
Skill17 starsChanged 4 months agoApache-2.0View on GitHub
Detect Break of Structure (BOS) and Change of Character (CHoCH) for trend analysis. Use when identifying trend reversals, confirming entry signals, or determining market bias direction.
1 other project uses a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- IngAs8/ClaudeSkilledited, first seen Sep 28, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 1
- IngAs8/ClaudeSkill★ 051% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository56 other files it gives its agents.
- candlestick-patternsSkill
- channel-tradingSkill
- cup-and-handleSkill
- double-top-bottomSkill
- flag-pennantSkill
- head-and-shouldersSkill
- triangle-patternsSkill
- wedge-patternsSkill
- altcoin-rotationSkill
- arbitrage-tradingSkill
- dca-strategySkill
- funding-rate-tradingSkill
- on-chain-analysisSkill
- breakout-tradingSkill
- gap-tradingSkill
- momentum-tradingSkill
- news-tradingSkill
- pullback-tradingSkill
- range-tradingSkill
- scalping-strategySkill
- earnings-tradingSkill
- economic-calendar-tradingSkill
- insider-activity-tradingSkill
- market-correlation-tradingSkill
- sector-rotationSkill
- sentiment-analysisSkill
- breaker-blocksSkill
- fair-value-gapsSkill
- kill-zonesSkill
- liquidity-zonesSkill
- optimal-trade-entrySkill
- order-blocksSkill
- premium-discountSkill
- correlation-riskSkill
- drawdown-managementSkill
- leverage-managementSkill
- partial-profit-takingSkill
- position-sizingSkill
- risk-reward-ratioSkill
- stop-loss-strategiesSkill
- trailing-stopSkill
- bollinger-bandsSkill
- divergence-tradingSkill
- fibonacci-tradingSkill
- ichimoku-cloudSkill
- macd-tradingSkill
- market-regime-detectionSkill
- mean-reversionSkill
- moving-average-crossoverSkill
- multi-timeframe-analysisSkill
- rsi-divergenceSkill
- stochastic-tradingSkill
- supply-demand-zonesSkill
- volume-profile-tradingSkill
- vwap-tradingSkill
- skill-nameSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 8 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 39
Detect structure breaks: only after a closed bar exceeds the pivot by a calibrated tick/ATR buffer.
- Distinctive: line 43
Wait for the closed-bar BOS trigger
- Distinctive: line 45
Stop below recent swing low (bull) or above swing high (bear)
- Distinctive: line 48
Treat HTF CHoCH as a candidate reversal condition
- Distinctive: line 49
Wait for LTF BOS in the new direction
- Distinctive: line 51
Stop beyond the CHoCH swing point
- Distinctive: line 55
Treat the setup as a testable hypothesis, not a prediction.
- Distinctive: line 64
Never use an unconfirmed right-edge pivot or intrabar break.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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 Structure Shift
Identify trend direction and potential reversals through swing point analysis.
Structure
Swing Points
- Higher High (HH) + Higher Low (HL) = Uptrend
- Lower Low (LL) + Lower High (LH) = Downtrend
Choose an objective swing algorithm before analysis—for example, a pivot with fixed left/right bars or an ATR-reversal rule. State how equal highs/lows, nested swings, and the unconfirmed final pivot are handled.
Break of Structure (BOS)
- Descriptive continuation label under the chosen swing rule
- Bullish BOS: Price breaks above swing high (HH)
- Bearish BOS: Price breaks below swing low (LL)
Change of Character (CHoCH)
- Descriptive possible-change label, not confirmation of reversal
- Bullish CHoCH: In downtrend, price breaks above LH
- Bearish CHoCH: In uptrend, price breaks below HL
Workflow
- Identify current trend on a predeclared context timeframe:
get_candles_around_date(symbol=<symbol>, exchange=<exchange>, interval="4h", date=<date>) - Mark swing points using
draw_chart_analysiswithhighlighttype (label HH, HL, LH, LL) - Detect structure breaks only after a closed bar exceeds the pivot by a calibrated tick/ATR buffer.
- Map nested timeframes with exact ratios and timestamps. If context and execution structure conflict, return
watchorno trade; do not force alignment.
Trend Continuation Entry (BOS)
- Wait for the closed-bar BOS trigger
- Enter on pullback to FVG or order block
- Stop below recent swing low (bull) or above swing high (bear)
Trend Reversal Entry (CHoCH)
- Treat HTF CHoCH as a candidate reversal condition
- Wait for LTF BOS in the new direction
- Enter on retracement to CHoCH level
- Stop beyond the CHoCH swing point
Evidence and Validation
- Treat the setup as a testable hypothesis, not a prediction. Define thresholds, entry, invalidation, and exit before evaluating outcomes.
- Calibrate on the same instrument, venue, session, and timeframe. Use closed candles and a held-out or walk-forward sample; record every variant tried.
- Include spread, fees, slippage, borrow or funding, partial fills, and latency. Reject the setup when net expectancy is not positive or depends on one narrow parameter.
- Return observed inputs, missing data, cost assumptions, entry, invalidation, exit, and a valid, watch, or no-trade status.
- Research basis: Use BOS/CHoCH as explicit swing-labeling rules. Lo, Mamaysky & Wang shows why visual price patterns must be algorithmically defined and tested.
Key Rules
- The context timeframe supplies a feature, not an immutable direction.
- Never use an unconfirmed right-edge pivot or intrabar break.
- Predeclare whether a single close, retest, or second-timeframe event is required; avoid future leakage.
- Select timeframes for the instrument/session and test nested conflicts explicitly.
Related Skills
- order-blocks — define and test candle zones around objective structure events
- liquidity-zones — Structure breaks often occur after liquidity sweeps of swing points
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.

