Trade Executor

Execute cryptocurrency trades on exchanges (Binance, OKX) with risk controls, user confirmation, and audit logging.

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.

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.