How to size Hyperliquid trades and set leverage so an agent stays inside its owner's caps by design rather than by bouncing off them: what the per-order and daily notional limits actually count, why every order sent costs its full size for the day whether or not it trades, why closing a position also consumes the budget, when to set leverage, and how to read liquidation distance. Use alongside hyperliquid-trading before deciding a size or a leverage. NOT a substitute for the caps themselves, which are enforced server-side.
cp -r cryptoskill/skills/mcp-servers/cryptolir-hyperliquid-risk .claude/skills/clawhub install cryptolir-hyperliquid-riskCapabilities below are detected automatically by an open-source scanner that reads the skill's text and scripts (see how this is computed). Not measured means the scanner couldn't make a confident call — it is NOT a green check, and you should treat it as a possible red flag until a human or a stronger scanner has measured it.
read_only Phase 1 single-mode classification — multi-mode breakdown deferred to Phase 2.
We did not find any well-known hosted services in this skill's text or scripts. This does NOT mean the skill is local-only — it might use services we don't yet recognize, or talk to them through code paths our scanner can't reach. A complete dependency list (every package, library, and binary, with integrity hashes) is on the roadmap; today we only show recognized hosts.
No one has audited this skill yet. That is different from “audited and clean” — it just means no professional reviewer (a security firm, the CryptoSkill team, or a verified independent researcher) has signed off on it. There are no audit reports to read. How reviewer levels work →
SKILL.md → SOURCE.md → TRUST.auto.yaml → Browse directory →
Auto-generated by cryptoskill/extract-capabilities/0.3.1 · hosted-service list version 2026-09-06 · how this is computed