BC usdc-escrow
Trustless USDC escrow for agent-to-agent payments on Base. Create, release, dispute escrows via simple commands.
Trustless USDC escrow for agent-to-agent payments on Base.
As a process C 51/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
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 · 6
✓ No critical or high findings
Medium and low: 6
-
low Secrets in code
secret-high-entropy-tokenreferences/api-docs.md:22High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"beneficiary": "0x74…D28",
quoted -
low Secrets in code
secret-high-entropy-tokenreferences/api-docs.md:50High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"beneficiary": "0x74…D28",
quoted -
low Secrets in code
secret-high-entropy-tokenreferences/api-docs.md:373High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)- **Escrow Contract:** [`0x2a…E04`](https://sepolia.basescan.org/address/0x2a…e04) (verified)
quoted -
low Secrets in code
secret-high-entropy-tokenreferences/api-docs.md:374High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)- **USDC Contract:** [`0x03…F7e`](https://sepolia.basescan.org/address/0x03…F7e)
detector -
low Secrets in code
secret-high-entropy-tokenscripts/create-escrow.sh:9High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)echo "Example: $0 0x74…D28 10 'Payment for service' 48"
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:27High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)Example: `./scripts/create-escrow.sh 0x74…D28 10 "Payment for data analysis" 48`
quoted
Files scanned: 9. 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")
Process rating: all ten parameters 51/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 7 mutating operations with no state check
- 100Tools and files. No external tools needed
- 100Steps. 12 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 578 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
- +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 112: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +4Structure: 14 headings
- +3Step-by-step instructions: 12 items
- +4Has examples (7 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
- +3All 7 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 76.