BB defi-yield-scout
Scan and compare DeFi yield farming opportunities for USDC stablecoins across Base and Arbitrum chains. Find the best APY rates, compare vault yields, and analyze historical performance using DeFiLlama data. Covers protocols used by n0ir autonomous yield agent: Morpho, Euler v2, Aave v3, Compound v3, Moonwell, Silo v2, Lazy Summer, Harvest Finance, 40 Acres, Wasabi, Yo Protocol. Use for yield farming comparison, stablecoin returns, USDC rates, vault APY ranking, breakeven analysis between vaults, APY trend history, protocol risk overview, DeFi yield optimization, best stablecoin yields on Base, best USDC yields on Arbitrum, n0ir vault strategy, ERC-4626 vault comparison, yield aggregator analysis, TVL-weighted yield ranking, cross-chain yield comparison, gas-adjusted net returns.
As a process B 65/100 · Nearly there — weak spots: when it triggers, inputs and preconditions, progress reporting
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The skill asks for more than the task needs: broad tool access, credential environment variables, binaries. Every extra permission widens the damage from a mistake or a compromise.
Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.
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 · 4
✓ No critical or high findings
Medium and low: 4
-
medium Broad scope
meta-broad-allowed-toolsSKILL.md:1Broad tool permissions pre-approved: Bashallowed-tools: Read Bash Glob
-
low Secrets in code
secret-high-entropy-tokenreferences/protocols.md:111High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)- **USDC address:** `0x83…913` (native Circle USDC)
quoted -
low Secrets in code
secret-high-entropy-tokenreferences/protocols.md:116High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)- **USDC address (native):** `0xaf…831`
quoted -
low Secrets in code
secret-high-entropy-tokenreferences/protocols.md:117High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)- **USDC.e address (bridged):** `0xFF…CC8`
quoted
Files scanned: 4. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 2, column 14: description: Scan and compare DeFi yield farming opportunities for USDC stablec… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value
Process rating: all ten parameters 65/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 55Failures and branches. 1 branches
- 60Result and completion. Output format stated, no completion criterion
- 85Steps. 20 steps, 1 vague phrases
- 100Tools and files. Tools declared in frontmatter
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1151 tokens
- 100Running it twice. No mutating operations
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)
- +1No license
- +2Single-language instructions
- +3Description length 790: enough signal without eating the budget
- +4Structure: 10 headings
- +3Step-by-step instructions: 20 items
- +3Output format is stated explicitly
- +4Has examples (5 code blocks)
- +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: 84.