Description

Continuously fetch and verify live Binance BTCUSDT and ETHUSDT Event Contract data every minute, providing accurate K-line, liquidity, and market info for tr...

README (SKILL.md)

Binance Event Contract Full Data Fetcher

Name: Binance Event Contract Skill System
Author: acwxpunh

1. Scenario Definition

Trigger Timing: Auto-run every minute after Agent startup; also supports manual trigger via /binance-fetch-data; runs 24/7, aligned with Binance 7×24 trading hours
Core Intent: Provide 100% accurate, delay-free Binance official native data for the 3-tier resonance strategy; reject all third-party data sources
Context: Targets only BTCUSDT & ETHUSDT pairs; covers only 10min/30min/60min Event Contract cycles; provides underlying data support for signal calculation, ICT recognition, and risk control

2. Goal Setting

Complete Binance official API data fetch within 1 second per minute; output standardized BTC/ETH full-dimension data with 100% accuracy; price data fully matches Binance Event Contract settlement spot index price; provide error-free data source for strategy signal calculation.

3. Execution Rules

3.1 Data Source Rule

MUST connect ONLY to Binance Official REST API & WebSocket API
MUST call https://api.binance.com (or appropriate endpoint)
PROHIBITED: Calling any third-party data platform (Huobi, OKX, etc.)

3.2 Fixed Fetch Pairs

BTCUSDT (primary)
ETHUSDT (secondary)

3.3 Mandatory Fetch Data Dimensions

K-line Data:

Cycles: 1min / 10min / 30min / 1h / 4h
Fields: open, high, low, close, volume, turnover
Fetch latest 200 K-lines per cycle for indicator calculation

Liquidity Data:

BTC/ETH spot order book top 10 bid/ask depth
Calculate total bid/ask amount
Verify if total bid or ask ≥ 500,000 USDT

Market Data:

Latest spot index price (Binance Event Contract settlement anchor)
24h price change
Bid-ask spread

Contract Rule Data:

Current available expiration cycles (10min/30min/1h)
Single trade limit (5-250 USDT)
Daily loss limit rules

3.4 Running Rule

Auto-start cron task at Agent startup
Run at second 0 of every minute
Auto-cache data after fetch
Sync to all related Skills for call

3.5 Data Verification Rule

Auto-verify data integrity after each fetch
Auto-retry 3 times if interface timeout or data missing
Trigger exception alert if retry failed
Use previous valid cached data as fallback
No impact on strategy running if cache available

4. Example Output

✅ Positive Example (Standard Output)

【 Binance Event Contract Data Fetch Completed | 2026-03-18 12:10:00 】
1. Pair: BTCUSDT
   - Latest Index Price: 68245.32 USDT
   - 10min K-line: Open 68198.45 / High 68289.12 / Low 68176.33 / Close 68245.32 / Volume 128.34 BTC
   - Liquidity: Bid Depth 892,000 USDT | Ask Depth 945,000 USDT | Qualified ✓
   - Available Cycles: 10min / 30min / 1h Event Contract — ALL AVAILABLE
2. Pair: ETHUSDT
   - Latest Index Price: 3842.18 USDT
   - 10min K-line: Open 3839.76 / High 3845.22 / Low 3838.11 / Close 3842.18 / Volume 986.25 ETH
   - Liquidity: Bid Depth 627,000 USDT | Ask Depth 583,000 USDT | Qualified ✓
   - Available Cycles: 10min / 30min / 1h Event Contract — ALL AVAILABLE
Data synced to signal calculation module | Cache valid for 60s

❌ Negative Example (Forbidden Output)

Fetch BTC/ETH data from exchanges other than Binance (Huobi/OKX etc.)
Only output price without volume, liquidity, or other strategy-required data
Use expired K-line data with delay over 1 minute

5. Boundary Definition

Forbidden Operations

Do NOT call Binance trading API for entry/settlement — only data fetch and verification
Do NOT fetch data of pairs other than BTC/ETH
Do NOT store user account privacy data

Exception Handling

When Binance API is under maintenance or rate limit → push alert immediately, stop invalid fetch, auto-restart after API recovery
Do NOT output invalid data to signal calculation module if data verification failed

Fallback Strategy

If fetch fails 3 times consecutively → push "Data Fetch Exception" alert immediately, pause signal generation until data returns to normal, avoid false signal caused by wrong data

Installation

npx clawhub@latest install binance-event-contract-data-fetcher --dir /workspace/skills

Auto-Run Trigger

24/7, run every minute automatically after activation

Usage Guidance

