Pack · #230 trending skills repo
Hypergrok Trading Desk
galleonlabs/hypergrok-trading-desk
Hyperliquid trading desk for AI agents: 7 roles, 17 skills and keyless market tools. Research first; execution requires your API wallet and approved tickets. Grok Bot, Claude Code, Cursor, Codex, Gemini CLI and Grok Build.
- Stars
- 402
- This week
- —
- Forks
- 95
- Open issues
- 1
- Skills inside
- 17
Get started
Install the skills
npx skills add galleonlabs/hypergrok-trading-deskInstalls into Claude Code, Codex, Cursor, OpenCode and the other agents it finds on your machine.
/plugin marketplace add galleonlabs/hypergrok-trading-deskRun inside Claude Code, then pick what to install from /plugin.
git clone --depth 1 https://github.com/galleonlabs/hypergrok-trading-desk.git /tmp/hypergrok-trading-desk
cp -r /tmp/hypergrok-trading-desk ~/.claude/skills/hypergrok-trading-deskClaude Code reads ~/.claude/skills/ (or .claude/skills/ in a project). Other agents read the same SKILL.md format from their own skills folder.
Inside this repo
17 skills
skills/desk-execution-protocoldesk-incident-responseWhat the desk does when something goes wrong on Hyperliquid - unknown send results, unexpected fills or positions, unprotected positions, stuck or orphaned orders, API outages, rate limiting, and suspected API wallet compromise. Contain first, reconcile from the exchange record, act only through appskills/desk-incident-responsedesk-monitoringHow the desk watches markets and the account between trades using Grok Bot routines and WebSocket or polling watches - the desk brief, book checks, funding and price watches, alert conditions and what a watch may and may not do. Use when the user asks for briefings, alerts, "watch X" or scheduled chskills/desk-monitoringdesk-operating-modelHow the HyperGrok trading desk works as a team of Grok Bots - roles, seats, shared workspace, evidence standard, approval model and handoff format. Use when setting up the desk, when a Bot is unsure who owns something, or when a request does not fit the normal trade lifecycle.skills/desk-operating-modeldesk-post-trade-reviewThe Trade Reviewer's procedure for journaling desk activity and reviewing trades from the exchange record - process graded separately from outcome, execution costs measured, one repeatable finding per review, plus the weekly desk review. Use after any send, when a trade closes, on the weekly routineskills/desk-post-trade-reviewdesk-risk-limitsHow the Risk Manager writes the desk's risk limits with the user, sizes every proposed trade from live account state and Hyperliquid's real constraints, checks the book, and issues a PASS or REJECT with exact ticket fields. Use for setting up or changing limits, sizing any trade, and answering "how'skills/desk-risk-limitsdesk-strategy-labHow the Strategist works with the user to turn their own trading idea into explicit rules, backtest it honestly on Hyperliquid candle and funding history, and paper-trade it on testnet through the desk lifecycle. Method only - the desk ships no strategies and makes no return claims. Use when the useskills/desk-strategy-labdesk-trade-lifecycleThe end-to-end procedure for one trade on the HyperGrok desk - from an idea to a reviewed, journaled result - with the ticket format, who owns each stage, and what "done" looks like. Use whenever the user wants to open, adjust or close a position, or whenever any Bot is about to touch the exchange wskills/desk-trade-lifecyclehypergrok-bootstrapBuild and verify a HyperGrok trading desk from the pinned public release. Use for first-run setup, repair, or a readiness check. Starts with a live zero-key Opening Bell, installs the seven role profiles and seventeen shared skills, prepares the Trading Floor, and returns an evidence receipt. Read-oskills/hypergrok-bootstraphyperliquid-accountRead a Hyperliquid account from the desk computer - positions and margin, spot balances, open orders including trigger details, fills, funding paid, ledger updates, order status by oid or cloid, historical orders, portfolio history, fee tier and rate-limit budget - with curl and Python SDK examples.skills/hyperliquid-accounthyperliquid-advancedLess common Hyperliquid actions and their rules - dead-man's switch (scheduleCancel), TWAP orders, spot orders, expiresAfter and nonces, API wallet approval from code, sub-account and vault addressing, HIP-3 dexs, and what the desk deliberately does not do (transfers, withdrawals, builder fees, stakskills/hyperliquid-advancedhyperliquid-api-referenceCompact reference for the Hyperliquid API as the desk uses it - endpoints and envelopes, desk-used /info request types and /exchange actions with their signing schemes, order and status vocabularies, asset ids, tick and lot rules, rate limits, WebSocket subscription list, error strings, and where thskills/hyperliquid-api-referencehyperliquid-market-dataRead live Hyperliquid market data from the desk computer with curl or the Python SDK - mid, mark and oracle prices, order book depth, funding (current, predicted, historical), open interest, volume, candles, perp and spot metadata, margin tiers, and how to save datasets for the strategy lab. Read-onskills/hyperliquid-market-datahyperliquid-ordersPlace, cancel and modify Hyperliquid orders correctly from the desk computer - limit and IOC (market-style) orders, take-profit and stop-loss trigger orders with grouping, client order ids, reduce-only, batch actions, price and size rounding, and how to read every response status. Write path - Execuskills/hyperliquid-ordershyperliquid-positionsManage Hyperliquid perp positions and margin from the desk computer - read positions and margin, set leverage and cross/isolated mode, add isolated margin, understand margin tiers and liquidation price, close a position with a reduce-only IOC, and clean up orphaned orders. Write actions are Executioskills/hyperliquid-positionshyperliquid-setupPrepare the desk computer to work with Hyperliquid - install the SDKs, pick testnet or mainnet, verify connectivity, and (only when the user asks) provision a trade-only API wallet through the secure secret store and verify it is approved. Use during desk setup, when moving between research, testnetskills/hyperliquid-setuphyperliquid-websocketSubscribe to live Hyperliquid data over WebSocket from the desk computer - mids, order book, trades, candles, best bid/offer, and per-account fills, order updates and events - with raw JSON, Python SDK and TypeScript examples, plus how to run a supervised watch that logs to a file and alerts. Read-oskills/hyperliquid-websocketDocumentation
README
Works in Grok Bot · Claude Code · Cursor · Codex · Gemini CLI · Grok Build
HyperGrok gives your AI agents a shared process for Hyperliquid research, risk, execution and review. It includes seven role profiles, seventeen skills and read-only Python tools. Start with public market data, then set up the desk in Grok Bot or your preferred agent tool. Trading requires your own API wallet, verified approval controls and an exact ticket you approve.
Try it now, no keys
git clone --depth 1 --branch v1.7.1 https://github.com/galleonlabs/hypergrok-trading-desk.git
cd hypergrok-trading-desk
python3 scripts/opening_bell.py --coin ETH
A live ETH snapshot from Hyperliquid's public /info endpoint: price, funding, open interest, spread and depth. It needs no wallet, account or key, and runs on Python 3's standard library.
Recorded from the command above on 25 October 2026 at 13:09 UTC. The figures are a historical snapshot; run it yourself for current data.
Start
For the seven-Bot desk with a shared Trading Floor, open Grok Bot and paste:
Set up the HyperGrok trading desk from https://github.com/galleonlabs/hypergrok-trading-desk/blob/v1.7.1/skills/hypergrok-bootstrap/SKILL.md. Follow the bootstrap skill, use https://github.com/galleonlabs/hypergrok-trading-desk/blob/v1.7.1/SETUP.md for the complete runbook, and finish with its evidence receipt.
Or add the public HyperGrok Desk Lead template, then send Start the desk. Its 1.7.1 bootstrap installs the complete seventeen-skill release. See the publication and native content checks.
The Desk Lead runs Opening Bell, installs the shared skills, prepares the team and returns a setup receipt. The desk starts in research mode. Add a testnet API wallet when you want to practise with play money; mainnet uses the same ticket process after its approval controls are verified. See the full setup runbook for each step.
Opening Bell and desk doctor for scripts
Opening Bell reports source and UTC time, mid/mark/oracle prices, 24-hour change and volume, hourly funding, open interest, spread and depth at 5/10/25 bps. It requests coarser book pages when twenty levels cannot cover a band, identifies each figure's source page and marks unreached depth as a floor. scripts/desk_doctor.py checks the release, roles, skill hashes, desk folders and public connectivity. Both use only Python's standard library.
For automation, inspect the offline --schema, then use --json. Failed reads, partial depth and doctor warnings remain explicit. Snapshots accept canonical mixed-case names and HIP-3 markets:
python3 scripts/opening_bell.py --schema
python3 scripts/opening_bell.py --coin xyz:TSLA --json
python3 scripts/desk_doctor.py --offline --json
--testnet explicitly selects testnet. A custom API origin is labelled custom. HIP-3 discovery stays read-only; execution remains opt-in under the desk's normal ticket rules.
Collect history you can check
Before a backtest, collect the exact period into a research bundle:
python3 scripts/research_dataset.py --coin ETH --interval 4h \
--start 2026-09-01T00:00:00Z --end 2026-10-01T00:00:00Z \
--with-funding --output ../hypergrok-data/eth-september --json
python3 scripts/research_dataset.py --verify ../hypergrok-data/eth-september --json
The bundle keeps requests, captured responses, observed CSV rows and a hashed manifest. Closed UTC windows, explicit missing ranges and bounded funding pagination distinguish complete, incomplete and unavailable history. Offline verification replays the saved responses; it checks consistency, not source authenticity or strategy quality. The tool needs no key and never fills a gap with synthetic data. See Research datasets for the supported intervals, market selection, exit codes and analyst handoff.
Meet the desk
You supply the ideas. Each role owns a stage and hands its evidence to the next.
| Bot | What they do for you |
|---|---|
| Desk Lead | Your main contact. Runs the floor, keeps every trade moving through the same clean process. |
| Market Analyst | Live Hyperliquid data on demand: price, depth, funding, open interest, candles. Timestamped and sourced. |
| Research Analyst | What is happening and what is scheduled: fundamentals, news, catalysts, onchain and social context. |
| Strategist | Turns your idea into explicit rules, backtests it honestly on Hyperliquid history, paper-trades it on testnet. |
| Risk Manager | Keeps your written limits, sizes every trade from your live account, watches the book, and can say no. |
| Execution Trader | The one Bot with the keys. Sends the ticket you approved, once, and reconciles it from the exchange record. |
| Trade Reviewer | Keeps the desk journal and grades every trade on process and outcome, separately. |
Six sit together on the Trading Floor group chat; the Trade Reviewer works by DM. Every trade follows the same path:
A day on the desk
"Brief me on ETH." The Market Analyst pulls mid, mark, funding, open interest, 24h volume and depth at 5/10/25 bps from the exchange, and posts a brief with sources and UTC times.
"I want to long ETH at 3,000 with a stop at 2,900." In this illustrative example, the Desk Lead opens HG-20260816-01. The Risk Manager reads the account and returns a sized ticket:
TICKET HG-20260816-01 | mainnet
market ETH-PERP side buy size 0.4827 ETH (~$1,448)
entry limit 3,000 Gtc stop sell 0.4827 @ 2,900 market (sent with the entry)
risk $51.00 = 0.5% of equity $10,200 (clearinghouseState 14:11 UTC) R = 100
sized on a stressed stop: 100 + 3.00 slippage + 2.65 fees = 105.65 per ETH
approve with: "approve HG-20260816-01"
You type approve HG-20260816-01. After the pre-send checks and native approval gate pass, the Execution Trader sends entry and stop in one grouped order, reconciles the exchange response and reports the order ids. The Trade Reviewer records costs, process and outcome.
"Can we test whether funding extremes mean-revert?" The Strategist writes the rules with you, collects and verifies the agreed history, then reports costs, funding assumptions, holdout results and the trade distribution. Missing history stays visible. Testnet paper trading follows the same ticket process.
"Watch ETH and tell me if funding flips negative." A routine on the desk computer watches the WebSocket feed and pings you when it happens.
What the desk knows
Seventeen skills, in the portable SKILL.md format, shared by all your Bots.
Bootstrap - pinned release install, Opening Bell, team construction, desk doctor and a receipt that distinguishes what happened from what still needs a manual step.
Hyperliquid - setup and API wallets, market data, account state, orders (limit, IOC, take-profit and stop-loss with grouping, client order ids), positions and margin, WebSocket feeds, advanced actions (dead-man's switch, TWAP, spot), and a compact API reference. Copy-pasteable curl for reads; the official Python SDK and @nktkas/hyperliquid for anything that signs.
Desk - how the team works: operating model, the trade lifecycle and ticket, risk limits and sizing arithmetic, the execution protocol, monitoring and routines, post-trade review, incident playbooks, and the strategy lab.
Other agent setups
HyperGrok is for a coordinated Hyperliquid desk in Grok Bot. For a different setup, these Galleon projects can help:
- Boomkin sets up a native Hermes DeFi profile with modular skill packs and official tool connections.
- crypto-defi-skills lets you add individual workflows to an existing agent: lending, liquidity provision, routing, portfolio review and more.
Neither is required to use HyperGrok. Installing instructions does not connect a wallet or authorize a trade.
Trading controls
- You approve every trade, by ticket id, after seeing the exact order. The line you type is evidence; the gate that enforces it sits outside the chat, in a Grok Bot Auto-review Ask first rule, because a Bot that can read an approval could also write one.
- A trade-only API wallet, provisioned through Grok Bot's secure secret store, is the only key the desk ever holds. It can trade; it cannot withdraw.
- Sized on a stressed stop. The desk includes assumed adverse stop fills and taker fees on both legs when sizing. Actual losses can exceed that assumption. See what a stop costs.
- Ceilings you cannot trade through. Your limits file may only tighten the desk's own caps, never loosen them.
- Testnet first. Every new kind of action is rehearsed with play money before it touches mainnet.
- One writer. Six Bots read; one Bot sends, once per approval, and reconciles by client order id.
- Separate process and outcome. The Trade Reviewer records both in a journal you can read.
Perpetual futures can liquidate an account. HyperGrok is documentation and instructions, not financial advice.
Also runs in Grok Build, Cursor, Claude Code, Codex and Gemini CLI
Choose the guide for your runtime. Each uses the same skills and ticket process; support for roles, rules and hooks differs.
| Runtime | Setup | Roles and controls |
|---|---|---|
| Claude Code | Install from the plugin marketplace | Seven subagents and an exchange-write confirmation hook; load the operating model explicitly |
| Cursor | Open the pinned checkout and enable the plugin | Seven role profiles and desk rules; no Claude Code hook |
| Grok Build | Install the pinned release | Skills and agent directories; rule loading is unverified |
| Codex | Install from the Codex marketplace | Skills, with the seven roles run as labelled passes |
| Gemini CLI | Install the extension | Skills and GEMINI.md, with roles run as labelled passes |
The Claude Code hook asks for confirmation when a Bash command or a named script looks like an exchange write. It cannot bind a request to a ticket or inspect every imported path. Every runtime still needs verified native approval coverage before an API wallet is provisioned. The guides distinguish manifest support from observed native installation.
The same pack installs as a skill:
npm exec --package=skills@1.5.23 -- skills add galleonlabs/hypergrok-trading-desk
The complete resources also install from npm:
npm install --save-exact --ignore-scripts hypergrok-trading-desk@1.7.1
python3 node_modules/hypergrok-trading-desk/scripts/desk_doctor.py --offline
The package contains the instructions, role profiles, plugin manifests and read-only Python tools. It has no JavaScript entry point, runtime dependencies or install hooks; installation does not start a desk or connect a wallet.
Live listings: HypurrCollective ecosystem map · skills.sh · cursor.directory · botdirectory.ai
After installation, load desk-operating-model using the command or context mechanism in your runtime guide.
Inside the repository
SETUP.md what your Grok Bot follows to build the desk
agents/ seven roles: Bot profile card + full system prompt
skills/ seventeen skills (bootstrap, hyperliquid-*, desk-*)
template/ exact public Grok Bot profile and skill hashes
scripts/ zero-key market, history, stop-cost and every-DEX account reads, offline verification, release checks
docs/ how it works, FAQ, install pages, stop cost, account read, provenance
assets/ the mascot, logo, README graphics and their generator
| Doc | |
|---|---|
| How the desk works | roles, files, trust boundaries |
| FAQ | keys, approvals, testnet, customising the team |
| Research datasets | collect, verify and hand off historical evidence |
| Stop cost | what a triggered stop costs, from the live book |
| Account read | positions and equity across the main DEX, every HIP-3 DEX and spot |
| Skills index | every skill and who uses it |
| Grok Bot template | public profile, publish contract and clean-install evaluation |
| Provenance | sources and licences |
| Contributing · Security · Changelog |
Get help and keep up
- Updates: use GitHub's Watch → Custom → Releases to follow new releases.
- Setup help: check the FAQ, then ask in Discussions. Share your runtime, release and failing command; keep keys and private account details out.
- Bugs: open an issue with a reproduction and sanitized output. Follow the community guidelines.
- Contribute: see Contributing, the fork review and security policy. Share reproducible fixes and source-backed documentation improvements.
License and credit
MIT licensed, with the copyright and permission notice retained when reusing copies or substantial portions. Created by Andrew Wilkinson and Galleon Labs.
See reuse and attribution for a ready-to-copy credit line. If HyperGrok Trading Desk helps your work, a star on the original repository is appreciated and entirely optional.
HyperGrok has no token and will not launch one. Read the FAQ.
Releases