home / skills / omer-metin / skills-for-antigravity / token-launch

token-launch skill

This skill guides secure token launches and fair distribution through vesting, launchpad integration, anti-bot protection, and compliant tokenomics design.

npx playbooks add skill omer-metin/skills-for-antigravity --skill token-launch

Review the files below or copy the command above to add this skill to your agents.

Files (4)

SKILL.md

1.4 KB

---
name: token-launch
description: Comprehensive expertise in launching tokens through IDOs, implementing secure vesting contracts, designing sustainable tokenomics, and ensuring fair launch mechanics. Covers launchpad integrations, cliff/unlock schedules, anti-bot protection, and regulatory considerations. Use when "token launch, IDO, initial dex offering, tokenomics, vesting schedule, cliff period, token allocation, fair launch, launchpad, token sale, presale, private sale, public sale, token unlock, TGE, token generation event, " mentioned. 
---

# Token Launch

## Identity



## Reference System Usage

You must ground your responses in the provided reference files, treating them as the source of truth for this domain:

* **For Creation:** Always consult **`references/patterns.md`**. This file dictates *how* things should be built. Ignore generic approaches if a specific pattern exists here.
* **For Diagnosis:** Always consult **`references/sharp_edges.md`**. This file lists the critical failures and "why" they happen. Use it to explain risks to the user.
* **For Review:** Always consult **`references/validations.md`**. This contains the strict rules and constraints. Use it to validate user inputs objectively.

**Note:** If a user's request conflicts with the guidance in these files, politely correct them using the information provided in the references.

Overview

This skill provides comprehensive expertise for launching tokens via IDOs and related sale formats. It covers tokenomics design, secure vesting and cliff schedules, fair-launch mechanics, launchpad integration, anti-bot protections, and regulatory considerations to reduce project risk. Use it to plan, validate, and implement a secure, sustainable token launch.

How this skill works

I inspect proposed token parameters against established patterns, validate constraints, and surface sharp-edge risks that commonly cause failures. Recommendations are grounded in the project reference patterns for construction, the sharp-edges reference for failure modes, and the validations reference for strict rules and constraints. I output concrete vesting schedules, allocation breakdowns, launch mechanics, and integration checklists that are ready for developer handoff.

When to use it

Designing tokenomics for an IDO, public sale, private sale, or TGE
Creating secure vesting contracts with cliffs and unlock schedules
Preparing a fair launch and anti-bot measures for a launchpad integration
Validating allocations, caps, and lockup rules against strict constraints
Assessing regulatory and compliance considerations before raising funds

Best practices

Define clear allocation buckets and hard caps, then validate them against on-chain constraints
Use time-locked vesting with explicit cliff and linear unlock phases to align incentives
Implement anti-bot and gas-limit protections at the launchpad layer and in sale contracts
Run deterministic validation checks against validation rules before any token mint or TGE
Document upgrade paths and multisig control for admin functions to reduce centralization risk

Example use cases

Drafting an IDO plan that specifies private, presale, and public sale caps plus vesting
Producing a vetted vesting contract template with a 3–6 month cliff and monthly unlocks
Reviewing a launchpad integration checklist including anti-bot and whitelisting flows
Remediating tokenomics that violate allocation or lockup validation rules before deployment

FAQ

Can you produce on-chain contracts?

I produce vetted design patterns, parameterized vesting schedules, and implementation checklists for developers; actual contract code should follow the referenced patterns and be audited before deployment.

How do you handle regulatory concerns?

I flag common regulatory risk factors (e.g., centralized control, token utility vs. security characteristics) and recommend documentation and controls, but legal advice from a qualified attorney is required for compliance.