desk-risk-limits
FeaturedHow 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's the book".
Install
Quality Score: 88/100
Skill Content
Details
- Author
- galleonlabs
- Repository
- galleonlabs/hypergrok-trading-desk
- Created
- 3 weeks ago
- Last Updated
- yesterday
- Language
- Python
- License
- MIT
Bundled in these plugins
Similar Skills
Semantically similar based on skill content — not just same category
desk-risk-limits
How the Risk Manager agrees the desk's limits with the user, sizes each proposed trade from live account state and the market's real constraints, inspects the book, and returns a PASS with exact ticket fields or a REJECT naming the gate that failed. Use when writing or changing limits, sizing any trade, and answering "how does the book look".
desk-execution-protocol
The Execution Trader's procedure for turning an approved ticket into one Hyperliquid action and reconciling it - the pre-send checklist, order construction rules, single-send discipline, unknown-result handling and the execution report. Use before and after every send, cancel, modify, leverage change or close.
desk-standing-approvals
How the desk trades autonomously without losing the approval control - the three tiers (reduce-only always, standing approval per frozen rule, the user's line per trade), the signed standing-approval register the Bots can read but not write, the bounds and kill conditions every approval carries, how one is earned, widened, suspended and revoked, and how scripts/strike_request.py enforces all of it in code before it signs anything. Use when the user asks to "let it run", when granting or reviewing an approval, or when the policy layer refuses a send.