dprolabs/dpro-ccxt/ccxt-trade

Use this skill only when user explicitly asks to trade.

Rules:

1. Validate input before execution.
2. Use exchange field directly.
3. Respect account risk guards (set during account_add_api).
4. For side effects, review preview details before execution.
5. create_order, cancel_order, and set_leverage require options.confirm=true to proceed.
6. When credentials are missing, use ccxt-admin.account_add_api exchange=<X> payload={alias:<A>,apiKey:<K>,secret:<S>} runtimeContext={password:<MASTER_PASSWORD>} onboarding.
7. Do not suggest environment-variable credential setup.

Confirmation Requirement

create_order, cancel_order, and set_leverage require explicit confirmation:

• Set options.confirm=true in the request, or
• The call returns CONFIRMATION_REQUIRED with a details.preview object.

Always confirm with the user before setting confirm=true.

details.preview is a preflight preview from request fields. Exchange precision and market limits are enforced during execution.

Prompting for API Keys

When the action fails with NO_API_ACCOUNT:

1. Use ../references/exchange-onboarding.md for exchange-specific API page and requirements.
2. Ask user to create API key/secret in exchange API management.
3. Remind user trading permissions must be enabled for write actions.
4. Guide user to add credentials via account_add_api first.
5. Remind user that account_add_api stores credentials locally before live trade actions are retried.

If user already has credentials:

• do not suggest onboarding again
• retry the requested trade flow directly

When response code is ACCOUNT_LOCKED:

• ask for master password only
• do not ask for API key/secret again
• retry the same trade command with password context

AUTH_ERROR handling

When request fails with AUTH_ERROR:

1. Ask user to verify key validity and trade permission scope.
2. If key is stale/invalid, guide key rotation and re-run account_add_api.
3. If credentials already valid, retry the trade request (no repeated onboarding).