AB create-test-pool
Deploy a custom Uniswap pool on the local testnet with configurable parameters. Create pools with specific conditions (thin liquidity, wide spreads, exact tick ranges) to test agent behavior under controlled scenarios. Requires a running local testnet.
As a process B 73/100 · Nearly there — weak spots: result and completion, inputs and preconditions
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 · 3
✓ No critical or high findings
Medium and low: 3
-
low Secrets in code
secret-high-entropy-tokenSKILL.md:89High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)If the pool requires tokens the deployer might not have, call `mcp__uniswap__fund_test_account` first to ensure the deployer (account #1: `0xf3…266`) has sufficient t
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:108High-entropy token-like string (may be an id, hash or a credential)Token0: USDC 0xA0…B48 (6 decimals)
-
low Secrets in code
secret-high-entropy-tokenSKILL.md:109High-entropy token-like string (may be an id, hash or a credential)Token1: WETH 0xC0…Cc2 (18 decimals)
Files scanned: 3. 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 73/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 85Steps. 29 steps, 2 vague phrases
- 100Tools and files. Tools declared in frontmatter
- 100When it triggers. States when to use and when not to
- 100Failures and branches. 3 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1722 tokens
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
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
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 252: enough signal without eating the budget
- +4Structure: 13 headings
- +3Step-by-step instructions: 29 items
- +4Has examples (3 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 88.