AF defi-yield-optimizer
Professional DeFi yield farming optimizer for tracking and optimizing yields across multiple chains and protocols. Use when user needs to discover high-yield DeFi opportunities, track portfolio performance, calculate ROI, and manage yield farming strategies across Ethereum, Polygon, BSC, Arbitrum, Optimism, and other EVM chains.
As a process F 49/100 · Will not run — References files that are not bundled: references/yield-strategies.md, references/risk-scoring.md, references/gas-optimization.md
How to improve
- The text references files that are not there: add them or drop the references.
- 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 · 0
✓ No critical or high findings
Files scanned: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: references/yield-strategies.md - warning
missing-refreference to a missing file: references/risk-scoring.md - warning
missing-refreference to a missing file: references/gas-optimization.md - warning
missing-refreference to a missing file: references/rebalancing.md
Process rating: all ten parameters 49/100
- 0Tools and files. 4 referenced file(s) missing: references/yield-strategies.md, references/risk-scoring.md, references/gas-optimization.md
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 1 mutating operations with no state check
- 40Consistency. Frontmatter name (defi-yield-optimizer) differs from the folder (defi-yield-tracker)
- 50Failures and branches. 0 branches, has a failure section
- 60Result and completion. Output format stated, no completion criterion
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 88 steps
- 100Execution cost. Instruction body is 2115 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 16 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)
- +1No license
- +2Single-language instructions
- +3Description length 330: enough signal without eating the budget
- +4Structure: 47 headings
- +3Step-by-step instructions: 88 items
- +3Output format is stated explicitly
- +4Has examples (11 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 75.