@tokenomist-ai/tokenomist-cli 0.1.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/LICENSE +21 -0
- package/README.md +176 -0
- package/dist/index.js +1237 -0
- package/dist/index.js.map +1 -0
- package/dist/update-check.js +113 -0
- package/dist/update-check.js.map +1 -0
- package/package.json +76 -0
- package/scripts/postinstall.js +162 -0
- package/skills/tokenomist-allocation-breakdown/SKILL.md +76 -0
- package/skills/tokenomist-burn-buyback/SKILL.md +92 -0
- package/skills/tokenomist-emission-report/SKILL.md +70 -0
- package/skills/tokenomist-fundraising-lookup/SKILL.md +89 -0
- package/skills/tokenomist-token-overview/SKILL.md +80 -0
- package/skills/tokenomist-unlock-analysis/SKILL.md +87 -0
|
@@ -0,0 +1,76 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: tokenomist-allocation-breakdown
|
|
3
|
+
description: Get 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.
|
|
4
|
+
metadata:
|
|
5
|
+
openclaw:
|
|
6
|
+
requires:
|
|
7
|
+
env:
|
|
8
|
+
- TOKENOMIST_API_KEY
|
|
9
|
+
bins:
|
|
10
|
+
- tokenomist
|
|
11
|
+
primaryEnv: TOKENOMIST_API_KEY
|
|
12
|
+
install:
|
|
13
|
+
- kind: node
|
|
14
|
+
package: "@tokenomist-ai/tokenomist-cli"
|
|
15
|
+
bins: [tokenomist]
|
|
16
|
+
allowed-tools: Bash(tokenomist:*)
|
|
17
|
+
---
|
|
18
|
+
|
|
19
|
+
# Skill: Allocation Breakdown
|
|
20
|
+
|
|
21
|
+
Get the full allocation distribution for a token — who owns what and how much is locked vs unlocked.
|
|
22
|
+
|
|
23
|
+
## When to use
|
|
24
|
+
|
|
25
|
+
When you need to understand a token's supply distribution across allocations (team, investors, community, ecosystem, etc.).
|
|
26
|
+
|
|
27
|
+
## Command
|
|
28
|
+
|
|
29
|
+
```bash
|
|
30
|
+
tokenomist allocation <tokenSlug> --output json
|
|
31
|
+
```
|
|
32
|
+
|
|
33
|
+
## Example
|
|
34
|
+
|
|
35
|
+
```bash
|
|
36
|
+
tokenomist allocation solana --output json
|
|
37
|
+
```
|
|
38
|
+
|
|
39
|
+
## Key output fields
|
|
40
|
+
|
|
41
|
+
**Top-level:**
|
|
42
|
+
- `name`, `symbol` — token identification
|
|
43
|
+
- `maxSupply` — maximum token supply (null if unlimited)
|
|
44
|
+
- `totalUnlockedAmount` — total tokens currently unlocked
|
|
45
|
+
- `totalLockedAmount` — total tokens still locked
|
|
46
|
+
- `totalUntrackedAmount` — tokens not tracked by Tokenomist
|
|
47
|
+
- `totalTBDLockedAmount` — tokens locked with no defined unlock schedule
|
|
48
|
+
|
|
49
|
+
**Per allocation (`allocations[]`):**
|
|
50
|
+
- `allocationName` — project-specific allocation name
|
|
51
|
+
- `standardAllocationName` — Tokenomist's standardized category (comparable across projects)
|
|
52
|
+
- `allocationType` — allocation classification
|
|
53
|
+
- `allocationAmount` — total tokens in this allocation
|
|
54
|
+
- `allocationUnlockedAmount` — tokens unlocked from this allocation
|
|
55
|
+
- `allocationLockedAmount` — tokens still locked in this allocation
|
|
56
|
+
- `trackedAllocationPercentage` — % of total tracked supply
|
|
57
|
+
|
|
58
|
+
## Analysis workflow
|
|
59
|
+
|
|
60
|
+
1. Get allocation: `tokenomist allocation <slug> --output json`
|
|
61
|
+
2. Check `totalLockedAmount` vs `totalUnlockedAmount` for overall supply status
|
|
62
|
+
3. Look at individual allocations — high locked amounts in "Investor" or "Team" allocations signal future sell pressure
|
|
63
|
+
4. Compare `standardAllocationName` across different tokens for apples-to-apples comparison
|
|
64
|
+
5. Cross-reference with `tokenomist unlock upcoming` to see when locked tokens will release
|
|
65
|
+
|
|
66
|
+
## Domain Context
|
|
67
|
+
|
|
68
|
+
- Allocations are **point-in-time analyses**. They reflect the current understanding of token distribution and may be updated as new information becomes available.
|
|
69
|
+
- `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.
|
|
70
|
+
- `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.
|
|
71
|
+
|
|
72
|
+
## Workflow
|
|
73
|
+
|
|
74
|
+
- Use allocation data as context for unlock analysis — understanding allocations helps interpret **who** is receiving unlocked tokens and why it matters.
|
|
75
|
+
- Chain with `tokenomist fundraising <slug>` to see investor-specific allocation details and funding round information.
|
|
76
|
+
- Compare `allocationLockedAmount` vs `allocationUnlockedAmount` per allocation to identify which groups still have significant locked positions.
|
|
@@ -0,0 +1,92 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: tokenomist-burn-buyback
|
|
3
|
+
description: Check token burn and buyback activity. Use when analyzing deflationary mechanisms — burns, buybacks, and net inflation.
|
|
4
|
+
metadata:
|
|
5
|
+
openclaw:
|
|
6
|
+
requires:
|
|
7
|
+
env:
|
|
8
|
+
- TOKENOMIST_API_KEY
|
|
9
|
+
bins:
|
|
10
|
+
- tokenomist
|
|
11
|
+
primaryEnv: TOKENOMIST_API_KEY
|
|
12
|
+
install:
|
|
13
|
+
- kind: node
|
|
14
|
+
package: "@tokenomist-ai/tokenomist-cli"
|
|
15
|
+
bins: [tokenomist]
|
|
16
|
+
allowed-tools: Bash(tokenomist:*)
|
|
17
|
+
---
|
|
18
|
+
|
|
19
|
+
# Skill: Burn & Buyback
|
|
20
|
+
|
|
21
|
+
Check token burn and buyback activity.
|
|
22
|
+
|
|
23
|
+
## When to use
|
|
24
|
+
|
|
25
|
+
When you need to analyze deflationary mechanisms — how many tokens have been permanently burned or bought back from the market.
|
|
26
|
+
|
|
27
|
+
## Commands
|
|
28
|
+
|
|
29
|
+
### Burns
|
|
30
|
+
|
|
31
|
+
List all tokens with burns:
|
|
32
|
+
```bash
|
|
33
|
+
tokenomist burn list --output json
|
|
34
|
+
```
|
|
35
|
+
|
|
36
|
+
Get burn events for a specific token:
|
|
37
|
+
```bash
|
|
38
|
+
tokenomist burn detail <tokenSlug> --output json
|
|
39
|
+
tokenomist burn detail <tokenSlug> --start 2024-01-01 --end 2024-12-31 --output json
|
|
40
|
+
```
|
|
41
|
+
|
|
42
|
+
### Buybacks
|
|
43
|
+
|
|
44
|
+
List all tokens with buybacks:
|
|
45
|
+
```bash
|
|
46
|
+
tokenomist buyback list --output json
|
|
47
|
+
```
|
|
48
|
+
|
|
49
|
+
Get buyback events for a specific token:
|
|
50
|
+
```bash
|
|
51
|
+
tokenomist buyback detail <tokenSlug> --output json
|
|
52
|
+
tokenomist buyback detail <tokenSlug> --start 2024-01-01 --end 2024-12-31 --output json
|
|
53
|
+
```
|
|
54
|
+
|
|
55
|
+
## Key output fields
|
|
56
|
+
|
|
57
|
+
**Burn list:**
|
|
58
|
+
- `totalBurnAmount` — total tokens burned for this token
|
|
59
|
+
|
|
60
|
+
**Burn detail:**
|
|
61
|
+
- `burns[].burnDate` — when the burn happened
|
|
62
|
+
- `burns[].amount` — tokens burned
|
|
63
|
+
- `burns[].burnType` — type of burn event
|
|
64
|
+
- `burns[].metadata.burnReasons` — why tokens were burned
|
|
65
|
+
|
|
66
|
+
**Buyback list:**
|
|
67
|
+
- `totalBuybackAmount` — total tokens bought back
|
|
68
|
+
|
|
69
|
+
**Buyback detail:**
|
|
70
|
+
- `buybacks[].buybackDate` — when the buyback happened
|
|
71
|
+
- `buybacks[].tokenAmount` — tokens bought back
|
|
72
|
+
- `buybacks[].value` — USD value of buyback
|
|
73
|
+
- `buybacks[].spentAmount` / `spentUnit` — what was spent (e.g. USDC)
|
|
74
|
+
|
|
75
|
+
## Analysis workflow
|
|
76
|
+
|
|
77
|
+
1. List tokens with burns: `tokenomist burn list --output json`
|
|
78
|
+
2. Compare `totalBurnAmount` across tokens to find most deflationary projects
|
|
79
|
+
3. Drill into a token: `tokenomist burn detail <slug> --output json`
|
|
80
|
+
4. Cross-reference with emissions from `tokenomist emission weekly <slug>` to calculate net inflation
|
|
81
|
+
|
|
82
|
+
## Domain Context
|
|
83
|
+
|
|
84
|
+
- A sequential buyback + burn is a **single** deflationary event, not two. Counting both would double-count the supply reduction.
|
|
85
|
+
- Burns from **locked** supply don't reduce circulating supply — they reduce future potential supply instead.
|
|
86
|
+
- The `startDate`/`endDate` filters on burn/buyback detail commands filter by **last activity date**, not the event date range. This is an API quirk — the filters determine which tokens to include based on when they last had activity.
|
|
87
|
+
|
|
88
|
+
## Workflow
|
|
89
|
+
|
|
90
|
+
- Cross-reference with `tokenomist emission weekly <slug>` to calculate net inflation: if burns exceed emissions, the token is net deflationary.
|
|
91
|
+
- Use `tokenomist token list --output json` to check `hasBurn`/`hasBuyback` fields before querying detail commands (these fields are only visible in JSON output, not table mode).
|
|
92
|
+
- Compare `totalBurnAmount` across tokens to find the most deflationary projects.
|
|
@@ -0,0 +1,70 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: tokenomist-emission-report
|
|
3
|
+
description: Get daily or weekly token emission data with allocation breakdowns. Use when analyzing token inflation, comparing emission rates, or understanding supply increases.
|
|
4
|
+
metadata:
|
|
5
|
+
openclaw:
|
|
6
|
+
requires:
|
|
7
|
+
env:
|
|
8
|
+
- TOKENOMIST_API_KEY
|
|
9
|
+
bins:
|
|
10
|
+
- tokenomist
|
|
11
|
+
primaryEnv: TOKENOMIST_API_KEY
|
|
12
|
+
install:
|
|
13
|
+
- kind: node
|
|
14
|
+
package: "@tokenomist-ai/tokenomist-cli"
|
|
15
|
+
bins: [tokenomist]
|
|
16
|
+
allowed-tools: Bash(tokenomist:*)
|
|
17
|
+
---
|
|
18
|
+
|
|
19
|
+
# Skill: Emission Report
|
|
20
|
+
|
|
21
|
+
Get daily or weekly token emission data with allocation breakdowns.
|
|
22
|
+
|
|
23
|
+
## When to use
|
|
24
|
+
|
|
25
|
+
When you need to analyze token inflation over time, compare emission rates across periods, or understand which allocations are contributing to supply increases.
|
|
26
|
+
|
|
27
|
+
## Commands
|
|
28
|
+
|
|
29
|
+
### Daily emission
|
|
30
|
+
```bash
|
|
31
|
+
tokenomist emission daily <tokenSlug> --output json
|
|
32
|
+
tokenomist emission daily arbitrum --start 2024-08-01 --end 2024-08-31 --output json
|
|
33
|
+
```
|
|
34
|
+
|
|
35
|
+
### Weekly emission
|
|
36
|
+
```bash
|
|
37
|
+
tokenomist emission weekly <tokenSlug> --output json
|
|
38
|
+
tokenomist emission weekly arbitrum --start 2024-01-01 --end 2024-06-30 --output json
|
|
39
|
+
```
|
|
40
|
+
|
|
41
|
+
## Key output fields
|
|
42
|
+
|
|
43
|
+
| Field | Description |
|
|
44
|
+
|-------|-------------|
|
|
45
|
+
| `startDate` | Period start |
|
|
46
|
+
| `endDate` | Period end |
|
|
47
|
+
| `unlockAmount` | Tokens emitted in period |
|
|
48
|
+
| `unlockValue` | USD value of emitted tokens |
|
|
49
|
+
| `referencePrice` | Token price used for value calculation |
|
|
50
|
+
| `allocations` | Breakdown by allocation (name, amount, value) |
|
|
51
|
+
| `totalCumulativeUnlockedAmount` | Running total of all unlocked tokens |
|
|
52
|
+
|
|
53
|
+
## Analysis workflow
|
|
54
|
+
|
|
55
|
+
1. Get weekly emissions to see the trend: `tokenomist emission weekly <slug> --output json`
|
|
56
|
+
2. Look at `unlockAmount` over time to spot acceleration or deceleration
|
|
57
|
+
3. Check `allocations` to see if emissions are going to investors (sell pressure) vs community/ecosystem (growth)
|
|
58
|
+
4. Compare `unlockValue` against market cap from `tokenomist token list` to assess dilution
|
|
59
|
+
|
|
60
|
+
## Domain Context
|
|
61
|
+
|
|
62
|
+
- Emission data shows **scheduled** releases per allocation. Actual on-chain supply may differ due to relocks, delays, or early releases.
|
|
63
|
+
- Compare `unlockValue` against market cap (from `tokenomist token list`) to assess dilution impact.
|
|
64
|
+
- Emissions going to "Investor" or "Team" allocations typically represent higher sell pressure than "Community" or "Ecosystem" allocations.
|
|
65
|
+
|
|
66
|
+
## Workflow
|
|
67
|
+
|
|
68
|
+
- Combine with `tokenomist unlock events <slug>` to distinguish between cliff unlocks (large one-time events) and continuous emissions (steady daily/weekly releases).
|
|
69
|
+
- Chain with `tokenomist burn detail <slug>` to calculate net inflation: emissions minus burns = net new supply.
|
|
70
|
+
- Use `tokenomist allocation <slug>` to see the full allocation picture and understand where emissions are going.
|
|
@@ -0,0 +1,89 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: tokenomist-fundraising-lookup
|
|
3
|
+
description: Look up fundraising rounds, investors, and valuation data for tokens. Use when finding who invested, at what valuation, or analyzing investor portfolios.
|
|
4
|
+
metadata:
|
|
5
|
+
openclaw:
|
|
6
|
+
requires:
|
|
7
|
+
env:
|
|
8
|
+
- TOKENOMIST_API_KEY
|
|
9
|
+
bins:
|
|
10
|
+
- tokenomist
|
|
11
|
+
primaryEnv: TOKENOMIST_API_KEY
|
|
12
|
+
install:
|
|
13
|
+
- kind: node
|
|
14
|
+
package: "@tokenomist-ai/tokenomist-cli"
|
|
15
|
+
bins: [tokenomist]
|
|
16
|
+
allowed-tools: Bash(tokenomist:*)
|
|
17
|
+
---
|
|
18
|
+
|
|
19
|
+
# Skill: Fundraising Lookup
|
|
20
|
+
|
|
21
|
+
Look up fundraising rounds, investors, and valuation data for tokens.
|
|
22
|
+
|
|
23
|
+
## When to use
|
|
24
|
+
|
|
25
|
+
When you need to find out who invested in a token, what valuation rounds were raised at, or what an investor's portfolio looks like.
|
|
26
|
+
|
|
27
|
+
## Commands
|
|
28
|
+
|
|
29
|
+
### Get fundraising data for a token
|
|
30
|
+
```bash
|
|
31
|
+
tokenomist fundraising <tokenSlug> --output json
|
|
32
|
+
tokenomist fundraising uniswap --output json
|
|
33
|
+
```
|
|
34
|
+
|
|
35
|
+
Filter by date or amount:
|
|
36
|
+
```bash
|
|
37
|
+
tokenomist fundraising uniswap --funding-date-min 2020-01-01 --raised-amount-min 1000000 --output json
|
|
38
|
+
```
|
|
39
|
+
|
|
40
|
+
### List all investors
|
|
41
|
+
```bash
|
|
42
|
+
tokenomist investor list --output json
|
|
43
|
+
```
|
|
44
|
+
|
|
45
|
+
### Get investor detail with portfolio
|
|
46
|
+
```bash
|
|
47
|
+
tokenomist investor detail <investorId> --output json
|
|
48
|
+
tokenomist investor detail <investorId> --is-lead-investor --output json
|
|
49
|
+
```
|
|
50
|
+
|
|
51
|
+
Filter by date or amount:
|
|
52
|
+
```bash
|
|
53
|
+
tokenomist investor detail <investorId> --funding-date-min 2023-01-01 --raised-amount-min 5000000 --output json
|
|
54
|
+
```
|
|
55
|
+
|
|
56
|
+
## Key output fields
|
|
57
|
+
|
|
58
|
+
**Token fundraising:**
|
|
59
|
+
- `totalAmountRaised` — total USD raised across all rounds
|
|
60
|
+
- `investorReleasedPercentage` — how much investor allocation has unlocked
|
|
61
|
+
- `fundingRounds[].fundingRound` — round name (Seed, Series A, etc.)
|
|
62
|
+
- `fundingRounds[].amountRaised` — USD raised in that round
|
|
63
|
+
- `fundingRounds[].valuation` — token valuation at that round
|
|
64
|
+
- `fundingRounds[].pricePerToken` — price investors paid
|
|
65
|
+
- `fundingRounds[].investors` — list of investors in the round
|
|
66
|
+
|
|
67
|
+
**Investor detail:**
|
|
68
|
+
- `fundingRounds[].tokenId` — which token they invested in
|
|
69
|
+
- `fundingRounds[].isLeadInvestor` — whether they led the round
|
|
70
|
+
- `fundingRounds[].totalAmountRaisedinThatRound` — round size
|
|
71
|
+
|
|
72
|
+
## Analysis workflow
|
|
73
|
+
|
|
74
|
+
1. Look up a token: `tokenomist fundraising <slug> --output json`
|
|
75
|
+
2. Compare `pricePerToken` across rounds to see valuation progression
|
|
76
|
+
3. Check `investorReleasedPercentage` — high % means most investor tokens are already unlocked (less future sell pressure)
|
|
77
|
+
4. Look at individual investors: `tokenomist investor detail <id> --output json` to see their full portfolio
|
|
78
|
+
|
|
79
|
+
## Domain Context
|
|
80
|
+
|
|
81
|
+
- `pricePerToken` in early rounds vs current market price shows investor ROI — large multiples may indicate sell pressure as investors take profits.
|
|
82
|
+
- `investorReleasedPercentage` indicates future sell pressure — a high percentage means most investor tokens have already unlocked (less remaining overhang).
|
|
83
|
+
- Valuation at each round shows the project's funding trajectory.
|
|
84
|
+
|
|
85
|
+
## Workflow
|
|
86
|
+
|
|
87
|
+
- Chain with `tokenomist investor detail <investorId>` to see an investor's full portfolio across multiple tokens.
|
|
88
|
+
- Cross-reference `pricePerToken` with current market data from `tokenomist token list` to calculate investor ROI.
|
|
89
|
+
- Use `tokenomist unlock events <slug>` to see when remaining investor allocations will unlock.
|
|
@@ -0,0 +1,80 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: tokenomist-token-overview
|
|
3
|
+
description: Get a summary list of all tracked tokens with market data and supply info. Use when browsing tokens, comparing market caps, or finding which tokens have fundraising/burn/buyback data.
|
|
4
|
+
metadata:
|
|
5
|
+
openclaw:
|
|
6
|
+
requires:
|
|
7
|
+
env:
|
|
8
|
+
- TOKENOMIST_API_KEY
|
|
9
|
+
bins:
|
|
10
|
+
- tokenomist
|
|
11
|
+
primaryEnv: TOKENOMIST_API_KEY
|
|
12
|
+
install:
|
|
13
|
+
- kind: node
|
|
14
|
+
package: "@tokenomist-ai/tokenomist-cli"
|
|
15
|
+
bins: [tokenomist]
|
|
16
|
+
allowed-tools: Bash(tokenomist:*)
|
|
17
|
+
---
|
|
18
|
+
|
|
19
|
+
# Skill: Token Overview
|
|
20
|
+
|
|
21
|
+
Get a summary list of all tracked tokens with market data and supply info.
|
|
22
|
+
|
|
23
|
+
## When to use
|
|
24
|
+
|
|
25
|
+
When you need to browse all available tokens, compare market caps, or find which tokens have fundraising/burn/buyback data.
|
|
26
|
+
|
|
27
|
+
## Command
|
|
28
|
+
|
|
29
|
+
```bash
|
|
30
|
+
tokenomist token list --output json
|
|
31
|
+
```
|
|
32
|
+
|
|
33
|
+
## Output fields
|
|
34
|
+
|
|
35
|
+
| Field | Description |
|
|
36
|
+
|-------|-------------|
|
|
37
|
+
| `id` | Token slug (use in other commands) |
|
|
38
|
+
| `name` | Token name |
|
|
39
|
+
| `symbol` | Ticker symbol |
|
|
40
|
+
| `marketCap` | Current market cap (USD), null if unavailable |
|
|
41
|
+
| `circulatingSupply` | Circulating supply |
|
|
42
|
+
| `totalLockedAmount` | Tokens still locked |
|
|
43
|
+
| `unlockedAmount` | Tokens already unlocked |
|
|
44
|
+
| `hasStandardAllocation` | Whether allocation data exists |
|
|
45
|
+
| `hasFundraising` | Whether fundraising data exists |
|
|
46
|
+
| `hasBurn` | Whether burn data exists |
|
|
47
|
+
| `hasBuyback` | Whether buyback data exists |
|
|
48
|
+
|
|
49
|
+
## Examples
|
|
50
|
+
|
|
51
|
+
List all tokens as a table:
|
|
52
|
+
```bash
|
|
53
|
+
tokenomist token list
|
|
54
|
+
```
|
|
55
|
+
|
|
56
|
+
Get JSON for programmatic use:
|
|
57
|
+
```bash
|
|
58
|
+
tokenomist token list --output json
|
|
59
|
+
```
|
|
60
|
+
|
|
61
|
+
Export to CSV:
|
|
62
|
+
```bash
|
|
63
|
+
tokenomist token list --output csv > tokens.csv
|
|
64
|
+
```
|
|
65
|
+
|
|
66
|
+
## Domain Context
|
|
67
|
+
|
|
68
|
+
- Token slugs (the `id` field) are the primary identifier used across all commands. Use `token list` to discover slugs.
|
|
69
|
+
- `circulatingSupply` and `unlockedAmount` are different concepts — unlocked tokens may not be circulating (they could be held by the team, locked in DeFi protocols, or otherwise not trading on exchanges).
|
|
70
|
+
- Fields like `hasStandardAllocation`, `hasFundraising`, `hasBurn`, `hasBuyback` indicate which data types are available. Check these before querying detail commands to avoid empty results.
|
|
71
|
+
|
|
72
|
+
## Workflow
|
|
73
|
+
|
|
74
|
+
- **Start here** to find token slugs before using other commands.
|
|
75
|
+
- Use the slug in: `tokenomist unlock events <slug>`, `tokenomist emission daily <slug>`, `tokenomist allocation <slug>`, etc.
|
|
76
|
+
- Check `has*` boolean fields (visible in `--output json`) to know which data types exist for a token before querying.
|
|
77
|
+
|
|
78
|
+
## Output Size
|
|
79
|
+
|
|
80
|
+
The `token list` command returns all tracked tokens (~200+). Use `--output json` and filter programmatically for large datasets.
|
|
@@ -0,0 +1,87 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: tokenomist-unlock-analysis
|
|
3
|
+
description: Analyze token unlock events — upcoming unlocks, historical events, and allocation breakdowns. Use when checking unlock impact on market cap or reviewing unlock schedules.
|
|
4
|
+
metadata:
|
|
5
|
+
openclaw:
|
|
6
|
+
requires:
|
|
7
|
+
env:
|
|
8
|
+
- TOKENOMIST_API_KEY
|
|
9
|
+
bins:
|
|
10
|
+
- tokenomist
|
|
11
|
+
primaryEnv: TOKENOMIST_API_KEY
|
|
12
|
+
install:
|
|
13
|
+
- kind: node
|
|
14
|
+
package: "@tokenomist-ai/tokenomist-cli"
|
|
15
|
+
bins: [tokenomist]
|
|
16
|
+
allowed-tools: Bash(tokenomist:*)
|
|
17
|
+
---
|
|
18
|
+
|
|
19
|
+
# Skill: Unlock Analysis
|
|
20
|
+
|
|
21
|
+
Analyze token unlock events — upcoming unlocks, historical events, and allocation breakdowns.
|
|
22
|
+
|
|
23
|
+
## When to use
|
|
24
|
+
|
|
25
|
+
When you need to check upcoming token unlocks, assess unlock impact on market cap, or review historical unlock events for a specific token.
|
|
26
|
+
|
|
27
|
+
## Commands
|
|
28
|
+
|
|
29
|
+
### List all unlock events (grouped by token)
|
|
30
|
+
```bash
|
|
31
|
+
tokenomist unlock list --output json
|
|
32
|
+
```
|
|
33
|
+
|
|
34
|
+
Filter options:
|
|
35
|
+
```bash
|
|
36
|
+
tokenomist unlock list --min-market-cap 1000000 --min-unlock-date 2024-01-01 --max-unlock-date 2024-12-31
|
|
37
|
+
tokenomist unlock list --min-value-to-market-cap 0.01 --standard-allocation "Investor,Team"
|
|
38
|
+
```
|
|
39
|
+
|
|
40
|
+
### Get upcoming unlocks (next event per token)
|
|
41
|
+
```bash
|
|
42
|
+
tokenomist unlock upcoming --output json
|
|
43
|
+
```
|
|
44
|
+
|
|
45
|
+
### Get unlock events for a specific token
|
|
46
|
+
```bash
|
|
47
|
+
tokenomist unlock events <tokenSlug> --output json
|
|
48
|
+
tokenomist unlock events solana --start 2024-01-01 --end 2024-12-31 --output json
|
|
49
|
+
```
|
|
50
|
+
|
|
51
|
+
## Key output fields
|
|
52
|
+
|
|
53
|
+
**unlock list / upcoming:**
|
|
54
|
+
- `tokenName`, `tokenSymbol` — token identification
|
|
55
|
+
- `marketCap` — current market cap
|
|
56
|
+
- `releasedPercentage` — how much of total supply has been released
|
|
57
|
+
|
|
58
|
+
**unlock events:**
|
|
59
|
+
- `unlockDate` — when the unlock happens
|
|
60
|
+
- `cliffUnlocks.cliffAmount` — number of tokens unlocking
|
|
61
|
+
- `cliffUnlocks.cliffValue` — USD value of the unlock
|
|
62
|
+
- `cliffUnlocks.valueToMarketCap` — unlock value as % of market cap
|
|
63
|
+
- `cliffUnlocks.allocationBreakdown` — which allocations are unlocking
|
|
64
|
+
|
|
65
|
+
## Analysis workflow
|
|
66
|
+
|
|
67
|
+
1. Run `tokenomist unlock upcoming --output json` to find tokens with large upcoming unlocks
|
|
68
|
+
2. Filter by `valueToMarketCap` to identify potentially market-moving events
|
|
69
|
+
3. Drill into specific tokens with `tokenomist unlock events <slug> --output json`
|
|
70
|
+
4. Check allocation breakdown to understand who is receiving tokens (investors, team, community, etc.)
|
|
71
|
+
|
|
72
|
+
## Domain Context
|
|
73
|
+
|
|
74
|
+
- **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.
|
|
75
|
+
- Schedules may include assumptions — the allocation breakdown can help assess confidence in the schedule.
|
|
76
|
+
- `valueToMarketCap` is a key metric: unlocks representing >1% of market cap may be market-moving events.
|
|
77
|
+
|
|
78
|
+
## Workflow
|
|
79
|
+
|
|
80
|
+
- Use `tokenomist token list --output json` first to find the token slug if you don't know it.
|
|
81
|
+
- Chain with `tokenomist emission daily <slug>` for a complete unlock + emission picture.
|
|
82
|
+
- Cross-reference with `tokenomist allocation <slug>` to understand which groups (team, investors, community) are unlocking.
|
|
83
|
+
- Use `tokenomist fundraising <slug>` to see what price investors paid — compare with current price to assess sell pressure.
|
|
84
|
+
|
|
85
|
+
## Output Size
|
|
86
|
+
|
|
87
|
+
The `unlock list` command can return hundreds of events. Use date and market cap filters to narrow results: `--min-market-cap`, `--min-unlock-date`, `--max-unlock-date`.
|