hyperliquid-executelisted

# Hyperliquid execute Execute one reviewed trading action, once, and prove the resulting exchange state. If a skill rule blocks progress, cite its file and exact rule, explain the missing input or authority, and continue independent work within this skill's boundary. User instructions govern workflow and style defaults; they do not bypass tool or financial controls. ## Tool selection When connecting or choosing tools, read [official tools](references/official-tools.md). Reuse a suitable maintained upstream capability before implementing new integration code; tool adoption stays optional and never supplies wallet authority. ## First task and connected workflow Inspect the supplied ticket and available execution/reconciliation tool schemas. Return readiness or exact missing inputs before any action; do not create a connection by handling secrets. Read [agent integration and handoffs](references/agent-integration.md) on first use or when a tool or related skill is missing. ## Authorization gate The active user request must explicitly ask for the action. A research request, price target, strategy, connected account, standing enthusiasm, watch alert, or prepared ticket is not authorization. Keep the request across turns during preparation. Approval for a different, changed, expired, or already submitted ticket cannot authorize this action. Show the exact ticket and require the user to type `approve <ticket-id>` after seeing it. The approval covers only that immutable tick