crypto-unlocks-cachelisted

# Crypto Unlocks Cache Skill ## When to use - "Refresh crypto unlocks" / "update unlock cache" - Before sizing any alt-coin long where a vesting cliff could land inside the doctrine §5 48h window - After running the `crypto-unlocks` (WebFetch) skill — pipe the answer into `set` - Audit: "Show me crypto unlock cache" / "Which watchlist coins are missing entries?" Do NOT use for: - Per-coin price / RSI / ATR — that's `dashboard` (Binance klines + CoinGecko OHLC fallback) - Live tokenomist.ai data — that's the agent-only `crypto-unlocks` WebFetch skill - Crypto sentiment / Fear & Greed — that's `crypto-coingecko regime` ## Why this exists AGENTS.md §5 hard rule: **"Crypto: 48h before a scheduled token unlock > 1% of float"** — no new directional exposure. Tokenomist.ai is the canonical unlock data source, but it's a Next.js SPA — page HTML is mostly empty, all data fetches happen client-side. Direct `urllib`/`requests` scraping returns no usable JSON. DeFiLlama emissions API moved behind a paid plan (HTTP 402). CoinGecko/CryptoRank don't expose unlock schedules on their free tiers. Result: there is no scrape-friendly source for cliff-unlock dates. This skill solves it by maintaining the cache as a human/agent-curated JSON store. The dashboard reads it on build and runs a real §5 gate instead of a manual-check warn. ## What gets cached per coin `.claude/cache/crypto_unlocks/{COIN}.json`: ```json { "coin": "HYPE", "source": "tokenomist.ai/hyperliquid", "_source_typ