CC FarmDash Futures Strategist
Hyperliquid perps strategist: market scans, funding rates, position sizing, and user-signed EIP-712 order execution & cancellation with drawdown guardrails.
As a process C 58/100 · Has gaps — weak spots: inputs and preconditions, consistency, execution cost
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The purpose itself is risky: wallets, browser password stores, offensive security. Even an honest implementation gives the agent access to things that cost money.
Explain in the description why the access is needed and how it is limited; add tests that show refusals on dangerous requests.
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- 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 · 3
✓ No critical or high findings
Medium and low: 3
-
medium Risky intent
intent-wallet-secretsopenapi.yaml:140Handles crypto-wallet secrets (seed / mnemonic / private key) — a classic stealer target`accountAddress` only when the signer directly owns the account. It does not require a private key or seed phrase. The
-
medium Risky intent
intent-wallet-secretsSKILL.md:98Handles crypto-wallet secrets (seed / mnemonic / private key) — a classic stealer target* never ask for a private key, seed phrase, or wallet export
-
medium Risky intent
intent-wallet-secretsSKILL.md:103Handles crypto-wallet secrets (seed / mnemonic / private key) — a classic stealer target* Never ask the user to paste a private key, seed phrase, or raw wallet export into the agent.
Files scanned: 4. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens) - warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
body-longSKILL.md body ≈ 12847 tokens (recommended < 5000); move details to references/ - note
frontmatter-keyunknown frontmatter key "homepage" - note
frontmatter-keyunknown frontmatter key "env"
Process rating: all ten parameters 58/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 40Consistency. Frontmatter name (FarmDash Futures Strategist) differs from the folder (farmdash-futures-strategist)
- 40Execution cost. Instruction body is 12847 tokens: crowds the task out of the window
- 50When it triggers. No condition that starts the skill
- 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 85Steps. 179 steps, 1 vague phrases
- 100Failures and branches. 20 branches, has a failure section
- 100Running it twice. Mutating operations check current state
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 27 top-level sections: this looks like several domains in one skill
- low The skill ranks results itself: that belongs to the system behind the tool, not the model
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
- +4Description does not say when NOT to use the skill (false activations)
- +1No license
- +2Single-language instructions
- +3Description length 156: enough signal without eating the budget
- +4Structure: 72 headings
- +3Step-by-step instructions: 179 items
- +3Output format is stated explicitly
- +4Has examples (11 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 58.