api-and-interface-desi…
Guides stable API and interface design. Use when designing APIs, module boundaries, or any public interface. Use when creating REST or GraphQL endpoints,…
Deep-dive framework for analyzing crypto tokens — market data, liquidity health, tokenomics, unlock schedules, and risk assessment. Combines on-chain data, API queries, and multi-source validation to generate actionable investment verdicts.
$ npx -y skills add kevinnft/ai-agent-skills --skill crypto-token-analysis --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/crypto-token-analysisContext preview
The summary Claude sees to decide when to auto-load this skill.
Deep-dive framework for analyzing crypto tokens — market data, liquidity health, tokenomics, unlock schedules, and risk assessment. Combines on-chain data, API queries, and multi-source validation to generate actionable investment verdicts.
name: crypto-token-analysis description: Deep-dive framework for analyzing crypto tokens — market data, liquidity health, tokenomics, unlock schedules, and risk assessment. Combines on-chain data, API queries, and multi-source validation to generate actionable investment verdicts. tags: [crypto, token-analysis, defi, research, trading, airdrop, risk-assessment] origin: unknown source_license: see upstream language: en
Systematic approach for analyzing crypto tokens with focus on **profit opportunities** and **risk avoidance**. Used when user requests token analysis, investment research, or airdrop evaluation.
Use when: Token already listed on CoinGecko/CMC, has trading volume, circulating supply.
Use when: Analyzing for **airdrop potential**, product is live but no token yet, or token just launched with minimal data.
**Key difference:** Type B focuses on **product reality**, **user onboarding**, **VC backing**, and **airdrop signals** rather than liquidity metrics.
Use when: Analyzing **Decentralized Physical Infrastructure Networks** — projects requiring hardware (IoT devices, sensors, nodes, GPUs, wireless hotspots).
**Key difference:** Type C evaluates **hardware requirements**, **operator economics**, **network effects**, and **adoption barriers** unique to physical infrastructure.
Use when: Analyzing **NFT collections** on OpenSea, Blur, or other marketplaces — evaluating floor price trends, trading volume, holder distribution, and project status.
**Key difference:** Type D focuses on **floor price trends**, **volume/holder ratio**, **chart patterns** (pump & dump, death spiral), and **project abandonment signals** rather than tokenomics.
---
**Primary endpoint:**
curl -s "https://api.coingecko.com/api/v3/coins/{token_id}"**Key metrics to extract:**
**Critical calculation:**
vol_mcap_ratio = (volume_24h / market_cap) * 100 # Benchmarks: # Healthy: >10% # Acceptable: 3-10% # Weak: 1-3% # Dead: <1%
**Volume/MCap ratio is THE critical metric for exit risk.**
If ratio < 1%, token is **illiquid** regardless of other fundamentals.
**Slippage estimation (rough):**
**Supply breakdown:**
circulating_pct = (circulating_supply / total_supply) * 100 locked_pct = 100 - circulating_pct # Risk levels: # <20% locked: Low risk # 20-50% locked: Medium risk # 50-70% locked: High risk # >70% locked: Extreme risk (avoid)
**Unlock schedule:**
**For lending/DEX/yield protocols:**
# Revenue efficiency revenue_tvl_ratio = (annual_revenue / tvl) * 100 # Benchmarks (lending protocols): # Excellent: >2% # Good: 1-2% # Acceptable: 0.5-1% # Poor: <0.5% # Utilization rate utilization = (total_borrowed / total_supplied) * 100 # Healthy range: 40-80% # Too low (<30%): Dead capital # Too high (>90%): Liquidity risk
**TVL quality check:**
**Context matters:**
**Example comparison:**
# If analyzing token on Hyperliquid: hype_vol_mcap = 1.2% # Native token target_vol_mcap = 0.02% # Your token relative_health = target_vol_mcap / hype_vol_mcap # If <0.1 (10x worse), token is dying relative to ecosystem
**Use delegation for:**
**Red flags:**
---
**Use when:** Analyzing projects for airdrop potential (no token yet, or token just launched with minimal market data).
**What to extract:**
191 attribution-first agent skills for Hermes Agent, Claude Code, Cursor — one installer, 28 categories, searchable catalog. See NOTICE for upstream attribution.
Repo: kevinnft/ai-agent-skills
Guides stable API and interface design. Use when designing APIs, module boundaries, or any public interface. Use when creating REST or GraphQL endpoints,…
Tests in real browsers. Use when building or debugging anything that runs in a browser. Use when you need to inspect the DOM, capture console errors, analyze…
Automates CI/CD pipeline setup. Use when setting up or modifying build and deployment pipelines. Use when you need to automate quality gates, configure test…
Conducts multi-axis code review. Use before merging any change. Use when reviewing code written by yourself, another agent, or a human. Use when you need to…
Simplifies code for clarity. Use when refactoring code for clarity without changing behavior. Use when code works but is harder to read, maintain, or extend…
Optimizes agent context setup. Use when starting a new session, when agent output quality degrades, when switching between tasks, or when you need to configure…