agentleFS
TermiX-officialTermiX-official/cryptoclaw/skills/binance-spot/SKILL.md

binance-spot

Skill100 starsChanged 9 months agoMITView on GitHub

Binance official spot trading skill — place orders, manage accounts, and access real-time market data via Binance Spot API. Sourced from github.com/binance/binance-skills-hub.

  • Reads credentials

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use vault_store_credential tool with provider "binance", apiKey, and apiSecret.

    line 18
  2. Distinctive:

    Never execute mainnet orders without explicit user confirmation

    line 194
  3. Distinctive:

    Always show order details before submission

    line 195

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Binance Spot Trading

Official Binance skill for CEX spot trading. Supports 60+ endpoints for market data, order management, and account operations.

Source: binance/binance-skills-hub

Configuration

Store credentials via SecureVault (recommended) or environment variables:

Option 1 — SecureVault (TEE-protected when available): Use vault_store_credential tool with provider "binance", apiKey, and apiSecret.

Option 2 — Environment variables:

BINANCE_API_KEY=<your_api_key>
BINANCE_API_SECRET=<your_api_secret>
BINANCE_TESTNET=false  # set true for testnet

How to Call Authenticated Endpoints

For all endpoints that require authentication, use the signed_api_request tool:

signed_api_request({
  provider: "binance",
  method: "POST",
  path: "/api/v3/order",
  params: '{"symbol":"BTCUSDT","side":"BUY","type":"MARKET","quantity":"0.001"}'
})

The vault handles HMAC-SHA256 signing, timestamp injection, and API key headers automatically. You NEVER need to handle API keys or secrets directly.

For public endpoints (no auth required), you may use direct HTTP requests.

Always require explicit user confirmation before executing mainnet transactions.

Base URLs

  • Mainnet: https://api.binance.com
  • Testnet: https://testnet.binance.vision

Market Data (no auth required)

Exchange Info

GET /api/v3/exchangeInfo
GET /api/v3/exchangeInfo?symbol=BTCUSDT

Price Ticker

GET /api/v3/ticker/price?symbol=BTCUSDT
GET /api/v3/ticker/24hr?symbol=BTCUSDT
GET /api/v3/ticker/bookTicker?symbol=BTCUSDT

Order Book

GET /api/v3/depth?symbol=BTCUSDT&limit=20

Klines / Candlesticks

GET /api/v3/klines?symbol=BTCUSDT&interval=1h&limit=100

Intervals: 1s, 1m, 3m, 5m, 15m, 30m, 1h, 2h, 4h, 6h, 8h, 12h, 1d, 3d, 1w, 1M

Recent Trades

GET /api/v3/trades?symbol=BTCUSDT&limit=50
GET /api/v3/aggTrades?symbol=BTCUSDT&limit=50

Average Price

GET /api/v3/avgPrice?symbol=BTCUSDT

Trading (auth required)

Place Order

POST /api/v3/order
  symbol=BTCUSDT
  side=BUY|SELL
  type=LIMIT|MARKET|STOP_LOSS_LIMIT|TAKE_PROFIT_LIMIT
  quantity=0.001
  price=60000        # required for LIMIT
  timeInForce=GTC    # GTC | IOC | FOK

Test Order (no execution)

POST /api/v3/order/test

Cancel Order

DELETE /api/v3/order?symbol=BTCUSDT&orderId=12345
DELETE /api/v3/openOrders?symbol=BTCUSDT   # cancel all

Query Order

GET /api/v3/order?symbol=BTCUSDT&orderId=12345
GET /api/v3/openOrders?symbol=BTCUSDT
GET /api/v3/allOrders?symbol=BTCUSDT

OCO Orders

POST /api/v3/order/oco
POST /api/v3/orderList/oco
DELETE /api/v3/orderList?orderListId=12345
GET /api/v3/orderList?orderListId=12345
GET /api/v3/allOrderList
GET /api/v3/openOrderList

Account (auth required)

Account Info

GET /api/v3/account

Returns balances, permissions, commission rates.

Commission Rates

GET /api/v3/account/commission?symbol=BTCUSDT

Trade History

GET /api/v3/myTrades?symbol=BTCUSDT

Allocations

GET /api/v3/myAllocations?symbol=BTCUSDT

Usage Examples

User: What's the current BTC price?
→ GET /api/v3/ticker/price?symbol=BTCUSDT (public, no auth needed)

User: Show my USDT balance
→ signed_api_request(provider:"binance", method:"GET", path:"/api/v3/account")
→ Filter response for USDT

User: Buy 0.001 BTC at market price
→ Confirm with user first
→ signed_api_request(provider:"binance", method:"POST", path:"/api/v3/order",
     params:'{"symbol":"BTCUSDT","side":"BUY","type":"MARKET","quantity":"0.001"}')

User: Place a limit sell for 0.01 ETH at $3500
→ Confirm with user first
→ signed_api_request(provider:"binance", method:"POST", path:"/api/v3/order",
     params:'{"symbol":"ETHUSDT","side":"SELL","type":"LIMIT","quantity":"0.01","price":"3500","timeInForce":"GTC"}')

Safety Rules

  • Never execute mainnet orders without explicit user confirmation
  • Always show order details before submission
  • Display masked credentials only (never full secret key)
  • Testnet recommended for testing and development

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.