BF spraay-compute
Pay-per-call GPU rental and AI inference (LLM, image, video, TTS, STT, embeddings) via Spraay x402 gateway. USDC micropayments on Base/Solana. Prepaid compute-futures with bulk discounts up to 15%. Keyless, agent-native — no API keys, no signup.
Pay-per-call GPU rental and AI inference (LLM, image, video, TTS, STT, embeddings) via Spraay x402 gateway.
As a process F 44/100 · Will not run — References files that are not bundled: references/endpoints.md, examples/quickstart.md
How to improve
- The text references files that are not there: add them or drop the references.
- 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 · 1
✓ No critical or high findings
Medium and low: 1
-
low Secrets in code
secret-high-entropy-tokenSKILL.md:20High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)Everything settles in **USDC over x402 V2** on **Base mainnet** and **Solana mainnet**. The gateway returns a standard HTTP `402 Payment Required` with payment requirements; the agent pays via its x40
quoted
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: references/endpoints.md - warning
missing-refreference to a missing file: examples/quickstart.md
Process rating: all ten parameters 44/100
- 0Tools and files. 2 referenced file(s) missing: references/endpoints.md, examples/quickstart.md
- 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. 11 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
- 100Steps. 28 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3091 tokens
- 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)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 245: enough signal without eating the budget
- +4Structure: 13 headings
- +3Step-by-step instructions: 28 items
- +4Has examples (3 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 75.