$npx -y skills add tokenomist-ai/tokenomist-cli --skill tokenomist-allocation-breakdownGet the full allocation distribution for a token — who owns what and how much is locked vs unlocked. Use when analyzing supply distribution across team, investors, community, etc.
| 1 | # Skill: Allocation Breakdown |
| 2 | |
| 3 | Get the full allocation distribution for a token — who owns what and how much is locked vs unlocked. |
| 4 | |
| 5 | ## When to use |
| 6 | |
| 7 | When you need to understand a token's supply distribution across allocations (team, investors, community, ecosystem, etc.). |
| 8 | |
| 9 | ## Command |
| 10 | |
| 11 | ```bash |
| 12 | tok allocation detail <tokenId> --output json |
| 13 | ``` |
| 14 | |
| 15 | ## Example |
| 16 | |
| 17 | ```bash |
| 18 | tok allocation detail solana --output json |
| 19 | ``` |
| 20 | |
| 21 | ## Key output fields |
| 22 | |
| 23 | **Top-level:** |
| 24 | - `name`, `symbol` — token identification |
| 25 | - `maxSupply` — maximum token supply (null if unlimited) |
| 26 | - `totalUnlockedAmount` — total tokens currently unlocked |
| 27 | - `totalLockedAmount` — total tokens still locked |
| 28 | - `totalUntrackedAmount` — tokens not tracked by Tokenomist |
| 29 | - `totalTBDLockedAmount` — tokens locked with no defined unlock schedule |
| 30 | |
| 31 | **Per allocation (`allocations[]`):** |
| 32 | - `allocationName` — project-specific allocation name |
| 33 | - `standardAllocationName` — Tokenomist's standardized category (comparable across projects) |
| 34 | - `allocationType` — allocation classification |
| 35 | - `allocationAmount` — total tokens in this allocation |
| 36 | - `allocationUnlockedAmount` — tokens unlocked from this allocation |
| 37 | - `allocationLockedAmount` — tokens still locked in this allocation |
| 38 | - `trackedAllocationPercentage` — % of total tracked supply |
| 39 | |
| 40 | ## Analysis workflow |
| 41 | |
| 42 | 1. Get allocation: `tok allocation detail <id> --output json` |
| 43 | 2. Check `totalLockedAmount` vs `totalUnlockedAmount` for overall supply status |
| 44 | 3. Look at individual allocations — high locked amounts in "Investor" or "Team" allocations signal future sell pressure |
| 45 | 4. Compare `standardAllocationName` across different tokens for apples-to-apples comparison |
| 46 | 5. Cross-reference with `tok unlock upcoming` to see when locked tokens will release |
| 47 | |
| 48 | ## Domain Context |
| 49 | |
| 50 | - Allocations are **point-in-time analyses**. They reflect the current understanding of token distribution and may be updated as new information becomes available. |
| 51 | - `standardAllocationName` enables cross-project comparison — different projects may use different names for similar allocations (e.g., "Core Contributors" vs "Team"), but the standard name normalizes this. |
| 52 | - `totalTBDLockedAmount` represents tokens that are known to be locked but have no defined unlock schedule. Their classification may change as the project releases more information. |
| 53 | |
| 54 | ## Workflow |
| 55 | |
| 56 | - Use allocation data as context for unlock analysis — understanding allocations helps interpret **who** is receiving unlocked tokens and why it matters. |
| 57 | - Chain with `tok fundraising detail <id>` to see investor-specific allocation details and funding round information. |
| 58 | - Compare `allocationLockedAmount` vs `allocationUnlockedAmount` per allocation to identify which groups still have significant locked positions. |