Agent skill · Data & Analytics

llama-analyst

DeFi fundamentals and cross-chain analytics using DefiLlama-style data. Use when you want to find undervalued protocols, screen by TVL/revenue growth vs token price, compare sectors, or run data-driven crypto research beyond pure memes.

majiayu000github.com/majiayu000GitHub ↗
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill llama-analyst-dreamineering-meme-times-2 --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 11 KB
Bundled scripts: none
Path: skills/analysis/llama-analyst-dreamineering-meme-times-2/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Llama Analyst - Fundamentals & Data-Driven Crypto Research Inspired by tools like LlamaAI (Dynamo DeFi walkthrough), this skill focuses on **systematic, data-first crypto investing** instead of pure narrative or meme trading. ## Activation Triggers Use this skill when: - You ask for **undervalued protocols** or tokens with: - Growing TVL or revenue - Flat or declining token price - You want **sector or protocol screens**, such as: - Top DEXs by revenue/TVL - Perps with fastest revenue growth - Chains with rising DeFi inflows - You request **macro DeFi analytics**: - Flows of SOL/BTC/ETH into DeFi over time - Comparing ecosystems (Solana vs Ethereum vs L2s) - Yield pool scans by APR, risk, and stickiness - You need **data-backed theses**, not just narratives. ## Core Capabilities ### 1. Protocol Screening & Ranking - Screen protocols by combinations of: - TVL level and TVL growth (absolute and %) - Revenue and revenue growth - Revenue efficiency (revenue / TVL) - Token price performance vs fundamentals - Identify: - Protocols with **rising TVL/revenue but lagging price** - Protocols with strong fundamentals but low narrative attention - Overheated names (price up much more than fu

What's inside
Steps it walks through
  1. Activation Triggers
  2. Core Capabilities
  3. 1. Protocol Screening & Ranking
  4. 2. Sector & Ecosystem Analytics
  5. 3. Flow & Macro Views
  6. 4. Output Formatting
  7. Example Queries This Skill Should Own
  8. Integration with Existing Agents
  9. Safety & Quality Gates
  10. Predictive Analytics Framework
  11. 1. TVL Momentum Prediction
  12. 2. Revenue-to-Price Divergence Detector
  13. 3. Sector Rotation Predictor
  14. 4. Protocol Health Score (ML-Generated)
Ships with 1 file
  • metadata.json
Commands it runs
Find undervalued protocols (ML divergence detector)
npx tsx .claude/skills/llama-analyst/scripts/screener.ts \
Predict sector rotation
Protocol health ranking
TVL momentum detection
Get protocol health score
npx tsx .claude/skills/llama-analyst/scripts/health-score.ts \
Run divergence analysis
npx tsx .claude/skills/llama-analyst/scripts/divergence.ts \
Sector rotation analysis
More from claude-skill-registry
All skills →
About this skill
What does the llama-analyst skill do?

DeFi fundamentals and cross-chain analytics using DefiLlama-style data. Use when you want to find undervalued protocols, screen by TVL/revenue growth vs token price, compare sectors, or run data-driven crypto research beyond pure memes.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill llama-analyst-dreamineering-meme-times-2 --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going