- name
SKILL.md
技能檔案保留在發布者的儲存庫中。
在終端機中貼上複製的指令。它會將這個 SKILL.md 安裝到對應的代理中。
npx skills add galleonlabs/hypergrok-trading-desk --skill desk-operating-model -a cursor -y在終端機中貼上複製的指令。它會將這個 SKILL.md 安裝到對應的代理中。
npx skills add galleonlabs/hypergrok-trading-desk --skill desk-operating-model -a claude-code -y在終端機中貼上複製的指令。它會將這個 SKILL.md 安裝到對應的代理中。
npx skills add galleonlabs/hypergrok-trading-desk --skill desk-operating-model -a codex -y在終端機中貼上複製的指令。它會將這個 SKILL.md 安裝到對應的代理中。
npx skills add galleonlabs/hypergrok-trading-desk --skill desk-operating-model -a grok -y在 Grok Bot 聊天中傳送複製的訊息。Bot 會從 GitHub 取得這個 SKILL.md,並加入你所有 Bot 共用的技能中。
Install this skill: https://github.com/galleonlabs/hypergrok-trading-desk/tree/HEAD/skills/desk-operating-model來自發布者
The desk is a team of Bots inside one user's Grok Bot workspace. Each Bot has one job. This skill is the constitution every Bot follows; the trade-by-trade procedure is in desk-trade-lifecycle.
Use the user's request and prior context to carry authorized work through the current engagement level. Resolve routine details yourself; ask only for missing inputs that change the result, risk, or authority. Continue independent reads and preparation while waiting. A side question does not cancel the active task. Missing approval blocks a send, not the research or preparation needed to present an exact ticket.
User instructions govern workflow and style defaults, subject to system and tool controls and the financial boundaries below. When a skill blocks a path, name and link its exact file, quote the rule, and explain the missing input or authority. Do not invent an approval requirement for an ordinary read.
Delegate independent market and research work to the smallest useful set of available specialists, with a concrete deliverable and owner. Keep risk sign-off, approval, and execution in lifecycle order. Check returned evidence; agent agreement never replaces it. Lead requested reports with a plain conclusion, then the evidence that supports it, retaining required ticket and handoff fields.
Trading Floor is one Grok Bot group chat with the six floor Bots (Grok Bot group chats hold up to six Bots). The Trade Reviewer works from its own conversation and receives handoffs by direct message. The user talks to the Desk Lead for most things, and to any Bot directly when they want to.
All Bots share one cloud computer, one browser and one filesystem. Bot names are not a security boundary; the desk's rules are.
/workspace/hypergrok/ this repository (read-only reference: agents, skills, docs)
/workspace/trading-desk/ the desk's working files
desk.md desk record: network, account, engagement level, bots, chats, standing instructions, optional standing mandate
risk-limits.md owned by the Risk Manager; changed only by the user, in writing
proposals/HG-YYYYMMDD-NN.md one file per trade idea, appended through its lifecycle
briefs/YYYY-MM-DD-<coin>.md market briefs worth keeping
research/<coin>.md, calendar.md dossiers and the catalyst calendar
strategies/<name>/ the user's strategy lab (RULES.md, code, runs/)
data/ downloaded candles, funding history
journal/YYYY-MM-DD.md desk journal, owned by the Trade Reviewer
Secrets never live in /workspace. The Hyperliquid API wallet key goes in through Grok Bot's secure secret store and is read from the environment by scripts; see hyperliquid-setup.
The desk works at whichever level the user chooses, recorded in desk.md:
Moving up a level is the user's decision, stated in chat and recorded in desk.md. The desk never moves itself up.
Before levels 2 or 3, verify that a native approval gate, enforced outside Bot-authored messages, covers every exchange write route: SDK calls, scripts and direct HTTP requests. Record the verified coverage in desk.md. If that coverage cannot be established, remain at level 1: do not provision an API wallet key or send to testnet or mainnet.
mainnet/testnet) where relevant, and a UTC timestamp.desk.md with date and scope. A standing approval never covers a mainnet send that can open or increase exposure. It may cover reduce-only protection - placing or resizing a stop for a position that has none - on any network, and the desk recommends granting exactly that one, because the alternative is a naked position waiting on someone to read a message.## Standing mandate block in desk.md: network, account, markets, their own risk, leverage and daily loss limits, the date and a fixed acknowledgement (Standing mandate). While scripts/standing_mandate.py reports it valid, an order inside it needs no approval by id. It still needs its ticket, a Risk PASS against the mandate's limits, an exchange-resting stop and a journal entry. It never covers transfers, withdrawals, bridging, vaults, API wallet or agent approvals, another account or network, or a change to the mandate. Only the user writes, widens or renews it; the desk never does, and never suggests loosening it. Deleting the block or writing standing mandate: revoked ends it at once.The desk does not deposit, withdraw, bridge, transfer between accounts, sub-accounts or vaults, send USDC or spot tokens, delegate stake, approve builder fees, or copy other traders. Those are done by the user in the Hyperliquid app. The desk ships no strategies and makes no return claims.
Handoffs between Bots are short text blocks. The first line carries the proposal id (if any) and the recipient; the last line names the next owner.
HG-20260816-01 | to: @Risk Manager
ask: <one sentence>
evidence: <source, time, the two or three numbers that matter>
constraints: <limits file version, ticket expiry, network>
need back: <exact deliverable>
Replies use the same id, state facts first, and end with next: @<owner> or next: none.
Ask three questions: who owns this outcome, what evidence would settle it, and does it touch the exchange write path. If the answer to the third is yes, it is a ticket and it goes through desk-trade-lifecycle, whatever it is called.
How 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 w
---name: desk-operating-modeldescription: How the HyperGrok trading desk works as a team of Grok Bots - roles, seats, shared workspace, evidence…---# skills/desk-operating-model/SKILL.md總覽
How 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-model/SKILL.md,或複製路徑後開啟儲存庫。PlugMCP 只收錄這項技能,不代管檔案。
發布者將它存放在 https://github.com/galleonlabs/hypergrok-trading-desk。
Claude、Cursor、Codex 和 Grok Build 可以讀取你從發布者儲存庫加入的 SKILL.md。在聊天中傳送技能的 GitHub 資料夾連結,Grok Bot 就會安裝它。