hyperliquid

Hyperliquid L1 perps DEX (69% market share)

Quality

51%

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 essentially a label rather than a functional skill description. It identifies the platform (Hyperliquid) and its market context but completely fails to describe what actions the skill performs or when Claude should select it. Without concrete capabilities or trigger guidance, Claude would struggle to know when to use this skill.

Suggestions

Add concrete actions the skill performs, e.g., 'Places and manages perpetual futures trades, queries open positions, checks funding rates, and retrieves market data on Hyperliquid L1 DEX.'

Add an explicit 'Use when...' clause with trigger terms, e.g., 'Use when the user asks about Hyperliquid trading, perpetual futures, perps positions, funding rates, or DEX order management.'

Remove the market share statistic ('69% market share') as it provides no selection value and replace it with actionable capability details.

Dimension	Reasoning	Score
Specificity	The description provides no concrete actions whatsoever. It only names the platform ('Hyperliquid L1 perps DEX') and a market share statistic, but does not describe what the skill actually does (e.g., place trades, query positions, analyze funding rates).	1 / 3
Completeness	The description fails to answer both 'what does this do' and 'when should Claude use it'. There is no explanation of capabilities and no 'Use when...' clause or equivalent trigger guidance.	1 / 3
Trigger Term Quality	It includes some domain-relevant terms like 'Hyperliquid', 'L1', 'perps', and 'DEX' that a user familiar with crypto trading might use. However, it misses common variations like 'perpetual futures', 'trading', 'orders', 'positions', or 'leverage'.	2 / 3
Distinctiveness Conflict Risk	The mention of 'Hyperliquid' specifically is distinctive and unlikely to conflict with other skills. However, the vague nature of the description (no actions specified) means it could overlap with any other crypto/DEX-related skill.	2 / 3
	Total	6 / 12 Passed

Implementation

79%

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-structured command reference that excels at conciseness and actionability — every command is concrete with clear syntax and examples. The main weaknesses are the lack of multi-step workflow guidance with validation checkpoints (important for financial operations) and the monolithic structure that could benefit from splitting detailed reference tables into separate files.

Suggestions

Add a recommended workflow for common trading scenarios (e.g., 'Before trading: 1. Verify credentials with /hl balance, 2. Set leverage, 3. Use DRY_RUN=true to test, 4. Execute trade, 5. Verify with /hl orders')

Include safety/validation guidance for destructive operations like /hl closeall and /hl orders cancelall — e.g., recommend checking /hl balance first and confirming positions before bulk operations

Dimension	Reasoning	Score
Conciseness	The content is lean and efficient — it's essentially a command reference with minimal prose. No unnecessary explanations of what perpetual futures are or how DEXes work. Every section earns its place.	3 / 3
Actionability	Every command is concrete and copy-paste ready with exact syntax, parameters, and practical examples. The configuration section provides exact environment variable names. No vague or abstract guidance.	3 / 3
Workflow Clarity	While individual commands are clear, there's no explicit workflow for common multi-step operations (e.g., setup → check balance → set leverage → open position → monitor → close). For trading operations involving real money, there are no validation checkpoints or confirmation steps mentioned. The DRY_RUN mode is mentioned but not integrated into a recommended workflow.	2 / 3
Progressive Disclosure	The content is well-organized with clear section headers and tables, but it's a fairly long monolithic document. The features list, shortcuts table, and database commands could potentially be split into separate reference files. The two external links at the bottom are helpful but minimal.	2 / 3
	Total	10 / 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: e71a5f6

Reviewed: 11 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.