agentleFS
JerryLiu369JerryLiu369/awesome-quant-skills/skills/crypto-web3/defillama-yields/SKILL.md

defillama-yields

Skill3 starsChanged 34 days agoMITView on GitHub

APY values are already percentages: apy = 2.32 means 2.32%. Do NOT multiply by 100. This is the most common mistake when working with yield data. The token param expects canonical token keys (e.g., coingecko:ethereum) and uses dim.pool_set() for family resolution. coingecko:ethereum finds pools containing ETH, wETH, stETH, cbETH, and all other variants in the ETH family -- not just native ETH. sort_by accepts strings like: "apy desc", "tvl desc", "apy_base desc", "apy_reward desc" Each result includes: symbol, protocol (sub-protocol…

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 2 are distinctive, and 4 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.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Do NOT multiply by 100. This is the most common mistake when working with yield data.

    line 18
  2. Very specific:

    Use period param (7d, 30d, 90d, 180d, 365d) for daily APY/TVL time-series history

    line 54
  3. Very specific:

    Use include_volatility: true to add APY volatility stats (apy_avg_30d, apy_median_30d, apy_std_30d, cv_30d) — current queries only

    line 55
  4. Very specific:

    Use start_date / end_date for custom date ranges (overrides period)

    line 56
  5. Very specific:

    Use include_borrow: true to ensure borrow columns are populated.

    line 66
  6. Distinctive:

    When allocating capital, check pool TVL.

    line 70

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
<!-- Imported from: https://github.com/DefiLlama/defillama-skills Source Path: yield-strategies/SKILL.md Curated for awesome-quant-skills -->

name: yield-strategies description: Guide for querying DeFi yield and APY data using get_yield_pools. Covers pool filtering by token, chain, protocol, category, stablecoin-only mode, and capacity assessment. Explains APY conventions, lending vs borrowing rates, and sort options. Use when users ask about yields, APY, lending rates, borrowing costs, best pools, or DeFi yield strategies.

DeFi Yield Strategies

APY Convention

APY values are already percentages: apy = 2.32 means 2.32%.

Do NOT multiply by 100. This is the most common mistake when working with yield data.

Tool: defillama:get_yield_pools

Filtering Guide

WantParameterExample
Pools with specific tokentoken"coingecko:ethereum"
Pools on specific chainchain"ethereum"
Pools from specific protocolprotocol"aave"
Pools from protocol categorycategory"Lending", "DEXes"
Only stablecoin poolsstablecoin_onlytrue
Minimum APY thresholdmin_apy5 (= 5%)
Minimum TVLmin_tvl1000000 (= $1M)
Include borrow-side datainclude_borrowtrue

Key Distinction

  • "ETH pools" = token filter: token: "coingecko:ethereum"
  • "Pools on Ethereum" = chain filter: chain: "ethereum"

Token Family Matching

The token param expects canonical token keys (e.g., coingecko:ethereum) and uses dim.pool_set() for family resolution. coingecko:ethereum finds pools containing ETH, wETH, stETH, cbETH, and all other variants in the ETH family -- not just native ETH.

Sort Options

sort_by accepts strings like: "apy desc", "tvl desc", "apy_base desc", "apy_reward desc"

Returned Columns

Each result includes: symbol, protocol (sub-protocol slug), parent_protocol, category, chain, apy, apy_base, apy_reward, apy_base_borrow, apy_reward_borrow, tvl, total_supply, total_borrow

Historical Data & Volatility

  • Use period param (7d, 30d, 90d, 180d, 365d) for daily APY/TVL time-series history
  • Use include_volatility: true to add APY volatility stats (apy_avg_30d, apy_median_30d, apy_std_30d, cv_30d) — current queries only
  • Use start_date / end_date for custom date ranges (overrides period)

Borrowing Costs

For lending protocols, borrowing rate data is available:

  • apy_base_borrow: Base borrowing cost (what you pay)
  • apy_reward_borrow: Reward offset on borrowing (incentives you earn)
  • Net borrow cost = apy_base_borrow - apy_reward_borrow

Use include_borrow: true to ensure borrow columns are populated.

Capacity Assessment

When allocating capital, check pool TVL. Allocating more than 10% of a pool's TVL may cause significant rate impact or slippage. Larger pools absorb capital more easily.

Examples

Example 1: User: "Best stablecoin lending yields" Tool call: defillama:get_yield_pools(stablecoin_only: true, category: "Lending", sort_by: "apy desc")

Example 2: User: "Top ETH yield pools with over $1M TVL" Tool call: defillama:get_yield_pools(token: "coingecko:ethereum", min_tvl: 1000000, sort_by: "apy desc")

Example 3: User: "Cheapest borrowing rates for stablecoins on Arbitrum" Tool call: defillama:get_yield_pools(stablecoin_only: true, chain: "arbitrum", category: "Lending", include_borrow: true, sort_by: "apy_base_borrow asc")

Example 4: User: "Where can I earn yield on USDC?" Tool call: defillama:get_yield_pools(token: "coingecko:usd-coin", sort_by: "apy desc", min_tvl: 100000)

Example 5: User: "Aave yields on Ethereum" Tool call: defillama:get_yield_pools(protocol: "aave", chain: "ethereum", sort_by: "apy desc")

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.