hyperliquid

Hyperliquid L1 perps DEX (69% market share)

Quality

55%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./src/skills/bundled/hyperliquid/SKILL.md

Quality

Discovery

22%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This description is severely underdeveloped, functioning more as a label than a skill description. It identifies a specific platform (Hyperliquid DEX) but completely fails to describe what actions the skill enables or when Claude should select it. The market share statistic is irrelevant fluff that doesn't help with skill selection.

Suggestions

Add concrete actions the skill performs (e.g., 'Query positions, place orders, check funding rates, analyze trading pairs on Hyperliquid')

Add an explicit 'Use when...' clause with trigger terms like 'Hyperliquid trading', 'perp positions', 'DEX orders', 'perpetual futures'

Remove the market share statistic and replace with functional capability descriptions that help Claude understand when to select this skill

Dimension	Reasoning	Score
Specificity	The description contains no concrete actions whatsoever. It only identifies a platform ('Hyperliquid L1 perps DEX') and a market share statistic, but doesn't describe what the skill actually does.	1 / 3
Completeness	Fails to answer both 'what does this do' and 'when should Claude use it'. There is no 'Use when...' clause and no description of capabilities - only platform identification and a market share claim.	1 / 3
Trigger Term Quality	Contains some relevant domain keywords ('Hyperliquid', 'perps', 'DEX', 'L1') that users in crypto/DeFi might use, but lacks common variations like 'perpetual futures', 'trading', 'derivatives', or action-oriented terms.	2 / 3
Distinctiveness Conflict Risk	The specific platform name 'Hyperliquid' provides some distinctiveness, but without describing what actions the skill performs, it could conflict with other crypto/trading skills. The niche is identifiable but not clearly scoped.	2 / 3
	Total	6 / 12 Passed

Implementation

87%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a well-crafted command reference skill that excels at conciseness and actionability. The tabular format efficiently presents 50+ commands with clear descriptions and examples. The main weakness is the lack of workflow guidance for complex multi-step operations like position management or risk scenarios.

Suggestions

Add a brief workflow section showing recommended order of operations (e.g., 'Before trading: 1. Check balance, 2. Set leverage, 3. Review funding rates')

Include validation guidance for risky operations like withdrawals or closing all positions (e.g., 'Verify positions with /hl balance before /hl closeall')

Dimension	Reasoning	Score
Conciseness	Extremely lean and efficient - pure command reference with no unnecessary explanations. Assumes Claude knows what perpetual futures, leverage, and TWAP orders are. Every line serves a purpose.	3 / 3
Actionability	Highly actionable with copy-paste ready commands throughout. Clear examples show exact syntax for common operations like opening positions, setting leverage, and executing TWAP orders.	3 / 3
Workflow Clarity	Commands are well-organized by category, but lacks explicit workflow sequences for multi-step operations. No validation checkpoints for risky operations like large trades or withdrawals. Missing guidance on order of operations (e.g., set leverage before opening position).	2 / 3
Progressive Disclosure	Well-structured with clear sections progressing from Quick Start to detailed command categories. External resources linked at the end. Content is appropriately organized for a command reference skill.	3 / 3
	Total	11 / 12 Passed

Validation

90%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: alsk1992/CloddsBot
Commit: 2a8c94e

Reviewed: 29 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.