← Back to Skills Marketplace
hybrid1labs

Binance Pro (Hybrid Labs)

by HYBRID1LABS · GitHub ↗ · v1.0.0 · MIT-0
cross-platform ⚠ suspicious
85
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install binance-pro-hybrid
Description
Complete Binance integration - world's largest crypto exchange. Trade spot, futures with up to 125x leverage, staking, and portfolio management. Use to check...
README (SKILL.md)

Binance Pro 🟡

Professional skill for trading on Binance - the world's largest crypto exchange.

🚀 Quick Start

Setup Credentials

Save to ~/.openclaw/credentials/binance.json:

{
  "apiKey": "YOUR_API_KEY",
  "secretKey": "YOUR_SECRET_KEY"
}

Environment Variables (alternative)

export BINANCE_API_KEY="your_api_key"
export BINANCE_SECRET="your_secret_key"

📊 Basic Queries

Check Spot Balance

TIMESTAMP=$(date +%s%3N)
QUERY="timestamp=${TIMESTAMP}"
SIGNATURE=$(echo -n "$QUERY" | openssl dgst -sha256 -hmac "$SECRET" | cut -d' ' -f2)

curl -s "https://api.binance.com/api/v3/account?${QUERY}&signature=${SIGNATURE}" \
  -H "X-MBX-APIKEY: ${API_KEY}" | jq '[.balances[] | select(.free != "0.00000000")]'

Get Current Price

curl -s "https://api.binance.com/api/v3/ticker/price?symbol=BTCUSDT" | jq '.'

Get All Futures Positions

TIMESTAMP=$(date +%s%3N)
QUERY="timestamp=${TIMESTAMP}"
SIGNATURE=$(echo -n "$QUERY" | openssl dgst -sha256 -hmac "$SECRET" | cut -d' ' -f2)

curl -s "https://fapi.binance.com/fapi/v2/positionRisk?${QUERY}&signature=${SIGNATURE}" \
  -H "X-MBX-APIKEY: ${API_KEY}" | jq '[.[] | select(.positionAmt != "0")]'

⚡ Futures (Leverage Trading)

Open LONG Position (Buy)

SYMBOL="BTCUSDT"
SIDE="BUY"
QUANTITY="0.001"

TIMESTAMP=$(date +%s%3N)
QUERY="symbol=${SYMBOL}&side=${SIDE}&type=MARKET&quantity=${QUANTITY}&timestamp=${TIMESTAMP}"
SIGNATURE=$(echo -n "$QUERY" | openssl dgst -sha256 -hmac "$SECRET" | cut -d' ' -f2)

curl -s -X POST "https://fapi.binance.com/fapi/v1/order?${QUERY}&signature=${SIGNATURE}" \
  -H "X-MBX-APIKEY: ${API_KEY}" | jq '.'

Open SHORT Position (Sell)

SYMBOL="BTCUSDT"
SIDE="SELL"
QUANTITY="0.001"

TIMESTAMP=$(date +%s%3N)
QUERY="symbol=${SYMBOL}&side=${SIDE}&type=MARKET&quantity=${QUANTITY}&timestamp=${TIMESTAMP}"
SIGNATURE=$(echo -n "$QUERY" | openssl dgst -sha256 -hmac "$SECRET" | cut -d' ' -f2)

curl -s -X POST "https://fapi.binance.com/fapi/v1/order?${QUERY}&signature=${SIGNATURE}" \
  -H "X-MBX-APIKEY: ${API_KEY}" | jq '.'

Set Stop Loss

SYMBOL="BTCUSDT"
SIDE="SELL"  # To close LONG use SELL, to close SHORT use BUY
STOP_PRICE="75000"

TIMESTAMP=$(date +%s%3N)
QUERY="symbol=${SYMBOL}&side=${SIDE}&type=STOP_MARKET&stopPrice=${STOP_PRICE}&closePosition=true&timestamp=${TIMESTAMP}"
SIGNATURE=$(echo -n "$QUERY" | openssl dgst -sha256 -hmac "$SECRET" | cut -d' ' -f2)

curl -s -X POST "https://fapi.binance.com/fapi/v1/order?${QUERY}&signature=${SIGNATURE}" \
  -H "X-MBX-APIKEY: ${API_KEY}" | jq '.'

Set Take Profit

SYMBOL="BTCUSDT"
SIDE="SELL"  # To close LONG use SELL, to close SHORT use BUY
TP_PRICE="85000"

TIMESTAMP=$(date +%s%3N)
QUERY="symbol=${SYMBOL}&side=${SIDE}&type=TAKE_PROFIT_MARKET&stopPrice=${TP_PRICE}&closePosition=true&timestamp=${TIMESTAMP}"
SIGNATURE=$(echo -n "$QUERY" | openssl dgst -sha256 -hmac "$SECRET" | cut -d' ' -f2)

