agentleFS
SKE-LabsSKE-Labs/agent-trading-skills/skills/ict-smart-money/kill-zones/SKILL.md

kill-zones

Skill17 starsChanged 4 months agoApache-2.0View on GitHub

Analyze intraday session seasonality and test time-window filters. Use when timing a strategy around exchange, London, New York, or Asian trading sessions with correct timezone and daylight-saving handling.

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:

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

    line 42
  2. Distinctive:

    Do not call opening moves manipulation without order-level evidence.

    line 50
  3. Distinctive:

    Never assume London or another session is most profitable.

    line 52
  4. Distinctive:

    Treat time-window and structural labels as features whose incremental value must be tested.

    line 54

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

Kill Zones Trading

Named session windows used by ICT-style traders. Activity, volatility, spreads, and returns vary intraday, but the best window is instrument-, venue-, season-, and strategy-specific.

Session Schedule

SessionReference windowRequired handling
AsianRelevant exchange/local sessionExchange holidays and product hours
LondonEurope/London local timeConvert with historical/current DST
New YorkAmerica/New_York local timeConvert with historical/current DST

Define candidate window boundaries in local session time, then convert every timestamp with a timezone database. Do not publish fixed UTC windows across DST changes.

Session Behaviors

For each instrument, measure time-of-day median volume, spread, realized volatility, jump frequency, and the strategy's net returns. Treat prior-session ranges and sweeps as hypotheses; sessions do not create a mandatory daily direction.

Workflow

  1. Pre-session: Mark Asian session high/low, identify HTF key levels, note scheduled news events
    get_candles_around_date(symbol=<symbol>, exchange=<exchange>, interval="15m", date=<asian_session_date>)
  2. Session open: measure spread, volatility, and any predeclared sweep; do not label price discovery manipulation
  3. Entry timing: apply the strategy's calibrated window and closed-bar trigger
  4. Session context:
    • Record which prior-session levels were crossed and whether price closed back inside
    • Estimate subsequent-return distributions without imposing bullish/bearish labels

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: Ito & Hashimoto documents intraday seasonality in FX activity, volatility, and spreads; it does not establish universal profitable windows or a mandatory direction.

Key Rules

  • Do not call opening moves manipulation without order-level evidence.
  • Allow trades outside named windows when the validated strategy and liquidity gates pass.
  • Never assume London or another session is most profitable; show instrument-specific held-out results.
  • Include DST, holidays, half-days, venue hours, and scheduled announcements.
  • Treat time-window and structural labels as features whose incremental value must be tested.

Related Skills

  • liquidity-zones — Kill zone opens frequently sweep Asian session liquidity before reversing
  • market-structure-shift — test objective structure events inside the chosen session window

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.