← Back to Skills Marketplace
patches429

Trade Executor

by Parker · GitHub ↗ · v0.1.0 · MIT-0
cross-platform ⚠ suspicious
446
Downloads
0
Stars
3
Active Installs
1
Versions
Install in OpenClaw
/install trade-executor
Description
Execute cryptocurrency trades on exchanges (Binance, OKX) with risk controls, user confirmation, and audit logging.
Usage Guidance
Do not install or grant API keys until the owner clarifies the credential requirements and behavior. Specific actions to consider before proceeding: - Ask the publisher to update metadata to list OKX env vars (OKX_API_KEY, OKX_API_SECRET, OKX_PASSPHRASE) if OKX support is intended, or remove OKX docs if not. - Only provide exchange API keys with minimal permissions (enable trading, disable withdrawals), and ideally restrict by IP or use testnet keys first. - Confirm who/what provides the gateway that enforces cross-session limits and audit logging (openclaw.json and gateway behavior), and verify those controls exist in your environment. - Verify the skill cannot bypass the explicit user confirmation step on your platform (test with a dry-run or very small orders in a sandbox environment). - If you need higher assurance, request the skill source (code or full implementation) for review or prefer a well-audited plugin from a known publisher. If you rely on OKX functionality and the skill's metadata is not corrected, treat the skill as incomplete/untrusted because it may attempt to access undeclared secrets at runtime.
Capability Analysis
Type: OpenClaw Skill Name: trade-executor Version: 0.1.0 The trade-executor skill is a well-structured tool for executing cryptocurrency trades on Binance and OKX with extensive built-in risk controls. It enforces mandatory user confirmation, trading pair whitelists (BTC/USDT, ETH/USDT, SOL/USDT), and strict transaction limits (e.g., <= 1,000 USDT per trade). The implementation files (impl/binance.md and impl/okx.md) provide legitimate API interaction logic using standard environment variables for authentication, and the skill explicitly denies file writing and shell execution permissions.
Capability Assessment
Purpose & Capability
The skill advertises support for Binance and OKX. The metadata/requirements only declare BINANCE_API_KEY and BINANCE_API_SECRET as required env vars (primaryEnv = BINANCE_API_KEY). However impl/okx.md describes OKX-specific credentials (OKX_API_KEY, OKX_API_SECRET, OKX_PASSPHRASE). This mismatch means the skill's declared needs do not fully match its claimed capabilities.
Instruction Scope
SKILL.md and impl files instruct calling official exchange APIs (api.binance.com, api.okx.com), performing HMAC signing, and requiring user confirmation and risk checks — these are appropriate. However the instructions reference openclaw.json allowedPairs and a gateway that tracks daily counts/losses across sessions without declaring access to those config or state paths. Also impl/okx.md references environment variables not listed in the skill metadata, which indicates the runtime agent may access env vars beyond those declared.
Install Mechanism
This is an instruction-only skill with no install spec and no code files to write to disk, which minimizes install-time risk.
Credentials
Requiring Binance API key/secret is proportionate for Binance trading. But because the skill also documents OKX integration that requires additional secrets, the environment requirements are incomplete/ambiguous. The skill may expect or attempt to read OKX credentials at runtime even though they aren't declared. The skill requests API keys (sensitive) and therefore the exact set of credentials should be clearly documented and limited to trade-only keys; that clarity is absent.
Persistence & Privilege
always:false and no install behavior modifying other skills or system-wide config. The skill states it will not write files and relies on a gateway for audit logging, which is consistent with being instruction-only.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install trade-executor
  3. After installation, invoke the skill by name or use /trade-executor
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v0.1.0
trade-executor v0.1.0 - Initial release of trade-executor for executing cryptocurrency trades on Binance and OKX. - Implements complete risk controls, including whitelist pairs, per-trade and daily limits, stop-loss enforcement, and session-aware checks. - Requires explicit user confirmation for every order before execution. - Supports both user-initiated and pre-authorized market-monitor signals (with confidence ≥ 0.85). - Orders are only executed when all safety checks pass; detailed rejection reasons provided otherwise. - All trades are logged for audit with structured records; no persistent writes by Vega itself.
Metadata
Slug trade-executor
Version 0.1.0
License MIT-0
All-time Installs 3
Active Installs 3
Total Versions 1
Frequently Asked Questions

What is Trade Executor?

Execute cryptocurrency trades on exchanges (Binance, OKX) with risk controls, user confirmation, and audit logging. It is an AI Agent Skill for Claude Code / OpenClaw, with 446 downloads so far.

How do I install Trade Executor?

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

Is Trade Executor free?

Yes, Trade Executor is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Trade Executor support?

Trade Executor is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Trade Executor?

It is built and maintained by Parker (@patches429); the current version is v0.1.0.

💬 Comments