protocol-deep-dive
Comprehensive single-protocol analysis combining TVL, fees, revenue, yields, events, income, and user activity. Produces a full protocol report. Use when the user asks for a complete overview, deep dive, "tell me everything about" a protocol, or a protocol research report.
What this skill does
# Protocol Deep Dive Perform a thorough analysis of a single DeFi protocol by combining multiple data sources into one structured report. ## Workflow ### Step 1 - Resolve the protocol entity If the protocol slug is unknown or ambiguous, resolve it first. ``` defillama:resolve_entity entity_type: "protocol" name: "<user-provided name>" ``` ### Step 2 - Core protocol metrics Fetch TVL, fees, revenue, market cap, ratios, and trend data. ``` defillama:get_protocol_metrics protocol: "<slug>" ``` Key fields to surface: `tvl_base`, `fees_1d`, `revenue_1d`, `mcap`, `ps_ratio`, `pf_ratio`, `tvl_base_7d_pct_change`, `tvl_base_30d_pct_change`. ### Step 3 - Top yield pools Retrieve the protocol's highest-TVL pools to show yield opportunities. ``` defillama:get_yield_pools protocol: "<slug>" ``` Highlight pools with the highest TVL and APY. Note any pools where the base APY is very low and rewards dominate (sustainability signal). ### Step 4 - Recent events Check for hacks, fundraises, or other notable events. ``` defillama:get_events protocol: "<slug>" event_type: "hacks" ``` Also check for fundraising activity: ``` defillama:get_events protocol: "<slug>" event_type: "raises" ``` ### Step 5 - Income statement Get the revenue breakdown to understand where income comes from. ``` defillama:get_income_statement protocol: "<slug>" ``` Use the `metric` param to filter by specific income line items if needed. ### Step 6 - User activity Fetch daily active users and transaction counts. ``` defillama:get_user_activity protocol: "<slug>" ``` ### Step 7 - Token price (if applicable) If the protocol has a native token, fetch current price context. ``` defillama:get_token_prices token: "<coingecko:token_id>" ``` ## Output Format Present the report with these sections in order: 1. **Overview** - One-paragraph summary: what the protocol does, which chain(s) it operates on, its category. 2. **Key Metrics** - Table of TVL, fees, revenue, mcap, P/S, P/F, and percentage changes (7d, 30d). 3. **Yield Opportunities** - Top 3-5 pools by TVL with chain, APY, and TVL. 4. **Revenue Breakdown** - Where income comes from (supply-side vs protocol). 5. **User Growth** - Active users trend, transaction volume. 6. **Recent Events** - Hacks, raises, governance events. 7. **Token Performance** - Price, market cap, volume, ATH distance. ## Tips - If `get_income_statement` returns no data, skip the Revenue Breakdown section rather than showing empty results. - Compare P/S and P/F ratios to category averages when possible. - Flag declining TVL + declining users as a bearish signal. - Flag growing TVL + growing users + growing revenue as strong fundamentals. - Use `start_date` / `end_date` for custom date ranges when analyzing specific periods.
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.