AC trust-escrow
Create and manage USDC escrows for agent-to-agent payments on Base Sepolia. 30% gas savings, batch operations, dispute resolution.
Create and manage USDC escrows for agent-to-agent payments on Base Sepolia.
As a process C 53/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
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 · 5
✓ No critical or high findings
Medium and low: 5
-
low Secrets in code
secret-high-entropy-tokenSKILL.md:25High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)- **Address:** `0x63…D64`
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)- **USDC:** `0x03…F7e`
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:47High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)address: '0x63…D64',
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:213High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)const ESCROW_ADDRESS = '0x63…D64';
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:214High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)const USDC_ADDRESS = '0x03…F7e';
quoted
Files scanned: 1. 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 53/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
- 100Tools and files. No external tools needed
- 100Steps. 29 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1820 tokens
- 100Running it twice. Mutating operations check current state
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- 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
- -212 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +3Description length 130: enough signal without eating the budget
- +4Structure: 23 headings
- +3Step-by-step instructions: 29 items
- +4Has examples (11 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 82.