BC orderly-api-authentication
Complete authentication guide for Orderly Network - EIP-712 wallet signatures for EVM accounts, Ed25519 message signing for Solana accounts, and Ed25519 signatures for API requests
As a process C 55/100 · Has gaps — weak spots: result and completion, when it triggers, execution cost
How to improve
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
For the model run — optional
- 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 · 5
✓ No critical or high findings
Medium and low: 5
-
low Secrets in code
secret-high-entropy-tokenSKILL.md:93High-entropy token-like string (may be an id, hash or a credential) (documentation table row)| **Off-chain** | Account registration, API key management | `0xCc…ccC` | `0xCc…ccC` |
table -
low Secrets in code
secret-high-entropy-tokenSKILL.md:94High-entropy token-like string (may be an id, hash or a credential) (documentation table row)| **On-chain** | Withdrawals, internal transfers, settle PnL | `0x6F…203` | `0x18…bff` |
table -
low Secrets in code
secret-high-entropy-tokenSKILL.md:107High-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-tokenSKILL.md:121High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)? '0x18…bff'
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:122High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded): '0x6F…203',
quoted
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 8962 tokens (recommended < 5000); move details to references/
Process rating: all ten parameters 55/100
- 0Result and completion. Does not say what the result is
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 40Execution cost. Instruction body is 8962 tokens: crowds the task out of the window
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 33 steps
- 100Consistency. Name and required fields are in place
- 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 30 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
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- -212 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +3Description length 180: enough signal without eating the budget
- +4Structure: 69 headings
- +3Step-by-step instructions: 33 items
- +4Has examples (43 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 72.
External checks
ClawHub: suspicious
This is a documentation-only Orderly Network authentication guide, but it includes unsafe private-key logging and high-impact trading or withdrawal examples that need careful review before copying.
LLM: suspicious (high) · VirusTotal: · 29 May 2026