ccxt-account

name	ccxt-account
description	Query authenticated read-only account state through CCXT including balances, orders, trades, and positions. Do not place or cancel orders.

Use this skill for private read-only queries.

Rules:

1. Never call create_order, cancel_order, or set_leverage.
2. This skill only covers: fetch_balance, fetch_open_orders, fetch_order, fetch_orders, fetch_my_trades, fetch_positions.
3. Account management actions (account_add_api, account_ls, account_remove, account_set_default) belong to ccxt-admin only.
4. Use exchange field directly.
5. Return JSON output first, then concise summary.
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.

Prompting for API Keys

When the action fails with NO_API_ACCOUNT:

1. Look up onboarding links and requirements from ../references/exchange-onboarding.md.
2. Ask user to open the exchange API management page and create API key/secret.
3. For account reads, recommend read-only/account-query permissions only.
4. Guide user to add credentials via ccxt-admin.account_add_api first.
5. Remind user that account_add_api writes credentials into the local encrypted account store for later account reads.

If user already has credentials:

• do not suggest onboarding again
• retry the requested account command directly

When response code is ACCOUNT_LOCKED:

• ask for master password only
• do not ask for API key/secret again
• retry the same account command with runtimeContext.password

AUTH_ERROR handling

When request fails with AUTH_ERROR:

1. Ask user to verify existing key/secret values and read permission scope.
2. If credentials are invalid, guide user to rotate/recreate key and re-run account_add_api.
3. If credentials are already valid, retry the requested action.