market-analysis
Patterns for DeFi market analysis, screening, and comparison using DefiLlama MCP tools. Covers valuation ratios (P/S, P/F), growth screening with pct_change columns, multi-metric protocol comparison, category comparison, and cross-entity analysis. Use when users ask to compare protocols, screen for undervalued projects, analyze growth trends, or do sector analysis.
What this skill does
# DeFi Market Analysis ## Valuation Ratios Pre-computed in `defillama:get_protocol_metrics` and `defillama:get_category_metrics`: - `ps_ratio` = mcap / annualised revenue. Lower = potentially undervalued relative to revenue. - `pf_ratio` = mcap / annualised fees. Lower = more fee-efficient valuation. ## Growth Screening Use `*_pct_change` columns for momentum analysis. Values are **decimals** (0.35 = +35%, -0.13 = -13%). Available windows: `*_7d_pct_change`, `*_30d_pct_change`, `*_90d_pct_change` Metrics with pct_change: `tvl_base`, `fees_1d`, `revenue_1d`, `price`, `volume_dexs_1d` Sort by any pct_change column to find fastest movers. ## Protocol Comparison Use array params for side-by-side comparison in a single call: ``` defillama:get_protocol_metrics( protocol: ["aave", "compound-v3", "morpho"], metrics: ["tvl_base", "fees_1d", "revenue_1d", "ps_ratio"] ) ``` This returns one row per protocol, which is more efficient than calling once per protocol. ## Category Comparison Use `defillama:get_category_metrics` to compare DeFi sectors: ``` defillama:get_category_metrics( category: "Lending", metrics: ["tvl_base", "fees_1d", "protocol_count"] ) ``` Call once per category in parallel for side-by-side comparison. ## Token Sector Screening Use `defillama:get_token_prices` for token-level analysis: ``` defillama:get_token_prices(token: "coingecko:ethereum", period: "30d") ``` ## Historical Trends Use `period` for trend analysis: - Short-term: `7d` or `30d` - Medium-term: `90d` or `180d` - Long-term: `365d` - Custom range: `start_date` / `end_date` (YYYY-MM-DD) overrides `period` Historical queries return daily data points with a `date` column. ## Cross-Entity Analysis Compare across entity types using parallel tool calls: - "ETH price vs Ethereum TVL" -> `defillama:get_token_prices` + `defillama:get_chain_metrics` - "Aave TVL vs AAVE token price" -> `defillama:get_protocol_metrics` + `defillama:get_token_prices` - "Lending vs DEX category" -> two `defillama:get_category_metrics` calls in parallel ## Examples **Example 1:** User: "Most undervalued DeFi protocols by P/S ratio" Tool call: `defillama:get_protocol_metrics(sort_by: "ps_ratio asc", limit: 20, metrics: ["tvl_base", "revenue_1d", "ps_ratio", "mcap"])` **Example 2:** User: "Which protocols grew TVL most in last 30 days?" Tool call: `defillama:get_protocol_metrics(sort_by: "tvl_base_30d_pct_change desc", limit: 10, metrics: ["tvl_base", "tvl_base_30d_pct_change"])` **Example 3:** User: "Compare Aave and Compound fees" Tool call: `defillama:get_protocol_metrics(protocol: ["aave", "compound-v3"], metrics: ["tvl_base", "fees_1d", "revenue_1d"])` **Example 4:** User: "Compare Lending vs DEX fees and TVL" Tool call: `defillama:get_category_metrics(category: ["Lending", "DEX"], metrics: ["tvl_base", "fees_1d", "revenue_1d"])` **Example 5:** User: "Aave TVL trend over 90 days" Tool call: `defillama:get_protocol_metrics(protocol: "aave", metrics: ["tvl_base"], period: "90d")` **Example 6:** User: "Aave fees in Q1 2025" Tool call: `defillama:get_protocol_metrics(protocol: "aave", metrics: ["fees_1d"], start_date: "2025-01-01", end_date: "2025-03-31")`
Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".