desk-incident-response SKILL.md skillA
desk-incident-response from galleonlabs/hypergrok-trading-desk is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add galleonlabs/hypergrok-trading-desk/desk-incident-response@v1.1.2Pins v1.1.2 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- galleonlabs/hypergrok-trading-desk
- Path
skills/desk-incident-response/SKILL.md- Versions recorded
- 4
- Latest version
- v1.1.2, committed Oct 8, 2026
- First version recorded
- Aug 16, 2026
- Size
- 8,166 bytes
- Repository stars
- 387
- License
- MIT
What 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 approved tickets, then review. Use the moment anything does not match the ticket.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Incident response An incident is any moment when the exchange record and the desk's expectation disagree, or when the desk cannot see the exchange at all. The reflex is: stop adding, look, contain with approval, then review. Never widen the harm by improvising. ## Declare Any Bot can declare an incident. Post on the floor: ``` INCIDENT INC-20260817-01 | 11:40 UTC | HG-20260817-02 | send timeout, result unknown | owner: Execution Trader ``` The Desk Lead confirms an owner (usually the Execution Trader for order/position incidents, the Risk Manager for exposure incidents, the Desk Lead for access incidents). New proposals pause until the incident is contained. ## Playbooks ### A. Unknown send result (timeout, 5xx, exception after send) 1. Do not resend. 2. `orderStatus` by cloid; `openOrders`; `userFills` since the send; `clearinghouseState`. 3. Found: continue reconciliation as normal; journal that the response was lost. 4. Not found: that is not proof. Wait until the signed `expiresAfter` deadline has passed, then reconcile again. Expiry prevents later acceptance; it does not cancel an order accepted before the deadline or remove its fills. …
Read the whole file at its exact version.
How to install
mdr add galleonlabs/hypergrok-trading-desk/desk-incident-response@sha256:7994c1309ee83a80The line at the top of this page pins the label v1.1.2, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_hgz7y2gczpat325p)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between Aug 16, 2026 and Oct 8, 2026, about one every 18 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.1.2 latest | 2026-10-08 | 5eb1d9a | 8,166 B | A | view · diff |
| v1.1.1 | 2026-10-02 | 1e429e5 | 7,678 B | A | view · diff |
| v1.1.0 | 2026-08-29 | 178de04 | 7,231 B | A | view · diff |
| v1.0.0 | 2026-08-16 | 1ead2e4 | 6,354 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (8166 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
galleonlabs/hypergrok-trading-desk · 387 stars · license MIT · pushed 2026-11-04 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_hgz7y2gczpat325p GET https://markdownregistry.com/api/v1/resolve?ref=galleonlabs/hypergrok-trading-desk/desk-incident-response GET https://markdownregistry.com/api/v1/blob/7994c1309ee83a80f729f8b037fd05e03d313866f892b1b88262345745bb34d1
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from galleonlabs/hypergrok-trading-desk
Every file in galleonlabs/hypergrok-trading-desk