skills.rest
swcstudiospace
swcstudiospaceOFFICIAL
Explore all skills by this author →
Website𝕏@govantarcticaGitHub

desk-operations

Operate an autonomous Hyperliquid trading desk with secrets management, execution tuning, and risk controls.

Updated Sep 7, 2026
Search Tags:#monitoring#risk management#secrets management#hyperliquid#trading operations#strategy review#maker-first execution
One-click install
npx skills add https://github.com/swcstudiospace/hypergrok-autonomous-desk --skill desk-operations-swcstudiospace
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: desk-operations
Source: https://github.com/swcstudiospace/hypergrok-autonomous-desk/tree/main/skills/desk-operations
Command: npx skills add https://github.com/swcstudiospace/hypergrok-autonomous-desk --skill desk-operations-swcstudiospace

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Running an autonomous trading desk in production requires solving operational problems that experiments ignore: keeping the API key out of plain text, avoiding unnecessary taker fees, proving a strategy on paper before real money, demoting strategies that stop working, and giving a human a dashboard and alerts to supervise it all. ## Core Features & Use Cases - Secrets Management: Resolve the Hyperliquid API key from the environment, a secrets-manager command (1Password, AWS, GCP, Azure, Vault, Doppler), or a locked-down file, without ever exposing the value. - Maker-First Execution & Fee Tuning: Send post-only orders with taker fallback, read real fees from userFees, and let the execution-stats controller tune maker offset and wait per market from measured fill rates. - Strategy Lifecycle Gates: Enforce a paper-record gate before going live, run weekly walk-forward re-reviews with automatic demotion, and check pairwise correlation before raising any strategy's share. - Risk Ladder & Liquidity Check: Shrink size automatically as drawdown crosses configured rungs, and defer entries when resting book depth is too thin for the intended notional. - Use Case: Before promoting a strategy to mainnet, run the paper-record script to confirm its testnet results match the backtest, check the correlation report, then read the dashboard and alerts weekly to supervise it. ## Quick Start Ask the agent to walk through the operator checklist for taking the desk from testnet to mainnet, starting with verifying the key source via a dry-run send.

Frequently Asked Questions about desk-operations

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

FAQPage Schema
How do I store a Hyperliquid API key securely for an automated trading bot?▼

Resolve the key at signing time from an environment variable, a secrets-manager command (1Password, AWS, GCP, Azure, Vault, or Doppler), or a mode-600 file owned by the running user. The resolver reports which source was used but never the value, and rejects anything that is not a 32-byte hex string.

How do I reduce taker fees on Hyperliquid orders?▼

Use maker-first execution: send a post-only limit order at the mid adjusted by a maker offset, wait a configured number of seconds, then cancel and fall back to a bounded IOC for the unfilled remainder. An execution-stats script measures real fill rates per market and tunes the offset and wait within clamped bounds.

When should a trading strategy go from paper to live?▼

Only after a signed paper record shows enough closed trades over enough days on testnet, with win rate, average hold, stop rate, and drawdown all within tolerance of the backtest. The engine refuses live status without this record, since a mismatch means the market changed or the backtest was wrong.

Why did my trading strategy get demoted automatically?▼

The weekly re-review script reruns the strategy review on fresh history, including a recent-window check, and demotes one rung on rejection: live to paper, paper to draft. Each demotion is logged as an event, an alert, and a journal line; nothing ever moves a status upward automatically.

Why did position size drop after a drawdown?▼

The risk ladder in the policy scales down gross exposure and per-trade budget when drawdown from the recorded equity peak crosses a configured rung, such as 0.5x at 3% and 0.25x at 6%. Size returns automatically as equity climbs back inside a rung; the peak is never lowered.

Can I expose the trading dashboard on a public interface?▼

No. The dashboard server serves the autonomy folder read-only on localhost and is meant for a private network or SSH tunnel only. That folder contains send logs and execution records, so exposing it publicly would leak sensitive trading activity.

Related Skills

Explore More Finance & Accounting Skills→
GhostOf0daysGhostOf0days

risk-management

Manage operational risk controls and diagnose limit breaches for trading desks.

Community
Advanced
mataeilmataeil
5

ooda-status

Aggregate OODA-loop cycle counts, domain statuses, confidence scores, actions, and alerts into a dashboard.

Community
Intermediate
NealschNealsch

Forge-Release-Readiness-Assessment

Assesses release candidates against agreed criteria using consolidated quality evidence.

Community
Intermediate
AgenticAIPlanAgenticAIPlan
10

agent-boundary-design

Design agent boundaries with autonomous actions, human confirmation, and refusal rules.

Official
Advanced