AC nansen-trading
Execute DEX swaps on Solana or Base (including cross-chain bridges) and Hyperliquid perpetual trades. Use when buying or selling a token, getting a swap quote, executing a trade, or opening/closing/managing a perp position.
As a process C 62/100 · Has gaps — weak spots: result and completion, when it triggers, running it twice
How to improve
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 · 6
✓ No critical or high findings
Medium and low: 6
-
low Secrets in code
secret-high-entropy-tokenSKILL.md:46High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)- USDC (Solana): `EPjF…t1v`
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:48High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)- Native SOL: `So11…112`
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:117High-entropy token-like string (may be an id, hash or a credential) (documentation table row)| SOL | Solana | `So11…112` |
table -
low Secrets in code
secret-high-entropy-tokenSKILL.md:118High-entropy token-like string (may be an id, hash or a credential) (documentation table row)| USDC | Solana | `EPjF…t1v` |
table -
low Secrets in code
secret-high-entropy-tokenSKILL.md:120High-entropy token-like string (may be an id, hash or a credential) (documentation table row)| USDC | Base | `0x83…913` |
table -
low Exfiltration
read-dotenvSKILL.md:183Reads a .env file (detector / deny-list definition; documentation table row)| `NANSEN_WALLET_PASSWORD` | **Required for `trade execute`.** Wallet encryption password — persisted in `~/.nansen/.env`. Source before executing: `source ~/.nansen/.env && nansen trade execute ...`
detectortable
Files scanned: 2. 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
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 5 mutating operations with no state check
- 60Failures and branches. 2 branches
- 70Inputs and preconditions. Inputs and preconditions are listed
- 85Steps. 14 steps, 1 vague phrases
- 100Tools and files. Tools declared in frontmatter
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2255 tokens
- low 16 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (4 tags): a typed call is more reliable
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
- +1No license
- +2Single-language instructions
- +3Description length 223: enough signal without eating the budget
- +4Structure: 21 headings
- +3Step-by-step instructions: 14 items
- +4Has examples (10 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 84.
External checks
ClawHub: suspicious
This is a real trading skill for irreversible crypto transactions, but it gives broad execution authority and tells agents to persist and source the wallet password from disk.
LLM: suspicious (high) · 13 Aug 2026