OpenClaw Binance

实时监控币安量化交易策略，分析表现，生成风险报告并推送多渠道风险预警。

Security Scan

The skill mostly does what its name says (fetch Binance data, analyze and send a Feishu webhook) but there are inconsistent instructions, unused/extra configuration and imports that don't match the declared behavior — so review before installing or supplying real API keys.

Purpose & Capability

The skill's stated purpose (real-time Binance monitoring, reports and multi-channel alerts) broadly matches the included code: main.py fetches Binance klines, computes basic metrics, saves a markdown report and posts a Feishu webhook. However the README/SKILL.md and skill.json advertise multi-channel push (email, SMS, scheduling, custom strategies) that are not implemented (the code only posts to a FEISHU_WEBHOOK_URL). The skill.json lists openclaw-sdk as a dependency, which is present in main.py as an import but not used. These extra claims/configs are disproportionate to the actual code.

Instruction Scope

SKILL.md instructs the user to modify config.example.json and run python main.py, but main.py actually looks for config.json and exits if it does not exist — SKILL.md omits the required rename/creation step. SKILL.md also instructs copying to a specific Windows path (C:\Users\admin\.openclaw\workspace\) even though the code uses the current working directory; this is inconsistent. The instructions tell the user to place API Key/Secret in a file (config.json) with no guidance on protecting those secrets. There is no instruction to use Binance API keys with withdrawals disabled or to use testnet keys.

Install Mechanism

There is no install spec (instruction-only skill), and included files are plain Python code and a requirements.txt. No downloads from external/untrusted URLs or archive extraction are specified. The installation surface is limited to running python with listed packages.

Credentials

The skill does not declare any required environment variables or primary credential in registry metadata, yet it requires Binance API_KEY and SECRET_KEY in a local config.json (config.example.json shows those keys). The config.example.json also includes OPENCLAW_GATEWAY, which is not used by main.py, and main.py imports openclaw_sdk but never uses it — these extra credential/endpoint fields are unexplained and increase risk if misused. The number of required credentials (API key + secret) is appropriate for the purpose, but storing them in a plain config file without guidance is risky.

Persistence & Privilege

The skill does not request always:true, does not modify other skills or system settings, and only writes its own report files to a local data/binance_trades directory. No elevated persistence or cross-skill configuration changes are present.

What to consider before installing

This skill largely implements a simple Binance monitor, but there are a few questionable items you should consider before installing or supplying real API keys: - The README/SKILL.md and skill.json promise broader features (email/SMS alerts, advanced scheduling) that the shipped code does not implement. Expect the code to only fetch hourly klines, compute basic metrics, save a markdown report, and post to a Feishu webhook. - SKILL.md omits that you must rename config.example.json to config.json (main.py will exit if config.json is missing). Follow the code's requirements, not the prose. - The project asks you to put your Binance API key and secret into a local config file. Prefer using API keys with trading-only permissions and withdrawals disabled, or use Binance testnet keys while evaluating. Do not reuse high-privilege keys. - main.py imports openclaw_sdk and config.example.json contains OPENCLAW_GATEWAY, but the code does not use them — this unexplained leftover could indicate incomplete code or planned behavior not yet implemented. Treat it as a warning: review the code for modifications before running. - The code writes reports to a data/binance_trades folder in the running directory and will make outbound HTTPS requests to Binance (via python-binance) and to the configured Feishu webhook. If you plan to run this, run it in an isolated account or VM and inspect the config file for any webhook/endpoint values you do not recognize. - If you want to proceed: (1) review the main.py source yourself, (2) create API keys with minimal permissions, (3) run in a safe environment, and (4) consider adding secrets-management (env vars or OS-protected vault) instead of storing keys in plaintext.

币安量化交易监控系统

概述

本技能用于实时监控币安交易所的量化交易策略，分析交易数据，生成风险报告并推送至指定渠道。支持自定义交易策略、风险阈值和通知方式。

功能特性

• ✅ 实时监控币安交易对价格和成交量
• ✅ 分析交易策略表现（胜率、盈亏比、最大回撤等）
• ✅ 生成每日/每小时交易报告
• ✅ 支持风险预警推送（飞书、邮件、短信等）
• ✅ 可配置多种交易策略和参数

使用方法

1. 将本目录复制到 C:\Users\admin\.openclaw\workspace\
2. 在币安官网获取API密钥（API Key 和 Secret Key）
3. 修改 config.example.json 中的币安API密钥
4. 运行 python main.py 开始监控

版本历史

v1.0.0 (2026-02-23)

• 初始版本，支持基础交易监控和报告生成
• 完成核心功能验证
• 增加定时任务配置

支持与反馈

联系：旺财助手 (coder YiBai) 邮箱：[e-mail] GitHub：https://github.com/yibaig/

🚀 本技能已通过OpenClaw测试，稳定可靠！