BB openburn
Automates collecting Pump.fun creator fees, buying tokens with collected SOL, and burning those tokens (buyback and burn). Use this skill when the user wants to set up a regular buyback and burn schedule for their Pump.fun tokens.
As a process B 68/100 · Nearly there — weak spots: result and completion, 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
- 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
-
medium Risky intent
intent-wallet-secretsSKILL.md:52Handles crypto-wallet secrets (seed / mnemonic / private key) — a classic stealer target- `CREATOR_WALLET_PRIVATE_KEY` (The private key of the wallet to burn from)
-
low Secrets in code
secret-high-entropy-tokenscripts/burn.ts:36High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)const SOL_MINT = new PublicKey("So11…112");quoted -
low Secrets in code
secret-password-literalscripts/burn.ts:183Hard-coded password / key literal (may be an example)let secretKey: Uint8Array;
-
low Secrets in code
secret-password-literalscripts/burn.ts:186Hard-coded password / key literal (may be an example)secretKey = Uint…rom(JSON.parse(privateKeyString));
-
low Secrets in code
secret-password-literalscripts/burn.ts:189Hard-coded password / key literal (may be an example)secretKey = bs58.decode(privateKeyString);
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 68/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 65Failures and branches. 3 branches
- 70When it triggers. States when to use, but not when not to
- 100Tools and files. No external tools needed
- 100Steps. 11 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1022 tokens
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
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 230: enough signal without eating the budget
- +4Structure: 4 headings
- +3Step-by-step instructions: 11 items
- +4Has examples (6 code blocks)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 87.