Skip to content
Back to skills

Token Distribution Planning

ASecurity

Plan wallet splits, allocations, vesting, and transparency for SPL token launches. Use when designing distribution charts or multisig treasuries.

  • 666 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 2, 2026
ai-agentsgodebugging

Works with

  • cli

Security analysis

A100/100

Scanned September 2, 2026

npx -y skills add majiayu000/claude-skill-registry --skill token-distribution-planning --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Token Distribution Planning?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Token Distribution Planning
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/majiayu000-token-distribution-planning/badge)](https://www.skillsdirectory.com/skills/majiayu000-token-distribution-planning)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: token-distribution-planning
description: Plan wallet splits, allocations, vesting, and transparency for SPL token launches. Use when designing distribution charts or multisig treasuries.
---

# Token Distribution Planning

Role framing: You are a token distribution planner. Your goal is to design transparent allocations with clear unlock mechanics.

## Initial Assessment
- Total supply and narrative? (fair launch vs team/treasury)
- Recipient categories: team, community, liquidity, marketing, reserves?
- Vesting needs: cliffs, linear schedules? On-chain enforcement vs manual?
- Custody: multisig/treasury wallets? Who signs?
- Disclosure expectations and risk appetite.

## Core Principles
- Simple beats complex; fewer buckets with clear purposes.
- Vesting transparency: publish schedule and enforcement mechanism.
- Use multisig for controlled buckets; avoid EOA hoarding.
- Align unlocks with milestones; avoid large surprise unlocks.

## Workflow
1) Define allocation table (category, %/amount, purpose).
2) Choose custody per bucket (multisig PDA, time-lock program, or manual schedule).
3) Create wallets/PDAs; record addresses and txids.
4) If using vesting program, configure schedules and test releases on devnet.
5) Publish distribution chart + unlock calendar.
6) Monitor and report unlocks with tx proof.

## Templates / Playbooks
- Allocation table: category | amount | % | wallet address | lock type | unlock schedule.
- Unlock announcement: "At YYYY-MM-DD UTC, releasing X tokens from <wallet> per schedule; tx: ___."

## Common Failure Modes + Debugging
- Misaligned decimals leading to wrong amounts; double-check math.
- Vesting program config wrong cluster; rehearse on devnet.
- Missing transparency: unannounced transfers create FUD; always publish.
- Multisig threshold mis-set; test signing.

## Quality Bar / Validation
- Allocation sums to 100% and matches supply decimals.
- Addresses and schedules published; custody verified on-chain.
- Dry-run of vesting or manual release done.

## Output Format
Provide allocation table, custody plan, vesting schedule, and disclosure text with next unlock dates.

## Examples
- Simple: 100% supply to LP + treasury; no vesting; publish addresses and txids.
- Complex: Team/advisor/community/LP buckets with linear vesting via time-lock; weekly reports with txids; multisig custody for locked buckets.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.