weex-trader-skill

Automate WEEX spot and futures REST tasks from natural-language requests.

4|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/drgnchan/weex-trader-skill --skill weex-trader-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: weex-trader-skill
Source: https://github.com/drgnchan/weex-trader-skill/tree/main
Command: npx skills add https://github.com/drgnchan/weex-trader-skill --skill weex-trader-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires requests, beautifulsoup4, pyyaml, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill removes the need to manually look up and wire up WEEX REST endpoints by letting you execute common market-data queries and trading actions through plain-language requests.

Core Features & Use Cases

  • Unified natural-language trading workflow: Use intent (e.g., ticker fetch, order placement, order cancellation) that the agent converts into structured fields and then routes to deterministic REST calls for execution.
  • Market + private account operations: Retrieve public market data (tickers, depth, klines, trades, funding) and, when credentials are provided, query balances/positions and manage orders.
  • Safety guardrails for mutating requests: Requires explicit live confirmation (via the script’s confirm-live flag) before placing/canceling orders.

Quick Start

Use $weex-trader-skill to get the latest BTCUSDT spot ticker and explain the result.

Frequently Asked Questions about weex-trader-skill

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate WEEX futures and spot trading using natural language?

Executing or canceling WEEX orders requires explicit live confirmation via the script's confirm-live flag safety guardrail, ensuring deliberate execution before any mutating request is processed.

Can I fetch WEEX market data like tickers, klines, and order book depth without authentication?

Querying private WEEX account operations like balances and positions requires environment-based credentials to execute authenticated REST calls with proper signing for private endpoints.

What is the best way to manage WEEX API credentials for private endpoints?

Canceling a WEEX futures order requires providing the specific symbol and order identifier, after which the script routes the cancellation intent through a signed REST call following explicit live confirmation.

Do I need Python dependencies to execute WEEX API automation scripts?

The WEEX natural language trading workflow retrieves public market data like tickers, klines, and order book depth, and manages private account operations including balance queries and order execution.

Why does placing a WEEX spot order require a confirmation flag?

You can retrieve WEEX klines, tickers, order book depth, trades, and funding rates for specific symbols, while private operations include querying balances and managing spot or futures orders.