AC hyperliquid-plan
Build an exact unsigned Hyperliquid ticket for an entry, exit, reduction, cancel, modify, trigger order, TWAP, leverage change, or isolated-margin change. Use when the user has chosen an intent and asks for size, limits, order fields, risk checks, or a preflight plan. Planning only; not for market selection, live monitoring, signing, or submission.
Build an exact unsigned Hyperliquid ticket for an entry, exit, reduction, cancel, modify, trigger order, TWAP, leverage change, or isolated-margin change.
As a process C 59/100 · Has gaps — weak spots: result and completion, failures and branches, consistency
How to improve
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 13. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 59/100
- 0Result and completion. Does not say what the result is
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 40Consistency. Frontmatter name (hyperliquid-plan) differs from the folder (galleon-hyperliquid-plan)
- 60Tools and files. Uses tools (node) that frontmatter does not declare
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 15 steps
- 100When it triggers. States when to use and when not to
- 100Execution cost. Instruction body is 1158 tokens
- 100Running it twice. No mutating operations
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 350: enough signal without eating the budget
- +4Structure: 8 headings
- +3Step-by-step instructions: 15 items
- +4Reference files are cited in the instructions (7 of 7)
- +3All 1 scripts are documented
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 92.