RapidX Trading

Use this skill after ltp-rapidx-config has confirmed the runtime path as MCP_READY or CLI_ONLY_READY. Prefer MCP tools only when the agent host is MCP_READY. Use direct CLI commands only when the confirmed path is CLI_ONLY_READY.

References

• Read references/capability-overview.md when selecting a CLI command, MCP tool, capability id, or RapidX endpoint mapping.
• Read references/best-practices.md when planning a full workflow across skills, CLI, MCP, preview, automation, and readback.

Non-Negotiable Rules

• Do not fake query or trading results. Every claim must come from an actual MCP tool or rapidx ... --json response, and final summaries must include toolOrCommandEvidence or equivalent observed evidence.
• Do not use shell bridge scripts, temporary JavaScript scripts, directory-changing shell chains, or chained shell invocations.
• Treat all trade-write tools as real production actions.
• Never submit a write without preview evidence and explicit user consent for that specific write, unless the user has explicitly enabled RapidX automation mode for the current scope in chat.
• Use confirmation.submitToken from the preview response as the submit continueConsentId.
• Keep business parameters unchanged between preview and submit. If symbol, side, positionSide, quantity, price, order id, leverage, or mode changes, create a new preview.
• If a write times out or the result is uncertain, query state before retrying.
• Never echo secrets.