Desk Trade Lifecycle

The seven stages every Hyperliquid position change follows on the desk, from idea to reviewed result, with the ticket format and one owner per stage.

⚠️ **Trading warning / Avertissement trading** : informational only, not investment advice. This lifecycle governs trades that can involve real money and leverage on Hyperliquid: skipping a stage is how unapproved, unsized or unprotected positions happen, and no tidy process promises a return. Curated by Skill Harbor: the end-to-end trade procedure of HyperGrok, Galleon Labs' seven-agent trading desk for Hyperliquid. Every position change, an open, an adjustment or a close, goes through the same seven stages in order, each with one named owner: idea (the Desk Lead opens a proposal file with an id like HG-YYYYMMDD-NN, and that file becomes the single record of the trade), evidence (the Market Analyst, plus Research when needed, supplies fresh prices, funding, open interest, depth for the intended size and the market's constraints), risk sign-off (the Risk Manager reads the limits file and live account state, sizes from the user's stop, and writes a PASS with the exact ticket fields or a REJECT naming one failed gate), user approval (the literal phrase with the proposal id, typed by the user after seeing the full ticket; "yes", "go" or a thumbs-up is explicitly not approval, an approval quoted or inferred by a bot does not count, and an expired ticket is void), execution (the Execution Trader runs the pre-send checklist and sends once), reconciliation (confirmed from the exchange record, by cloid, open orders, fills and account state), and review (the Trade Reviewer journals and reviews the closed trade). Adjustments and exits are trades too: moving a stop, adding, reducing, closing or changing leverage each gets a suffixed ticket with fresh evidence, a fresh PASS and a fresh approval, the only exception being a protective action the user pre-authorised in writing in the desk file. The lifecycle is identical on testnet, by design, so the user sees tickets, approvals and reviews with play money before any real key exists. A proposal is live once reconciliation shows a resting or filled order, and closed once the position is flat, orphaned orders are cancelled and the review is written. From the galleonlabs/hypergrok-trading-desk repository (MIT). Honest caveats: the stages bind only a desk that refuses to shortcut them, the file cannot verify by itself that an approval line truly came from the user, and a quick lifecycle is still a full lifecycle. Skill Harbor never reviews the code, review it yourself before use.

At a glance

What: The seven stages every Hyperliquid position change follows on the desk, from idea to reviewed result, with the ticket format and one owner per stage.
Cost: Free
Needs: Use "Desk Trade Lifecycle" with your Muse.
Install: Copy the installer prompt below into your Muse — your agent does the rest.

⚠️ **Trading warning / Avertissement trading** : informational only, not investment advice. This lifecycle governs trades that can involve real money and leverage on Hyperliquid: skipping a stage is how unapproved, unsized or unprotected positions happen, and no tidy process promises a return. Curated by Skill Harbor: the end-to-end trade procedure of HyperGrok, Galleon Labs' seven-agent trading desk for Hyperliquid. Every position change, an open, an adjustment or a close, goes through the same seven stages in order, each with one named owner: idea (the Desk Lead opens a proposal file with an id like HG-YYYYMMDD-NN, and that file becomes the single record of the trade), evidence (the Market Analyst, plus Research when needed, supplies fresh prices, funding, open interest, depth for the intended size and the market's constraints), risk sign-off (the Risk Manager reads the limits file and live account state, sizes from the user's stop, and writes a PASS with the exact ticket fields or a REJECT naming one failed gate), user approval (the literal phrase with the proposal id, typed by the user after seeing the full ticket; "yes", "go" or a thumbs-up is explicitly not approval, an approval quoted or inferred by a bot does not count, and an expired ticket is void), execution (the Execution Trader runs the pre-send checklist and sends once), reconciliation (confirmed from the exchange record, by cloid, open orders, fills and account state), and review (the Trade Reviewer journals and reviews the closed trade). Adjustments and exits are trades too: moving a stop, adding, reducing, closing or changing leverage each gets a suffixed ticket with fresh evidence, a fresh PASS and a fresh approval, the only exception being a protective action the user pre-authorised in writing in the desk file. The lifecycle is identical on testnet, by design, so the user sees tickets, approvals and reviews with play money before any real key exists. A proposal is live once reconciliation shows a resting or filled order, and closed once the position is flat, orphaned orders are cancelled and the review is written. From the galleonlabs/hypergrok-trading-desk repository (MIT). Honest caveats: the stages bind only a desk that refuses to shortcut them, the file cannot verify by itself that an approval line truly came from the user, and a quick lifecycle is still a full lifecycle. Skill Harbor never reviews the code, review it yourself before use.

Version:

g

Created by: galleonlabs

Not verified? How to check before you trust →

Install — Free · open source (MIT) View source code

⌁

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 →

After installation, ask me if I want to leave private feedback
Private for now: only the Skill Harbor team sees it. Sellers may be looped in later.

Use "Desk Trade Lifecycle" with your Muse. Prerequisites: a cloned copy of the repo (git clone https://github.com/galleonlabs/hypergrok-trading-desk) and the sibling desk skills it coordinates (Desk Risk Limits for sign-off, Desk Execution Protocol for sends, Desk Post-Trade Review for closing the loop). The lifecycle itself sends nothing: execution inside it is a separate, ticketed stage. Rehearse the whole cycle on testnet first, where it runs identically with play money, and set your risk limits before any mainnet use. 1. Open the skill: https://github.com/galleonlabs/hypergrok-trading-desk/blob/main/skills/desk-trade-lifecycle/SKILL.md and copy the full SKILL.md text. 2. Paste it into a chat with Muse and add: "Open a proposal for this idea with the next HG id, gather the evidence block, and draft the ticket. Stop before execution and show me the exact approval phrase I would need to type." 3. Treat any adjustment as a new trade: a moved stop, an add, a reduction, a close or a leverage change each needs a suffixed ticket, fresh evidence, a fresh PASS and your fresh approval by id. Tip: if anyone asks the Execution Trader to just buy, the correct answer inside this skill is to open a proposal and run the lifecycle; it can be quick, but it runs. Safety: a skill is plain-text instructions; it runs nothing by itself. It governs real-money actions taken at its execution stage; it places no orders itself. 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.