技能详情（站内镜像，无评论）
许可证：MIT-0
MIT-0 ·免费使用、修改和重新分发。无需归因。
版本：v1.0.0
统计：⭐ 0 · 28 · 0 current installs · 0 all-time installs
⭐ 0
安装量（当前） 0
🛡 VirusTotal ：良性 · OpenClaw ：可疑
Package：acwxpunh/binance-event-contract
安全扫描（ClawHub）
- VirusTotal ：良性
- OpenClaw ：可疑
OpenClaw 评估
The skill's stated purpose (fetching Binance market data) is plausible, but multiple runtime instructions (reporting to Feishu, tracking account capital/exposure, and continuous auto-run) are not matched by any declared credentials, config, or installation — this mismatch is inconsistent and warrants caution.
目的
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 o…
说明范围
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-sync…
安装机制
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.
证书
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.
持久
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.
安装（复制给龙虾 AI）
将下方整段复制到龙虾中文库对话中，由龙虾按 SKILL.md 完成安装。
请把本段交给龙虾中文库（龙虾 AI）执行：为本机安装 OpenClaw 技能「Binance Event Contract Skill System」。简介：Continuously fetch and verify live Binance BTCUSDT and ETHUSDT Event Contract d…。
请 fetch 以下地址读取 SKILL.md 并按文档完成安装：https://raw.githubusercontent.com/openclaw/skills/refs/heads/main/skills/acwxpunh/binance-event-contract/SKILL.md
（来源：yingzhi8.cn 技能库）SKILL.md
# Binance Event Contract Full Data Fetcher
## 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
1. Do NOT call Binance trading API for entry/settlement — only data fetch and verification
2. Do NOT fetch data of pairs other than BTC/ETH
3. Do NOT store user account privacy data
### Exception Handling
1. When Binance API is under maintenance or rate limit → push alert immediately, stop invalid fetch, auto-restart after API recovery
2. 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
```bash
npx clawhub@latest install binance-event-contract-data-fetcher --dir /workspace/skills
```
## Auto-Run Trigger
24/7, run every minute automatically after activation