curl -s -X POST "https://fapi.binance.com/fapi/v1/order?${QUERY}&signature=${SIGNATURE}" \
  -H "X-MBX-APIKEY: ${API_KEY}" | jq '.'

Close Position (Market)

# First, get current position quantity
POSITION=$(curl -s "https://fapi.binance.com/fapi/v2/positionRisk?timestamp=${TIMESTAMP}&signature=${SIGNATURE}" \
  -H "X-MBX-APIKEY: ${API_KEY}" | jq -r '.[] | select(.symbol=="BTCUSDT") | .positionAmt')

# If POSITION > 0, it's LONG, close with SELL
# If POSITION \x3C 0, it's SHORT, close with BUY

Change Leverage

SYMBOL="BTCUSDT"
LEVERAGE="10"  # 1 to 125

TIMESTAMP=$(date +%s%3N)
QUERY="symbol=${SYMBOL}&leverage=${LEVERAGE}&timestamp=${TIMESTAMP}"
SIGNATURE=$(echo -n "$QUERY" | openssl dgst -sha256 -hmac "$SECRET" | cut -d' ' -f2)

curl -s -X POST "https://fapi.binance.com/fapi/v1/leverage?${QUERY}&signature=${SIGNATURE}" \
  -H "X-MBX-APIKEY: ${API_KEY}" | jq '.'

📈 Spot Trading

Buy (Market)

SYMBOL="ETHUSDT"
QUANTITY="0.1"

TIMESTAMP=$(date +%s%3N)
QUERY="symbol=${SYMBOL}&side=BUY&type=MARKET&quantity=${QUANTITY}&timestamp=${TIMESTAMP}"
SIGNATURE=$(echo -n "$QUERY" | openssl dgst -sha256 -hmac "$SECRET" | cut -d' ' -f2)

curl -s -X POST "https://api.binance.com/api/v3/order?${QUERY}&signature=${SIGNATURE}" \
  -H "X-MBX-APIKEY: ${API_KEY}" | jq '.'

Sell (Market)

SYMBOL="ETHUSDT"
QUANTITY="0.1"

TIMESTAMP=$(date +%s%3N)
QUERY="symbol=${SYMBOL}&side=SELL&type=MARKET&quantity=${QUANTITY}&timestamp=${TIMESTAMP}"
SIGNATURE=$(echo -n "$QUERY" | openssl dgst -sha256 -hmac "$SECRET" | cut -d' ' -f2)

curl -s -X POST "https://api.binance.com/api/v3/order?${QUERY}&signature=${SIGNATURE}" \
  -H "X-MBX-APIKEY: ${API_KEY}" | jq '.'

🔧 Utilities

View Open Orders

TIMESTAMP=$(date +%s%3N)
QUERY="timestamp=${TIMESTAMP}"
SIGNATURE=$(echo -n "$QUERY" | openssl dgst -sha256 -hmac "$SECRET" | cut -d' ' -f2)

# Futures
curl -s "https://fapi.binance.com/fapi/v1/openOrders?${QUERY}&signature=${SIGNATURE}" \
  -H "X-MBX-APIKEY: ${API_KEY}" | jq '.'

Cancel Order

SYMBOL="BTCUSDT"
ORDER_ID="123456789"

TIMESTAMP=$(date +%s%3N)
QUERY="symbol=${SYMBOL}&orderId=${ORDER_ID}&timestamp=${TIMESTAMP}"
SIGNATURE=$(echo -n "$QUERY" | openssl dgst -sha256 -hmac "$SECRET" | cut -d' ' -f2)

curl -s -X DELETE "https://fapi.binance.com/fapi/v1/order?${QUERY}&signature=${SIGNATURE}" \
  -H "X-MBX-APIKEY: ${API_KEY}" | jq '.'

View Trade History

SYMBOL="BTCUSDT"
TIMESTAMP=$(date +%s%3N)
QUERY="symbol=${SYMBOL}&timestamp=${TIMESTAMP}"
SIGNATURE=$(echo -n "$QUERY" | openssl dgst -sha256 -hmac "$SECRET" | cut -d' ' -f2)

curl -s "https://fapi.binance.com/fapi/v1/userTrades?${QUERY}&signature=${SIGNATURE}" \
  -H "X-MBX-APIKEY: ${API_KEY}" | jq '.[-10:]'

🏦 Detailed Futures Balance

TIMESTAMP=$(date +%s%3N)
QUERY="timestamp=${TIMESTAMP}"
SIGNATURE=$(echo -n "$QUERY" | openssl dgst -sha256 -hmac "$SECRET" | cut -d' ' -f2)

curl -s "https://fapi.binance.com/fapi/v2/balance?${QUERY}&signature=${SIGNATURE}" \
  -H "X-MBX-APIKEY: ${API_KEY}" | jq '[.[] | select(.balance != "0")]'

