AC spraay-gateway
Access the Spraay x402 payment gateway — batch stablecoin payments (up to 200 recipients per transaction, ~80% gas savings), escrow, payroll, robot task payments, and 190 endpoints across 15 chains. Use this skill whenever the user wants to send batch payments, pay multiple wallets at once, run crypto payroll, create escrow, price/validate a payout, check token prices or chain status, or interact with any Spraay Gateway endpoint. Works in free mode with no credentials; paid endpoints unlock with a Spraay subscription API key (external paid service, from $29/mo) or per-call x402 payment from a funded wallet.
Access the Spraay x402 payment gateway — batch stablecoin payments (up to 200 recipients per transaction, ~80% gas savings), escrow, payroll, robot task…
As a process C 57/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 Exfiltration
net-credential-usereferences/endpoints.md:86Credential used in a network call (verify the destination is the intended service) (the skill's own vendor host)curl -sS -H "X-API-Key: $SPRAAY_API_KEY" "https://gateway.spraay.app/api/v1/usage"
vendor-host -
low Secrets in code
secret-high-entropy-tokenreferences/endpoints.md:92High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)- Spraay batch contract (Base): `0x16…eEC`
quoted
Files scanned: 4. 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 57/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 6 mutating operations with no state check
- 55Failures and branches. 1 branches
- 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
- 70When it triggers. States when to use, but not when not to
- 100Steps. 22 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1809 tokens
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +3Description length 614: enough signal without eating the budget
- +4Structure: 8 headings
- +3Step-by-step instructions: 22 items
- +4Reference files are cited in the instructions (1 of 1)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 87.