← Search

Hyperliquid Orders
Trading
⚙ Needs: ⚠️ REAL MONEY WARNING: this skill places, cancels…

Hyperliquid Orders

Place, cancel, and modify Hyperliquid orders correctly: rounding rules, client order ids, trigger orders, grouped take-profit and stop-loss, and every response status read properly.

⚠️ **Trading warning / Avertissement trading** : informational only, not investment advice. This skill is a WRITE path: its snippets end in signed requests that place real orders, and on mainnet that is real money from the first fill, with losses possible on every position. Curated by Skill Harbor: the order-mechanics skill of HyperGrok, Galleon Labs' seven-agent trading desk for Hyperliquid, written in Python (official SDK) and TypeScript. It teaches the concepts traders get wrong: orders address an asset index, not a symbol; prices round to at most five significant figures with a decimals cap, sizes always round down; there is no market order, only an IOC limit bounded by a slippage tolerance; a client order id (cloid) on every order is what lets you reconcile when a response is lost; trigger orders fire on mark price and need a worst-acceptable price beyond the trigger (desk defaults: a 5% bound for stop-losses, 1% for take-profits); and entries can carry grouped take-profit and stop-loss children that live and die with the entry. Full worked code covers resting limits, market-style entries, grouped entries, stops on existing positions, cancels, and modifies (a stop can never be modified: place the new one, confirm it rests, then cancel the old, so the position is never naked). A complete error-string table maps exchange rejections to causes and fixes. The desk discipline around it is part of the skill: only the Execution Trader role sends, only on a ticket with a risk PASS and the user's approval by id, and the default network is testnet. From the galleonlabs/hypergrok-trading-desk repository (MIT). Honest caveats: none of that discipline is enforced by the code itself; it binds only a desk that actually routes every send through it, and a signed request sent twice after a timeout doubles a position, which is why the reconcile-by-cloid rule exists. Skill Harbor never reviews the code, review it yourself before use.
At a glance
What
Place, cancel, and modify Hyperliquid orders correctly: rounding rules, client order ids, trigger orders, grouped take-profit and stop-loss, and every response status read properly.
Cost
Free
Needs
⚠️ REAL MONEY WARNING: this skill places, cancels, and modifies real orders on Hyperliquid. On mainnet every fill is real money and can lose. Do not use it on mainnet until you have rehearsed the full flow on testnet, set written risk limits first (see Desk Risk Limits), and adopted the ticket rule: no send without a risk PASS and your explicit approval by id, and never a second send after a timeout before reconciling by cloid. The signing key belongs in the HYPERLIQUID_PRIVATE_KEY environment variable or a local key file on your own machine only, with HYPERLIQUID_ACCOUNT_ADDRESS naming the main account (never the API wallet's own address). Never paste a private key or seed phrase into a chat, including this one.
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 places, cancels, and modifies real orders on Hyperliquid. On mainnet every fill is real money and can lose. Do not use it on mainnet until you have rehearsed the full flow on testnet, set written risk limits first (see Desk Risk Limits), and adopted the ticket rule: no send without a risk PASS and your explicit approval by id, and never a second send after a timeout before reconciling by cloid. The signing key belongs in the HYPERLIQUID_PRIVATE_KEY environment variable or a local key file on your own machine only, with HYPERLIQUID_ACCOUNT_ADDRESS naming the main account (never the API wallet's own address). Never paste a private key or seed phrase into a chat, including this one. Prerequisites: Python with the official hyperliquid-python-sdk (or Node 22.12+ for the TypeScript client), a cloned copy of the repo (git clone https://github.com/galleonlabs/hypergrok-trading-desk), a funded testnet account to rehearse on, and your network chosen deliberately via HYPERLIQUID_NETWORK (testnet is the desk default). 1. Open the skill: https://github.com/galleonlabs/hypergrok-trading-desk/blob/main/skills/hyperliquid-orders/SKILL.md and copy the full SKILL.md text. 2. Paste it into a chat with Muse and add: "On testnet only, walk me through a resting limit order with a fresh cloid, then show me how you would read the response status and reconcile it. Do not send anything to mainnet." 3. Before any real send, confirm the ticket: size rounded down, price inside the approved bound, reduce-only set correctly on exits, and the cloid written down before signing. Safety: a skill is plain-text instructions; it runs nothing by itself, but the code 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.