📋 Popular Pairs

Pair Description
BTCUSDT Bitcoin
ETHUSDT Ethereum
BNBUSDT BNB
SOLUSDT Solana
XRPUSDT XRP
DOGEUSDT Dogecoin
ADAUSDT Cardano
AVAXUSDT Avalanche

⚠️ Safety Rules

  1. ALWAYS verify position before closing
  2. ALWAYS set Stop Loss on leveraged trades
  3. NEVER use leverage higher than 10x without experience
  4. VERIFY pair and quantity before executing
  5. CONFIRM with user before executing large orders

🔗 Links


Skill created by Total Easy Software - Clayton Martins

Usage Guidance
This skill appears to implement Binance trading functionality, but packaging and metadata are inconsistent — the skill requires sensitive Binance API keys (file or env vars) even though the registry metadata lists none, and it sets always:true (force-enabled) without justification. Before installing: 1) Do not use your main/live API keys — create a restricted test key with minimal permissions (or enable only read/balance access) and IP restrictions if possible. 2) Verify the skill source/author and prefer skills with a homepage or trusted publisher. 3) Inspect the full code (binance_cli.py) yourself; look for any unexpected network endpoints. 4) Fix variable inconsistencies (SKILL.md examples vs code use BINANCE_API_KEY/BINANCE_SECRET) and ensure required binaries are declared (python3, openssl, curl, jq). 5) Reject or request removal of always:true unless you understand and accept global inclusion; at minimum, require user opt-in. 6) Test in a sandbox account before using with real funds. If you are not comfortable auditing the code, avoid installing.
Capability Analysis
Type: OpenClaw Skill Name: binance-pro-hybrid Version: 1.0.0 The skill provides a legitimate integration with the Binance API for spot and futures trading, allowing users to manage portfolios and execute trades. It handles API credentials via environment variables or a local JSON file (~/.openclaw/credentials/binance.json) as documented. All network requests in both the Python CLI (binance_cli.py) and the markdown examples (SKILL.md) are directed to official Binance endpoints (api.binance.com and fapi.binance.com), with no evidence of data exfiltration, unauthorized execution, or malicious prompt injection.
Capability Assessment
Purpose & Capability
Name/description match the included code and SKILL.md (Binance trading). However the registry metadata claims no required env vars or primary credential even though the SKILL.md and binance_cli.py both require Binance API keys (file ~/.openclaw/credentials/binance.json or env vars). Also the skill bundles a Python CLI but does not declare Python as a required runtime; these mismatches suggest sloppy packaging or incomplete metadata.
Instruction Scope
SKILL.md and the CLI instruct the agent/user to read credentials from a home path or environment and to issue trade orders (spot and futures). That's consistent with the advertised purpose, but the examples use different env var names ($API_KEY/$SECRET) than the Quick Start (BINANCE_API_KEY/BINANCE_SECRET) and some examples call openssl for HMAC signing while openssl is not listed in required binaries. The instructions perform high-privilege actions (placing/canceling orders) — expected for a trading skill, but the inconsistencies increase the chance of misconfiguration or accidental misuse.
Install Mechanism
There is no install spec (instruction-only), so nothing is downloaded or executed by an installer — low install risk. However the skill includes a Python CLI file (binance_cli.py) but does not declare Python as a required binary, which is an omission that can cause runtime surprises.
Credentials
The skill legitimately needs Binance API keys to operate, which is proportionate to its purpose. But the registry metadata did not declare required env vars or a primary credential while SKILL.md and the code expect sensitive keys; that mismatch reduces transparency. Also the skill asks users to store private keys in a local file or env vars without guidance on least privilege (e.g., read-only vs trading) or IP restrictions.
Persistence & Privilege
The skill metadata sets always: true, meaning it will be force-included in every agent run. There is no documented justification for global, always-on inclusion. Combined with the skill's access to trading keys and ability to place orders, always:true materially increases the blast radius if the skill or agent is compromised.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install binance-pro-hybrid
  3. After installation, invoke the skill by name or use /binance-pro-hybrid
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Hybrid Labs edition - Binance trading automation
Metadata
Slug binance-pro-hybrid
Version 1.0.0
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 1
Frequently Asked Questions

What is Binance Pro (Hybrid Labs)?

Complete Binance integration - world's largest crypto exchange. Trade spot, futures with up to 125x leverage, staking, and portfolio management. Use to check... It is an AI Agent Skill for Claude Code / OpenClaw, with 85 downloads so far.

How do I install Binance Pro (Hybrid Labs)?

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

Is Binance Pro (Hybrid Labs) free?

Yes, Binance Pro (Hybrid Labs) is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Binance Pro (Hybrid Labs) support?

Binance Pro (Hybrid Labs) is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Binance Pro (Hybrid Labs)?

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

💬 Comments