Binance ICT Structure Recognizer

Automatically identifies ICT structures like Order Blocks, FVGs, and liquidity sweeps on Binance BTC/ETH 1H data to verify SSS tier signals.

Security Scan

The skill's instructions and claims contain multiple incoherences (undeclared dependencies, contradictory rules about issuing trade signals, and mismatched install metadata) that don't line up with its stated purpose.

Purpose & Capability

The SKILL.md requires data 'MUST only use Binance official BTC/ETH K-line data from `binance-event-contract-data-fetcher` Skill' and expects automatic triggering when an 'SSS tier' signal is calculated, but the registry metadata lists no dependency on that other skill or any signal-calculator integration. The install example uses a different package name ('binance-event-contract-ict-recognizer' vs registry slug 'binance-event-contract-ict'), which is inconsistent. These omissions mean the declared purpose (verifying SSS signals using a specific data fetcher and signal calculator) is not fully supported by the declared requirements.

Instruction Scope

The runtime instructions forbid issuing trading signals ('FORBIDDEN: Issue trading signals directly — only output ICT structure analysis') yet the positive example includes a concrete trade recommendation (entry, target, SL). The SKILL.md also says to 'Output structured ICT report to risk manager' but provides no mechanism or destination (no env/config declared). The skill mandates only using a particular other skill for data, but gives no guidance how to access that skill's data (no declared APIs, calls, or inter-skill contract). These contradictions and omissions create ambiguous agent behavior and scope creep.

Install Mechanism

There is no platform install spec and no code files (instruction-only), which lowers installation risk. However the SKILL.md includes a human-facing install example using npx with a package name that doesn't match the registry slug, indicating sloppiness or a packaging mismatch that should be clarified before installation.

Credentials

The skill requests no environment variables or credentials, yet it expects automated triggers, integration with a separate 'data-fetcher' skill and a 'risk manager' destination. If the skill actually needs to call external endpoints or other skills, appropriate credentials/config should be declared. The absence of any declared env/config for integrations is disproportionate to the intended automated behavior and is an omission that could hide necessary permissions or secret access.

Persistence & Privilege

The skill does not request always:true and declares no special system persistence or privileges; it is user-invocable and can be invoked autonomously (platform default). On its own this is not a red flag, but combined with the other inconsistencies it increases the need for clearer dependency and data-flow declarations.

What to consider before installing

This skill is instruction-only and doesn't present obvious code-level malware, but it contains several incoherences you should resolve before installing or enabling it: (1) Ask the author to declare and link the required dependencies (the 'binance-event-contract-data-fetcher' skill and the SSS signal-calculator) and explain how the agent should access those skills' data. (2) Fix the contradictory rule that forbids issuing trade signals while the example gives a trade recommendation — decide whether the skill should only report structures or also suggest trades. (3) Correct the install/package name mismatch and provide a proper install spec if code is needed. (4) Specify where the 'structured ICT report' is sent (risk manager) and declare any credentials or endpoints required. (5) Treat the claimed 95–100% accuracy claims skeptically; they are unrealistic and don't affect security but indicate overconfidence. After these clarifications, re-evaluate; unresolved discrepancies warrant keeping the skill disabled or only using it in an isolated/test environment.

1. Scenario Definition

• Trigger Timing: Auto-trigger when SSS tier signal is calculated; also supports manual trigger via /binance-ict-recognize; runs after each 10min/30min/1h K-line closed; 24/7
• Core Intent: Provide ICT structure verification for SSS tier highest win rate signal; identify Order Blocks, FVG (Fair Value Gap), liquidity sweep zones of Binance BTC/ETH corresponding cycles; improve SSS tier signal win rate
• Context: Only for SSS tier signal of Binance Event Contract 1h cycle; only uses Binance official K-line data; adapts to price fluctuation characteristics of short-term event contracts

2. Goal Setting

Accurately identify ICT core structure of corresponding cycle; provide 100% accurate structure verification for SSS tier signal; filter false signals without ICT structure support; ensure SSS tier signal win rate stable above 95%.

3. Execution Rules

3.1 Data Dependency

• MUST only use Binance official BTC/ETH K-line data from binance-event-contract-data-fetcher Skill
• PROHIBITED: Use any third-party indicator or data source

3.2 Core Recognition Dimensions

Order Block Recognition:

• Identify bullish/bearish valid Order Blocks of corresponding cycle
• Confirm signal trigger after price backtest Order Block
• Tag: Bullish OB (last candle red before bullish candle) | Bearish OB (last candle green before bearish candle)

FVG Recognition:

• Identify Fair Value Gaps (3-candle pattern)
• Bullish FVG: gap between high of candle 1 and low of candle 3
• Bearish FVG: gap between low of candle 1 and high of candle 3
• Calculate FVG fill probability

Liquidity Sweep Zone:

• Identify stop hunt zones above/below key structure
• Detect liquidity sweeps at highs/lows of previous cycle
• Calculate sweep-to-reversal zones

Inducement Identification:

• Identify fake breakouts at key levels
• Detect liquidity grabs at chart patterns

3.3 ICT Signal Scoring

• Score each ICT element: OB (0-40pts), FVG (0-30pts), Liquidity Sweep (0-20pts), Inducement (0-10pts)
• Total Score ≥ 80 = SSS Strong Confirm | 60-79 = SS Confirm | < 60 = No Trade

3.4 Running Rule

• Trigger automatically when SSS signal detected from signal calculator
• Run after each 10min/30min/1h K-line close
• Output structured ICT report to risk manager

4. Example Output

✅ Positive Example

【 ICT Structure Recognition | BTCUSDT 1H | 2026-03-18 12:10 】
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Order Blocks:
  → Bullish OB: Zone 67850-67920 (Price returned, VALID)
  → Bearish OB: Zone 68500-68580 (Not touched, PENDING)

FVG Detection:
  → Bullish FVG: 67980-68100 (Unfilled, HIGH PROBABILITY)
  → Bearish FVG: 68320-68400 (Partially filled, CAUTION)

Liquidity Sweep:
  → Low liquidity sweep at 68150 (逆向吃到流动性)
  → High sweep at 68600 (Inducement detected)

ICT Score: 88/100 → SSS STRONG CONFIRM ✓
Recommendation: Long Entry at OB retest 67850 | Target 68500 | SL 67500

❌ Negative Example

• Recognize ICT patterns using non-Binance data
• Issue trade signal without full ICT scan
• Ignore timeframe confluence (multi-timeframe analysis)

5. Boundary Definition

• FORBIDDEN: Issue trading signals directly — only output ICT structure analysis
• FORBIDDEN: Use timeframe below 10min for SSS tier signals
• Exception: If K-line data missing → output "Data Unavailable" and wait for next close

Installation

npx clawhub@latest install binance-event-contract-ict-recognizer --dir /workspace/skills

Trigger Command

/binance-ict-recognize