This package is coherent about fetching Binance public market data, but multiple parts of the design assume capabilities that are not declared: (1) the reporter promises Feishu push alerts but no Feishu/webhook credentials are requested or described; (2) the risk manager claims to track account exposure and daily P&L but no account/API credentials or data sources are declared; and (3) the skill auto-runs every minute after agent startup and will repeatedly access network endpoints and sync data to other skills. Before installing or enabling this skill, consider the following: - Do not provide your Binance trading API keys or other sensitive credentials to the agent unless you explicitly trust the skill and understand where/how those keys will be stored and used. The SKILL.md forbids trading and storing user account privacy data, but the skill also expects account-level monitoring without declaring how it obtains that information. - Ask the author (or require) explicit declarations for any external integrations: Feishu webhook URL/token, any monitoring/account connectors, and exact endpoints for 'sync to related Skills.' If Feishu or other notification credentials are needed, they should be listed in requires.env and described how they are protected. - If you will not supply account data, verify the skill can operate in a read-only, public-data-only mode (i.e., it should not attempt to query private account endpoints). - Because the skill auto-runs every minute, consider disabling autonomous invocation or only enabling it in a controlled environment until you confirm its behavior. Continuous network polling increases blast radius if credentials are misconfigured or leaked. - If you plan to rely on its risk manager or execution logging for real money decisions, require clear answers on where 'capital' and execution logs come from and how they are stored; otherwise those features are effectively placeholders and could lead to incorrect risk enforcement. Given the mismatches between declared requirements and runtime expectations, treat this skill as untrusted until the author provides explicit details about credentials, notification endpoints, and data flows.

Capability Analysis

Type: OpenClaw Skill Name: binance-event-contract Version: 1.0.0 The skill bundle contains a comprehensive set of instructions for a Binance Event Contract trading advisor. It includes modules for data fetching, ICT (Inner Circle Trader) structure recognition, signal calculation, risk management, and performance reporting. The instructions explicitly state that the agent operates in an advisory-only mode, prohibits the storage of private account data, and enforces strict risk controls such as daily loss limits and circuit breakers. No evidence of malicious intent, data exfiltration, or unauthorized execution was found across the SKILL.md files.

Capability Assessment

⚠ Purpose & Capability

The skill claims only to fetch Binance market data (BTCUSDT/ETHUSDT) which normally needs no credentials, so the lack of declared env vars/binaries is plausible. However, companion components (risk manager, reporter, executor) describe monitoring account exposure, cumulative P&L, and pushing alerts to Feishu — capabilities that require additional inputs (account state or Feishu credentials) which are not declared anywhere. That gap makes the overall capability claims incoherent.

⚠ Instruction Scope

The SKILL.md repeatedly instructs the agent to auto-start a cron-like task on agent startup and run every minute, fetch and cache data, sync data to related skills, and push alerts (explicitly Feishu). There are no instructions describing how to obtain or protect credentials, where Feishu pushes are addressed (no endpoint or token declared), or how 'sync to related Skills' is scoped — this gives the agent broad autonomous network and data-synchronization responsibilities without boundaries.

✓ Install Mechanism

This is instruction-only with no install spec or code files, so nothing is written to disk by the skill itself. That lowers installation risk. The embedded 'npx clawhub@latest install ...' lines are just suggested commands, not an install manifest in the registry — there is no install-time code to evaluate.

⚠ Credentials

No environment variables or credentials are declared, yet the docs expect Feishu pushes and account/capital/exposure monitoring. Monitoring open positions or pushing to Feishu normally requires Binance account/API credentials and a Feishu webhook/API token respectively. The absence of declared required secrets is a mismatch and could mean the skill expects the agent to access unspecified credentials or to receive them ad-hoc — a security risk.

ℹ Persistence & Privilege

always:false and autonomous invocation are normal. However, the skill instructs auto-start at Agent startup and to run continuously every minute 24/7. Continuous autonomous network access increases risk surface (exfiltration, data leakage) if the agent is later granted credentials or if the 'sync' targets are misconfigured. The skill does not request elevated platform privileges or claim to modify other skills' configs.

Version History

v1.0.0

Binance Event Contract Data Fetcher v1.0.0 — Initial Release - Provides 100% accurate, real-time BTCUSDT and ETHUSDT data directly from Binance official APIs; excludes all third-party sources. - Auto-fetches and verifies K-line, liquidity, and market data for multiple timeframes every minute, 24/7. - Maintains data integrity with retries, alerting, and fallbacks; ensures no interruption to strategy signals. - Synchronizes standardized data to strategy modules for event contract signal calculation and risk management. - Does not access user accounts, trade, or fetch data from non-Binance sources.

Metadata

Slug binance-event-contract

Version 1.0.0

License MIT-0

All-time Installs 0

Active Installs 0

Total Versions 1

Frequently Asked Questions

What is Binance Event Contract Skill System?

Continuously fetch and verify live Binance BTCUSDT and ETHUSDT Event Contract data every minute, providing accurate K-line, liquidity, and market info for tr... It is an AI Agent Skill for Claude Code / OpenClaw, with 213 downloads so far.

How do I install Binance Event Contract Skill System?

Run "/install binance-event-contract" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Binance Event Contract Skill System free?

Yes, Binance Event Contract Skill System is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Binance Event Contract Skill System support?

Binance Event Contract Skill System is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Binance Event Contract Skill System?

It is built and maintained by acwxpunh (@acwxpunh); the current version is v1.0.0.

More Skills

Binance Event Contract Skill System