BC spraay-payments
Send batch crypto payments and payroll through the Spraay x402 gateway. Supports Base, Ethereum, Arbitrum, Polygon, BNB Chain, Avalanche, Unichain, and more. Use when the user asks to send a batch payment with Spraay, run crypto payroll through Spraay, create a Spraay invoice, check token balances via the Spraay gateway, look up token prices, or resolve ENS/Basename addresses through Spraay.
Send batch crypto payments and payroll through the Spraay x402 gateway.
As a process C 62/100 · Has gaps — weak spots: result and completion, inputs and preconditions, 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 · 2
✓ No critical or high findings
Medium and low: 2
-
low Secrets in code
secret-high-entropy-tokenSKILL.md:126High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)Payment contract (Base): `0x16…eEC`
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:199High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)const SPRAAY = "0x16…eEC"; // Base
quoted
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 62/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 12 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 70When it triggers. States when to use, but not when not to
- 100Tools and files. No external tools needed
- 100Steps. 42 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3695 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 12 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 394: enough signal without eating the budget
- +4Structure: 20 headings
- +3Step-by-step instructions: 42 items
- +4Has examples (10 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 83.