agentleFS
SKE-LabsSKE-Labs/agent-trading-skills/skills/ict-smart-money/breaker-blocks/SKILL.md

breaker-blocks

Skill17 starsChanged 4 months agoApache-2.0View on GitHub

Define and test breaker-block polarity-flip setups. Use when a previously labeled candle zone is crossed and later retested as support or resistance.

1 other project uses a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    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
  1. Distinctive:

    Use a closed-bar crossing buffer and prevent future bars from changing the original label.

    line 33
  2. Distinctive:

    Treat the setup as a testable hypothesis, not a prediction.

    line 50
  3. Distinctive:

    Do not claim knowledge of trapped traders or hidden order intent from candles alone.

    line 58
  4. Distinctive:

    Test first and later retests separately rather than assuming only the first works.

    line 60

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Breaker Blocks Trading

A discretionary label for a candle zone that is crossed and later tested from the opposite side. It is a support/resistance hypothesis, not evidence of trapped or institutional orders.

Identification

Bullish Breaker (Failed Bearish OB)

  1. Bearish order block forms
  2. Price returns and breaks through the OB aggressively (displacement)
  3. The broken OB flips to support (bullish breaker)
  4. Trade longs when price returns to this zone

Bearish Breaker (Failed Bullish OB)

  1. Bullish order block forms
  2. Price returns and breaks through the OB aggressively (displacement)
  3. The broken OB flips to resistance (bearish breaker)
  4. Trade shorts when price returns to this zone

Testable Features

  • Normalize break distance and speed by ATR and elapsed bars.
  • Define the zone from exact OHLC fields and an objective swing rule.
  • Record overlap with an FVG, higher-timeframe state, and retest count as candidate features—not quality grades.
  • Use a closed-bar crossing buffer and prevent future bars from changing the original label.

Workflow

  1. Find a failed order block using candle data:
    get_candles_around_date(symbol=<symbol>, exchange=<exchange>, interval=<interval>, date=<date>)
  2. Confirm the break with the predeclared swing and close-plus-buffer rule
  3. Mark the breaker zone using draw_chart_analysis with demand (bullish) or supply (bearish)
  4. Wait for price to return to the zone from the opposite side
  5. Enter with LTF confirmation (structure shift or rejection)
  6. Stop loss beyond the breaker zone
  7. Target next liquidity level or POI

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: Treat breaker blocks as a discretionary support/resistance labeling convention. Lo, Mamaysky & Wang supports objective pattern testing, not claims about hidden institutional intent.

Key Rules

  • Do not claim knowledge of trapped traders or hidden order intent from candles alone.
  • Define displacement in ATR and bars before testing.
  • Test first and later retests separately rather than assuming only the first works.
  • Return no trade when swing, break, retest, liquidity, or cost definitions are incomplete.

Related Skills

  • order-blocks — Breakers are failed OBs; understanding OBs is prerequisite
  • fair-value-gaps — FVGs created during the break add confluence to breaker zones

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.