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

order-blocks

Skill17 starsChanged 4 months agoApache-2.0View on GitHub

Define and test ICT-style order-block candle zones. Use when labeling the last opposite candle before an objective displacement and structure break, without inferring hidden institutional orders.

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:

    Break of Structure: use an objective pivot and closed-bar buffer

    line 31
  2. Distinctive:

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

    line 50
  3. Distinctive:

    Do not describe the zone as unfilled institutional inventory without order-level evidence.

    line 58
  4. Distinctive:

    Test first and later retests with an expiry rule.

    line 59

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

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

Order Blocks Trading

A candle-zone heuristic conventionally defined before a displacement and structure break. OHLC data cannot establish that institutional orders remain there or caused a later reaction.

Identification

Bullish Order Block

  1. Find the last bearish candle before a strong upward move
  2. The move must break previous structure (higher high)
  3. Zone = open to low of that bearish candle

Bearish Order Block

  1. Find the last bullish candle before a strong downward move
  2. The move must break previous structure (lower low)
  3. Zone = open to high of that bullish candle

Validation

  • Displacement: normalize return/range by ATR and elapsed bars
  • Break of Structure: use an objective pivot and closed-bar buffer
  • Retest count/age: record continuously and test first versus later returns
  • Context state: define higher timeframe objectively and test its incremental value

Workflow

  1. Identify the zone with fixed timeframe, OHLC boundary, pivot, and displacement rules
  2. Get candle data around the zone:
    get_candles_around_date(symbol=<symbol>, exchange=<exchange>, interval=<interval>, date=<date>)
  3. Mark the zone using draw_chart_analysis with type demand (bullish) or supply (bearish)
  4. Wait for price to return to the order block zone
  5. Confirm entry with LTF structure shift, rejection wicks, or volume increase
  6. Stop loss below/above the order block
  7. Target next opposing order block or liquidity level

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 an order block as a reproducible candle-zone heuristic, not proof of unfilled institutional orders. Order-flow research relates price impact to observable imbalance and market depth.

Key Rules

  • Do not describe the zone as unfilled institutional inventory without order-level evidence.
  • Test first and later retests with an expiry rule; keep failures in the sample.
  • Define context and entry confirmation before evaluation and use closed bars.
  • Quantify displacement in normalized units rather than a universal candle count.

Related Skills

  • fair-value-gaps — test overlap between two explicitly defined candle-zone conventions
  • market-structure-shift — BOS/CHoCH confirms the displacement that validates an OB

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.