agentleFS
SperaxSperax/sperax-skills/skills/defi-yield-strategies/SKILL.md

defi-yield-strategies

Skill8 starsChanged 9 months agoMITView on GitHub

Comprehensive guide to DeFi yield farming strategies — lending, liquidity provision, auto-compounding, stablecoin yield, and risk management. Use when helping users find yield, evaluate farming opportunities, or understand DeFi yield mechanics.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When recommending yield strategies:

    line 126
  2. Distinctive:

    Check TVL and audit status: before recommending protocols

    line 128

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

DeFi Yield Strategies Guide

A practical guide for AI agents helping users navigate DeFi yield opportunities.

Yield Sources in DeFi

1. Lending (Supply-Side)

Deposit tokens into lending protocols, earn interest from borrowers.

ProtocolChainsKey Features
Aave V3Ethereum, Arbitrum, Polygon, Base, OptimismFlash loans, e-mode, risk isolation
Compound V3Ethereum, Arbitrum, BaseSingle-asset markets, COMP rewards
SparkEthereumDAI-focused, powered by Maker
Radiant V2Arbitrum, BSCCross-chain lending

Typical APYs: 1–8% for stablecoins, variable for volatile assets

Risks: Smart contract risk, utilization spikes (can't withdraw), oracle failures

2. Liquidity Provision (DEX)

Provide trading liquidity and earn fees from swaps.

Full-Range (V2-style):

  • Provide both tokens in a 50/50 ratio
  • Earn fees on all trades in the pool
  • Subject to impermanent loss

Concentrated (V3-style):

  • Choose a price range for your liquidity
  • Higher capital efficiency = more fees per dollar
  • Higher IL risk if price moves out of range
  • Requires active management

DEXs: Uniswap V3, Camelot, Curve, Balancer

3. Auto-Yield Stablecoins

Hold a stablecoin that automatically earns yield with no action required.

  • USDs by Sperax: Auto-rebasing stablecoin on Arbitrum. Backed by USDC/USDT, yield from Aave/Compound/Curve. 70% of yield goes to holders. Just hold it — yield is automatic.
  • sDAI by Maker: DAI deposited into Maker's DSR

4. Liquidity Farming (Extra Rewards)

Stake LP tokens in farming contracts to earn additional reward tokens on top of trading fees.

  • Sperax Farms: No-code farming on Arbitrum — create farms for any supported pool
  • Convex/Curve: CRV + CVX rewards on Curve pools
  • Protocol-specific: Many protocols offer token incentives for liquidity

5. Vault Strategies (Auto-Compounding)

Deposit into vaults that automatically compound rewards.

ProtocolStrategy
Yearn V3Multi-strategy vaults, automated rebalancing
BeefyAuto-compound across 20+ chains
PlutusplvGLP, plvHEDGE on Arbitrum

Risk Framework

Risk Tiers

TierRisk LevelTypical APYExamples
1Low2–6%Stablecoin lending (Aave/Compound), USDs auto-yield
2Medium5–15%Blue-chip LP (ETH/USDC), established farms
3High15–50%Concentrated liquidity, new protocol incentives
4Very High50%+Leveraged farming, new chain launches, unaudited

Key Risk Factors

  1. Smart contract risk: Is the protocol audited? How long has it been live?
  2. Impermanent loss: For LP positions, how volatile is the pair?
  3. Liquidation risk: For leveraged positions, what's the health factor?
  4. Protocol risk: How decentralized is governance? Multisig setup?
  5. Yield sustainability: Where does the yield come from? Is it from real revenue or token emissions?

Red Flags

  • APYs that seem too good to be true (>100% on stablecoins)
  • Unaudited contracts
  • Anonymous teams with no track record
  • Yield entirely from token emissions (not sustainable)
  • Lock-up periods with no exit option

Strategy Examples

Conservative: Stablecoin Yield Stack

  1. Hold USDs on Arbitrum (auto-yield, ~3–8% APY)
  2. Supply USDC to Aave V3 on Arbitrum (~2–5% APY)
  3. Diversify across 2–3 lending protocols

Target: 3–7% blended APY with minimal risk

Moderate: LP + Farming

  1. Provide USDs/USDC liquidity on Uniswap V3 (tight range)
  2. Stake LP in Sperax Farms for additional rewards
  3. Auto-compound with a vault strategy

Target: 8–15% APY with moderate IL risk

Aggressive: Multi-Protocol Optimization

  1. Supply ETH to Aave → borrow stablecoins
  2. Mint USDs with borrowed stables
  3. Provide USDs/ETH liquidity
  4. Farm rewards → compound

Target: 15–30%+ APY with leverage and IL risk

Agent Tips

When recommending yield strategies:

  1. Always assess risk tolerance first — don't recommend aggressive strategies to beginners
  2. Check TVL and audit status before recommending protocols
  3. Explain IL for any LP recommendation
  4. Sustainable yield > high APY — prefer real yield (fees, lending interest) over pure emissions
  5. Diversification — never put everything in one protocol

Links

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.