← Search

Desk Execution Protocol
Trading
⚙ Needs: ⚠️ REAL MONEY WARNING: this skill is the desk's…

Desk Execution Protocol

The Execution Trader's discipline for turning an approved ticket into exactly one Hyperliquid action: pre-send checklist, single send, and full reconciliation.

⚠️ **Trading warning / Avertissement trading** : informational only, not investment advice. This is the one desk skill that ends in a signed request to the exchange: on mainnet every send is real money, leveraged positions can be liquidated, and a mishandled resend can double a position. No procedure here promises a return. Curated by Skill Harbor: the execution discipline of HyperGrok, Galleon Labs' seven-agent trading desk for Hyperliquid. The API mechanics live in the sibling orders and positions skills; this skill is the procedure around them. It starts from an approved proposal file carrying a Risk Manager PASS and exact ticket fields, plus the user's approval by id inside the ticket's expiry, and runs an eight-point pre-send checklist before anything is sent: ticket integrity (any economic change means a new ticket id, a new PASS and a new approval), network and account matching the ticket, the API wallet verified as an approved agent for that account, a fresh price still inside the slippage tolerance, correct rounding and minimum notional, a fresh cloid with the signed nonce and an expiresAfter deadline recorded, one action per send with entry, stop and take-profit grouped, and capacity re-read with no unreconciled send outstanding. The send itself happens exactly once, with a finite timeout and the raw response captured. A timeout or a lost response is an unknown result, treated as possibly executed: never resend, reconcile by cloid through order status, open orders, fills and account state, and wait out the expiry deadline before any replacement on a fresh ticket. Cancels, modifies, leverage changes and closes are each their own ticket, and any action type the desk has never performed is rehearsed on testnet first. From the galleonlabs/hypergrok-trading-desk repository (MIT). Honest caveats: the discipline binds only a desk that actually routes every send through it, nothing in the file can stop a human or an agent from bypassing the checklist, and the desk never withdraws, deposits, bridges or transfers funds. Skill Harbor never reviews the code, review it yourself before use.
At a glance
What
The Execution Trader's discipline for turning an approved ticket into exactly one Hyperliquid action: pre-send checklist, single send, and full reconciliation.
Cost
Free
Needs
⚠️ REAL MONEY WARNING: this skill is the desk's send path. Its procedure ends in signed requests to Hyperliquid's exchange endpoint, and on mainnet that is real money with leverage and liquidation risk from the first fill. Do not use it on mainnet until you have rehearsed the full flow on testnet first, configured your risk limits in advance (see Desk Risk Limits), and adopted the ticket rule: no send without a Risk Manager PASS and your explicit approval by id for that exact ticket. The API wallet key belongs in the HYPERLIQUID_PRIVATE_KEY environment variable or the secure secret store only, with HYPERLIQUID_NETWORK and HYPERLIQUID_ACCOUNT_ADDRESS set deliberately. Never paste a private key, a seed phrase or an API secret into a chat, including this one, and never send from a main wallet key.
Install
Copy the installer prompt below into your Muse — your agent does the rest.

Version:

⌁

Install

Copy the install package below, then paste it into Muse
Wanna be extra careful?

The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?

How to check a build before installing →

⚠️ REAL MONEY WARNING: this skill is the desk's send path. Its procedure ends in signed requests to Hyperliquid's exchange endpoint, and on mainnet that is real money with leverage and liquidation risk from the first fill. Do not use it on mainnet until you have rehearsed the full flow on testnet first, configured your risk limits in advance (see Desk Risk Limits), and adopted the ticket rule: no send without a Risk Manager PASS and your explicit approval by id for that exact ticket. The API wallet key belongs in the HYPERLIQUID_PRIVATE_KEY environment variable or the secure secret store only, with HYPERLIQUID_NETWORK and HYPERLIQUID_ACCOUNT_ADDRESS set deliberately. Never paste a private key, a seed phrase or an API secret into a chat, including this one, and never send from a main wallet key. Prerequisites: a cloned copy of the repo (git clone https://github.com/galleonlabs/hypergrok-trading-desk), the desk computer configured per Hyperliquid Setup, the sibling Hyperliquid Orders and Hyperliquid Positions skills for the API mechanics, and an approved proposal file to execute from. Start on testnet. 1. Open the skill: https://github.com/galleonlabs/hypergrok-trading-desk/blob/main/skills/desk-execution-protocol/SKILL.md and copy the full SKILL.md text. 2. Paste it into a chat with Muse and add: "On testnet only, run the pre-send checklist against this approved ticket item by item and show me the result of each check. Do not send anything in this chat." 3. Before any real send, confirm the cloid, the signed nonce and the expiresAfter deadline are written in the proposal file, and that you know the unknown-result procedure by heart: never resend, reconcile by cloid, wait out the deadline. Safety: a skill is plain-text instructions; it runs nothing by itself, but the procedure it documents signs real exchange requests. Informational only, not investment advice.

?

Questions

How do I install a build?

Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.

Where does my money go?

Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.

What does the ✓ next to a creator’s name mean?

It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.