BD gank — solana trading terminal for agents
gank is a multi-wallet solana trading terminal. launch tokens on pump.fun, run swarm buys, volume bots, copy trades, manage wallets. we literally have the most toxic platform atm and now your agent...
gank is a multi-wallet solana trading terminal.
As a process D 41/100 · Unfinished process — 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.
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 · 2
✓ No critical or high findings
Medium and low: 2
-
medium Risky intent
intent-wallet-secretsSKILL.md:86Handles crypto-wallet secrets (seed / mnemonic / private key) — a classic stealer targetgives you a `...pump` address upfront. the `keypair` field is the **mint keypair** (token contract address keypair, not a wallet private key), pass it straight to `/launch` as `reserved_mint_keypair`.
-
low Risky intent
intent-wallet-secretsskill.json:66Handles crypto-wallet secrets (seed / mnemonic / private key) — a classic stealer target (quoted — discussed, not commanded)"note": "API keys start with pb_ and authenticate all requests. Wallet private keys are encrypted server-side and never returned by the API. The reserve-mint endpoint returns a mint keypair (the token
quoted
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")
Process rating: all ten parameters 41/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 1 mutating operations with no state check
- 40Consistency. Frontmatter name (gank — solana trading terminal for agents) differs from the folder (gank-solana-bundler)
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 100Steps. 8 steps
- 100Execution cost. Instruction body is 2218 tokens
- 100Progress reporting. Reports progress
- 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
- +1No license
- +2Single-language instructions
- +3Description length 200: enough signal without eating the budget
- +4Structure: 15 headings
- +3Step-by-step instructions: 8 items
- +4Has examples (49 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 67.