CC solana-trader
Solana wallet management and token trading via Jupiter aggregator. Check balances, view transaction history, swap tokens, and manage your Solana portfolio.
Solana wallet management and token trading via Jupiter aggregator.
As a process C 60/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
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.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
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
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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 · 10
✓ No critical or high findings
Medium and low: 10
-
medium Risky intent
intent-wallet-secretsSKILL.md:113Handles crypto-wallet secrets (seed / mnemonic / private key) — a classic stealer target**From seed phrase (mnemonic):**
-
medium Risky intent
intent-wallet-secretsSKILL.md:117Handles crypto-wallet secrets (seed / mnemonic / private key) — a classic stealer target# Enter your 12/24 word seed phrase when prompted
-
medium Risky intent
intent-wallet-secretsSKILL.md:122Handles crypto-wallet secrets (seed / mnemonic / private key) — a classic stealer target> ⚠️ **Security**: Never share your private key or seed phrase. Store keypair files with restricted permissions: `chmod 600 ~/.config/solana/*.json`
-
medium Exfiltration
net-credential-useSKILL.md:182Credential used in a network call (verify the destination is the intended service)curl -s "https://api.helius.xyz/v0/addresses/${WALLET}/transactions?api-key=…&limit=10" | jq '.[] | {signature: .signature, type: .type, timestamp: .timestamp, fee: .fee}' -
low Secrets in code
secret-high-entropy-tokenSKILL.md:59High-entropy token-like string (may be an id, hash or a credential) (documentation table row)| `FEE_ACCOUNT` | `8KDD…bNN` | Solana wallet to receive fees |
table -
low Exfiltration
exfil-secret-in-urlSKILL.md:182Credential passed in a URL query string (normal for some APIs — verify the host is the intended service) (placeholder value)curl -s "https://api.helius.xyz/v0/addresses/${WALLET}/transactions?api-key=…&limit=10" | jq '.[] | {signature: .signature, type: .type, timestamp: .timestamp, fee: .fee}'placeholder -
low Secrets in code
secret-high-entropy-tokenSKILL.md:232High-entropy token-like string (may be an id, hash or a credential)| Wrapped SOL | SOL | So11…112 | 9 |
-
low Secrets in code
secret-high-entropy-tokenSKILL.md:233High-entropy token-like string (may be an id, hash or a credential)| USD Coin | USDC | EPjF…t1v | 6 |
-
low Secrets in code
secret-high-entropy-tokenSKILL.md:234High-entropy token-like string (may be an id, hash or a credential)| Tether | USDT | Es9v…NYB | 6 |
-
low Secrets in code
secret-high-entropy-tokenSKILL.md:235High-entropy token-like string (may be an id, hash or a credential)| Bonk | BONK | DezX…263 | 5 |
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 60/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 5 mutating operations with no state check
- 85Steps. 40 steps, 1 vague phrases
- 100Tools and files. No external tools needed
- 100Failures and branches. 2 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3762 tokens
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 14 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
- -218 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +3Description length 155: enough signal without eating the budget
- +4Structure: 35 headings
- +3Step-by-step instructions: 40 items
- +4Has examples (25 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 70.