BC orderly-perps
Trade perpetual futures on Orderly Network (via HyperClaw broker). Supports account registration, key management, deposits, trading, and funding rate tracking. Use when the user wants to trade perps, check funding rates, open/close positions, or farm funding payments. Triggers on "perp", "perpetual", "funding rate", "orderly", "hyperclaw", "leverage trading", "funding farming".
Trade perpetual futures on Orderly Network (via HyperClaw broker).
As a process C 62/100 · Has gaps — weak spots: result and completion, failures and branches, running it twice
What is at stake
The skill contains fragments that, in the wrong hands, cost money or data. Below: what the installer risks and what the author should do.
The instructions or scripts send data out: environment variables, keys, file contents, chat history. You may never notice, because the agent performs the upload as "part of the task".
If the upload is not needed for the task, remove it: catalogs flag such skills and delist them. If it is needed, name the destination explicitly, say what leaves the machine, and give the user a switch.
How to improve
- Address the high-severity findings: each costs 18 safety points. If one is a false positive, add the rule id to guard.allow in spec.yaml.
- 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 · 4
-
high Exfiltration
exfil-webhook-urlSKILL.md:227Webhook / callback URL commonly used for exfiltration (verify the destination)- Dashboard: [Ori Dashboard](https://admissions-human-views-icq.trycloudflare.com)
Medium and low: 3
-
low Secrets in code
secret-high-entropy-tokenscripts/orderly-add-key.mjs:27High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)verifyingContract: '0xCc…ccC'
quoted -
low Secrets in code
secret-high-entropy-tokenscripts/orderly-deposit.mjs:23High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)USDC_ADDRESS: '0x83…913'
quoted -
low Secrets in code
secret-high-entropy-tokenscripts/orderly-register.mjs:98High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)verifyingContract: '0xCc…ccC' // Standard address
quoted
Files scanned: 14. 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 62/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
- 30Running it twice. 3 mutating operations with no state check
- 70When it triggers. States when to use, but not when not to
- 70Inputs and preconditions. Inputs and preconditions are listed
- 85Steps. 26 steps, 3 vague phrases
- 100Tools and files. No external tools needed
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1366 tokens
- low 11 top-level sections: this looks like several domains in one skill
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
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- -5TODO / placeholder text left in the skill
- -31 of 12 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +5Description quotes 6 example trigger phrases
- +3Description length 380: enough signal without eating the budget
- +4Structure: 28 headings
- +3Step-by-step instructions: 26 items
- +4Has examples (21 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 81.