desk-incident-response
What the desk does when something goes wrong on Hyperliquid or in the autonomous loop - unknown send results, unexpected fills or positions, unprotected positions, stuck or orphaned orders, API outages, rate limiting, suspected API wallet compromise, a gate or guard refusing everything, and a runaway loop. Contain first, halt when in doubt, reconcile from the exchange record, act only through gated tickets, then review. Use the moment anything does not match the ticket.
- Version
- 1.2.0
- License
- MIT
Pinned to revision 4d915c1fa4c1, so it is the text this page describes rather than whatever the author pushed since.
Files
- skills/desk-incident-response/SKILL.md
- skills/desk-incident-response/ATTRIBUTION.md
- skills/desk-incident-response/LICENSE
Every link opens the file at its source, pinned to the revision this page describes.