BD fuego
Local Solana agent wallet with local infra for transfers (SOL, USDC, USDT), Jupiter swaps, and x402 purch.
Local Solana agent wallet with local infra for transfers (SOL, USDC, USDT), Jupiter swaps, and x402 purch.
As a process D 48/100 · Unfinished process — weak spots: result and completion, when it triggers, running it twice
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
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:33High-entropy token-like string (may be an id, hash or a credential)# Address: DmFy…UZF
-
low Secrets in code
secret-high-entropy-tokenSKILL.md:120High-entropy token-like string (may be an id, hash or a credential)fuego send GvCo…7r5 0.25 --token USDC --yes
-
low Secrets in code
secret-high-entropy-tokenSKILL.md:209High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"address": "DmFy…UZF",
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:401High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"address": "DmFy…UZF",
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:500High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"wallet": "DmFy…UZF",
quoted
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") - note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 48/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. 8 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 60Steps. 56 steps, 6 vague phrases
- 70Inputs and preconditions. Inputs and preconditions are listed
- 70Execution cost. Instruction body is 4360 tokens
- 100Consistency. Name and required fields are in place
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 10 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)
- +3Description length 106: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- -2localhost URLs: will not work for another user
- +1No license
- +2Single-language instructions
- +4Structure: 51 headings
- +3Step-by-step instructions: 56 items
- +4Has examples (59 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 66.