desk-monitoring

Configures read-only market and account watches, alerts, and scheduled desk briefs for Hyperliquid trading.

Updated Sep 7, 2026
One-click install
npx skills add https://github.com/swcstudiospace/hypergrok-autonomous-desk --skill desk-monitoring-swcstudiospace
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: desk-monitoring
Source: https://github.com/swcstudiospace/hypergrok-autonomous-desk/tree/main/skills/desk-monitoring
Command: npx skills add https://github.com/swcstudiospace/hypergrok-autonomous-desk --skill desk-monitoring-swcstudiospace

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Trading desks need continuous awareness of markets, positions, and system health between trades, but watches that silently fail or act on their own create hidden risk. This Skill defines how to run read-only monitoring routines, briefs, and alerts that never touch the exchange and never mistake a dead feed for a calm market. ## Core Features & Use Cases - Scheduled Routines: Set up cron or timer-based routines such as the autonomous cycle, heartbeat watch, daily desk brief, book checks, funding snapshots, and weekly reviews. - Polling and WebSocket Watches: Run price, funding, fill, margin, and liquidation watches via /info polling scripts or WebSocket subscriptions like allMids, l2Book, and userFills. - Three-Outcome Alerting: Every watch reports fired, not fired, or unavailable, with staleness bounds so failed reads escalate as explicit alerts instead of false silence. - Use Case: A user asks to "watch ETH funding and alert me if it flips sign." The Skill sets up a polling watch on metaAndAssetCtxs, logs to watch/<name>.log, and alerts with the value, threshold, source, and UTC time when the condition fires. ## Quick Start Ask the desk to set up a watch that alerts you when BTC crosses a price level or when the heartbeat file goes stale.

Frequently Asked Questions about desk-monitoring

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up price alerts for Hyperliquid markets?▼

Create a watch that polls `allMids` or `candle` data every 5-15 seconds per market, or subscribe via WebSocket for lower latency. When the price crosses your level, the watch alerts you and the Desk Lead with the value, threshold, source, and UTC time.

What is the difference between polling and WebSocket watches?▼

Polling uses repeated `/info` calls on a loop and is simple but rate-limited, while WebSocket subscriptions like `userFills` and `orderUpdates` stream events in real time. WebSocket suits fills and order updates but needs a supervised process with logging.

Can a watch place a protective stop order automatically?▼

No. Watches are strictly read-only and may never send to the exchange. A protective condition opens a `protect` proposal under `proposals/`, and the next autonomous cycle takes it through the gate and the sender.

Why does a watch alert say unavailable instead of not fired?▼

A failed request, empty response, or stale data means the watch could not tell, which is a third outcome distinct from the condition not firing. Reporting a dead feed as calm is treated as the most dangerous monitoring failure, so it escalates as an unavailable alert.

How many watches can run at once on the desk?▼

Only a few watches should run concurrently since each is a process on the shared computer, and polling too fast risks rate limits that blind the desk. Stop position-related watches when the desk goes flat for the day.