$npx -y skills add tokenomist-ai/tokenomist-cli --skill tokenomist-unlock-analysisAnalyze token unlock events — upcoming unlocks, historical events, and allocation breakdowns. Use when checking unlock impact on market cap or reviewing unlock schedules.
| 1 | # Skill: Unlock Analysis |
| 2 | |
| 3 | Analyze token unlock events — upcoming unlocks, historical events, and allocation breakdowns. |
| 4 | |
| 5 | ## When to use |
| 6 | |
| 7 | When you need to check upcoming token unlocks, assess unlock impact on market cap, or review historical unlock events for a specific token. |
| 8 | |
| 9 | ## Commands |
| 10 | |
| 11 | ### List all unlock events (grouped by token) |
| 12 | ```bash |
| 13 | tok unlock list --output json |
| 14 | ``` |
| 15 | |
| 16 | Options: |
| 17 | | Option | Description | |
| 18 | |--------|-------------| |
| 19 | | `--min-market-cap <value>` | Minimum market cap | |
| 20 | | `--min-released-percentage <value>` | Minimum released percentage | |
| 21 | | `--min-unlock-date <date>` | Min unlock date (YYYY-MM-DD) | |
| 22 | | `--max-unlock-date <date>` | Max unlock date (YYYY-MM-DD) | |
| 23 | | `--min-total-unlock-amount <value>` | Minimum total unlock amount | |
| 24 | | `--min-value-to-market-cap <value>` | Min value-to-market-cap ratio | |
| 25 | | `--standard-allocation <names>` | Filter by allocation (comma-separated) | |
| 26 | | `--page <number>` | Page number | |
| 27 | | `--page-size <number>` | Items per page | |
| 28 | |
| 29 | ```bash |
| 30 | tok unlock list --min-market-cap 1000000 --min-unlock-date 2025-01-01 --max-unlock-date 2025-12-31 |
| 31 | tok unlock list --min-value-to-market-cap 0.01 --standard-allocation "privateInvestors,founderTeam" |
| 32 | ``` |
| 33 | |
| 34 | Available `--standard-allocation` values: `community`, `founderTeam`, `privateInvestors`, `publicInvestors`, `others`, `reserve` (comma-separated for multiple). |
| 35 | |
| 36 | ### Get upcoming unlocks (next event per token) |
| 37 | ```bash |
| 38 | tok unlock upcoming --output json |
| 39 | ``` |
| 40 | |
| 41 | Options: |
| 42 | | Option | Description | |
| 43 | |--------|-------------| |
| 44 | | `--start <date>` | Start date (YYYY-MM-DD) | |
| 45 | | `--end <date>` | End date (YYYY-MM-DD) | |
| 46 | | `--standard-allocation <names>` | Filter by allocation (comma-separated) | |
| 47 | | `--min-market-cap <value>` | Minimum market cap | |
| 48 | | `--min-released-percentage <value>` | Minimum released percentage | |
| 49 | | `--min-total-unlock-amount <value>` | Minimum total unlock amount | |
| 50 | | `--min-value-to-market-cap <value>` | Min value-to-market-cap ratio | |
| 51 | | `--page <number>` | Page number | |
| 52 | | `--page-size <number>` | Items per page | |
| 53 | |
| 54 | ```bash |
| 55 | tok unlock upcoming --min-market-cap 5000000 --min-value-to-market-cap 0.01 --output json |
| 56 | ``` |
| 57 | |
| 58 | ### Get unlock events for a specific token |
| 59 | ```bash |
| 60 | tok unlock events <tokenId> --output json |
| 61 | ``` |
| 62 | |
| 63 | Options: |
| 64 | | Option | Description | |
| 65 | |--------|-------------| |
| 66 | | `--start <date>` | Start date (YYYY-MM-DD) | |
| 67 | | `--end <date>` | End date (YYYY-MM-DD) | |
| 68 | | `--standard-allocation <names>` | Filter by allocation (comma-separated) | |
| 69 | | `--page <number>` | Page number | |
| 70 | | `--page-size <number>` | Items per page | |
| 71 | |
| 72 | ```bash |
| 73 | tok unlock events solana --start 2025-01-01 --end 2025-12-31 --output json |
| 74 | ``` |
| 75 | |
| 76 | ## Key output fields |
| 77 | |
| 78 | **unlock list / upcoming:** |
| 79 | - `tokenName`, `tokenSymbol` — token identification |
| 80 | - `marketCap` — current market cap |
| 81 | - `releasedPercentage` — how much of total supply has been released |
| 82 | |
| 83 | **unlock events:** |
| 84 | - `unlockDate` — when the unlock happens |
| 85 | - `cliffUnlocks.cliffAmount` — number of tokens unlocking |
| 86 | - `cliffUnlocks.cliffValue` — USD value of the unlock |
| 87 | - `cliffUnlocks.valueToMarketCap` — unlock value as % of market cap |
| 88 | - `cliffUnlocks.allocationBreakdown` — which allocations are unlocking |
| 89 | |
| 90 | ## Analysis workflow |
| 91 | |
| 92 | 1. Run `tok unlock upcoming --output json` to find tokens with large upcoming unlocks |
| 93 | 2. Filter by `valueToMarketCap` to identify potentially market-moving events |
| 94 | 3. Drill into specific tokens with `tok unlock events <id> --output json` |
| 95 | 4. Check allocation breakdown to understand who is receiving tokens (investors, team, community, etc.) |
| 96 | |
| 97 | ## Domain Context |
| 98 | |
| 99 | - **Unlocked does not mean circulating.** Tokenomist tracks release schedules (when tokens become available), not on-chain transfers. Tokens can be unlocked but still held by the team, locked in DeFi, or otherwise not on the open market. |
| 100 | - Schedules may include assumptions — the allocation breakdown can help assess confidence in the schedule. |
| 101 | - `valueToMarketCap` is a key metric: unlocks representing >1% of market cap may be market-moving events. |
| 102 | |
| 103 | ## Workflow |
| 104 | |
| 105 | - Use `tok token list --output json` first to find the token ID if you don't know it. |
| 106 | - Chain with `tok emission daily <id>` for a complete unlock + emission picture. |
| 107 | - Cross-reference with `tok allocation detail <id>` to understand which groups (team, investors, community) are unlocking. |
| 108 | - Use `tok fundraising detail <id>` to see what price investors paid — compare with current price to assess sell pressure. |
| 109 | |
| 110 | ## Output Size |
| 111 | |
| 112 | The `unlock list` command can return hundreds of events. Use date and market cap filters to n |