AC fund-wallet
Add funds to the wallet. Use when you or the user want to fund, deposit, top up, load, add funds, onramp, buy crypto, or get tokens into the wallet. Also use when the wallet has insufficient balance for a send, swap, or DeFi operation, or when someone asks "how do I get funds?" or "how do I add money?".
As a process C 64/100 · Has gaps — weak spots: result and completion, when it triggers, running it twice
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 · 0
✓ No critical or high findings
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 64/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
- 55Failures and branches. 1 branches
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Tools and files. Tools declared in frontmatter
- 100Steps. 13 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 702 tokens
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
- +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
- +5Description quotes 2 example trigger phrases
- +3Description length 304: enough signal without eating the budget
- +4Structure: 10 headings
- +3Step-by-step instructions: 13 items
- +4Has examples (4 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 89.