AC defi-stablecoin-yield-scanner
Scan live stablecoin yields across every major DeFi protocol and chain — Ethereum, Base, Arbitrum, Optimism, Polygon, Avalanche, and more — using the free DeFiLlama pools API (no API key required). Built for crypto and DeFi users hunting the best USDC, USDT, DAI, and other stablecoin APY without directional trading risk. Filters by minimum TVL to screen out low-liquidity rug risk, filters by APY range to catch unsustainable reward-emission traps, and can scope results to a single chain. Useful for passive income, yield farming, treasury management, and whale-style capital allocation across DeFi protocols like Aave, Pendle, Curve, and Morpho. Complements trading and options skills by covering the non-directional yield side of crypto.
Scan live stablecoin yields across every major DeFi protocol and chain — Ethereum, Base, Arbitrum, Optimism, Polygon, Avalanche, and more — using the free…
As a process C 60/100 · Has gaps — weak spots: when it triggers, inputs and preconditions, failures and branches
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 · 1
✓ No critical or high findings
Medium and low: 1
-
medium Broad scope
meta-broad-allowed-toolsSKILL.md:1Broad tool permissions pre-approved: Bashallowed-tools: Bash
Files scanned: 0. 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 60/100
- 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
- 60Result and completion. Output format stated, no completion criterion
- 85Steps. 8 steps, 1 vague phrases
- 100Tools and files. Tools declared in frontmatter
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 492 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 742: enough signal without eating the budget
- +4Structure: 5 headings
- +3Step-by-step instructions: 8 items
- +3Output format is stated explicitly
- +4Has examples (1 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 87.