New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

60 Launch Playbook Global

by minhnv0807 in minhnv0807/ai-business-skills

A skill your agent uses when a launch needs a repeatable EXECUTION playbook — a T-30 to D+7 timeline, per-function checklists for content, design, ads, sales, and engineering, a launch-day war room…

MITAuto-check passedMarketing & SEO

Install 60 Launch Playbook Global

skills CLI
$ npx skills add minhnv0807/ai-business-skills --skill 60-launch-playbook-global -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install minhnv0807/ai-business-skills 60-launch-playbook-global --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/minhnv0807/ai-business-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/en/60-launch-playbook-global .claude/skills/60-launch-playbook-global && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
60-launch-playbook-global
GitHub stars
609
Token cost
~3k tokens
SKILL.md length
1,430 words
Files
1
Skills in repo
142
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when a launch needs a repeatable EXECUTION playbook — a T-30 to D+7 timeline, per-function checklists for content, design, ads, sales, and engineering, a launch-day war room…

  • Works in 3 steps: Pre-launch (T-30 to T-1) → Launch-day war room → Post-launch (D+8 onward)
  • A launch needs a repeatable EXECUTION playbook — a T-30 to D+7 timeline
  • SKILL.md covers Information gathering, Principles, Phase 1 — Pre-launch (T-30 to… and Per-function checklist (before…, plus 5 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

60 Launch Playbook Global is an agent skill from minhnv0807/ai-business-skills. Use when a launch needs a repeatable EXECUTION playbook — a T-30 to D+7 timeline, per-function checklists for content, design, ads, sales, and engineering, a launch-day war room, an escalation matrix, and roll-back criteria. Trigger on 'launch playbook', 'launch checklist', 'launch day plan', 'launch SOP', 'war room', 'we launch in two weeks and nothing is organized'. Also use when a GTM strategy exists and nobody knows who does what on the day. Not for — the strategy and beachhead choice, see…

Its SKILL.md is about 3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Marketing & SEO, covering Go-to-market strategy, Feature launches and release readiness and Retrospectives. The repository describes itself as: 138 bilingual AI marketing skills (69 VN + 69 Global) for Claude Code, OpenCode, Codex, VS Code. Four role SOP packs — content, design, performance, leader ops — plus strategy… The licence is MIT.

When your agent uses it

  • A launch needs a repeatable EXECUTION playbook — a T-30 to D+7 timeline
  • Per-function checklists for content
  • A launch-day war room
  • An escalation matrix

Example prompts

  • “launch playbook”
  • “launch checklist”
  • “launch day plan”
  • “/60-launch-playbook-global”

Workflow steps

3 steps, taken from the step headings in SKILL.md.

  1. Pre-launch (T-30 to T-1)
  2. Launch-day war room
  3. Post-launch (D+8 onward)

What it can do on your machine

Read from SKILL.md and the folder at commit 0360adc. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

60 Launch Playbook Global loads about 3k tokens when it runs. Until then it costs about 179 tokens; SKILL.md has 1,430 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~179
When it runs · the whole SKILL.md, loaded when a task matches
~3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from minhnv0807/ai-business-skills at commit 0360adc, republished under its MIT licence (© minhnv0807). 1,430 words, ~2,970 tokens.

Download SKILL.mdSave it as .claude/skills/60-launch-playbook-global/SKILL.md (or your agent's skills folder).
name
60-launch-playbook-global
description
Use when a launch needs a repeatable EXECUTION playbook — a T-30 to D+7 timeline, per-function checklists for content, design, ads, sales, and engineering, a launch-day war room, an escalation matrix, and roll-back criteria. Trigger on 'launch playbook', 'launch checklist', 'launch day plan', 'launch SOP', 'war room', 'we launch in two weeks and nothing is organized'. Also use when a GTM strategy exists and nobody knows who does what on the day. Not for — the strategy and beachhead choice, see `59-go-to-market-global`; the campaign brief, see `02-campaign-brief-global`; the post-launch review, see `63-campaign-retrospective-global`; a live crisis, see `66-crisis-playbook-global`.
metadata.version
1.0.1
metadata.category
strategy
license
MIT
triggers
launch playbook, launch process, launch checklist, launch SOP, war room, roll back launch, launch day plan, launch preparation
output
File .md — three-phase playbook: pre-launch T-30 to T-1, launch-day war room plus D+1 to D+7, post-launch; per-function checklists, escalation matrix…
related
59-go-to-market-global, 02-campaign-brief-global, 41-campaign-asset-list-global, 63-campaign-retrospective-global, 66-crisis-playbook-global

Launch Playbook (Global)

A playbook is not a plan. A plan is for one launch; a playbook is reusable and improves after every launch. Successful launches are not luck — they are the product of correct preparation and disciplined execution. Run 59-go-to-market-global first for the GTM plan; this playbook is the execution layer underneath it.

Information gathering

Read the GTM plan and the campaign brief if available. If missing, ask up to 4 questions:

  1. What is launching, and on what date? Product or offer, exact D-day, and any blackout dates in the period.
  2. Who is on the team? Content, design, media buying, sales/support, engineering — who can do what?
  3. What assets exist already? Landing page, creative, email sequence, tracking — status of each.
  4. What did the last launch teach you? Read the previous retrospective and update the playbook; never reuse the old version unchanged.

Principles

  1. Update the playbook after every launch. Lessons from the retrospective must land in the playbook.
  2. "No-go" is a valid decision. Launching at the wrong time is worse than launching late.
  3. Only the leader decides go/no-go. Never delegate it.
  4. Plan backwards from D-day. Every task has exactly one owner and a deadline with a specific time and timezone. Keep a one-day buffer before launch for the unexpected.
  5. Ads are built and left Paused. They go live on D-day only, never earlier.

Phase 1 — Pre-launch (T-30 to T-1)

T-30 to T-21: Foundation
  • Offer finalized: price, bundle, guarantee, bonuses locked (no changes after this point)
  • Positioning and core message locked (from 58-positioning-global or the GTM plan)
  • Landing page brief handed to design/dev
  • Content team briefed: angles, hooks, visual direction
  • Media buyer briefed: audience research, account structure, ads plan
  • Full asset list built (run 41-campaign-asset-list-global)
  • Claim substantiation file started: every performance, health, or income claim has evidence on record
T-21 to T-14: Build
  • Landing page live, tracking verified green (pixel, server-side events, UTMs)
  • Pre-launch email sequence written (3-5 emails), unsubscribe and sender identity compliant with CAN-SPAM/GDPR
  • Designer has the brief and the asset list (T-14 checkpoint)
  • Teaser content starts: 1-2 posts per week, problem-aware, NO offer reveal
  • Warm-audience ads live (engagement objective, low CPM)
  • Email #1 sent: name the problem
  • Seeding in relevant communities (Reddit, Discord, Slack, niche forums) following each community's self-promotion rules
  • Creators / UGC partners briefed, with disclosure requirements stated (FTC requires clear #ad or #sponsored disclosure on paid endorsements)
T-7: Ramp up
  • Teasers move to daily cadence
  • Designer submits MVP concept > leader approves (T-7); complex assets such as the landing page finished by T-5
  • Email #2: reveal the problem, hint at the solution
  • Ads budget increased (traffic to landing page to build custom audiences)
  • Social proof collected: testimonials from beta users or existing customers
  • FAQ content published: handles the common objections
T-3: Final prep
  • All content approved and scheduled (medium-complexity assets — carousels, banner sets — done by T-3)
  • Ads fully built and Paused, waiting for D-day
  • Landing page final QA: load time, forms, payment (card, PayPal, wallets), mobile rendering
  • Email #3: "Doors open [date] — want to be told first?"
  • Team brief: who does what, at what hour, in which timezone (war room roster)
  • Inbox coverage assigned with response scripts ready
  • Fast assets (statics, stories) done by T-1
T-1: Go / no-go check
  • Tracking 100% working
  • Payment tested successfully across every method offered
  • All links resolve, no 404s
  • Offer copy correct (price, bonuses, deadline)
  • Consent, privacy notice, and unsubscribe paths verified
  • Team confirmed ready
  • LEADER SIGN-OFF: GO / NO-GO — any missing item means NO-GO

Per-function checklist (before D-day)

FunctionChecklist
ContentCaptions, scripts, and creative approved by leader; hashtags and UTM links complete; schedule set or a person on duty to post; backup content if creator delivery slips
DesignCorrect size per platform; assets follow the timeline T-14 brief > T-7 concept > T-5 complex > T-3 medium > T-1 fast; quick-asset standby on launch day
Ads (media buyer)Pixel and tracking verified; campaigns built and Paused; budget matches plan; UTMs on every link; backup creative ready in case of policy rejection
Sales / supportInbox coverage by shift and timezone; reply scripts for common comments and DMs; lead handoff process to sales; complaint-handling script
EngineeringPage loads fast, forms work, payment tested; on-call engineer on launch day; redirect plan if the page goes down

Phase 2 — Launch-day war room

The war room is one shared channel plus a clear on-duty roster. The leader coordinates and each function has a single point of contact. Data is checked hourly and decisions are made same-day. For distributed teams, publish the roster in a single reference timezone with local equivalents, and require written status updates at each checkpoint so no decision depends on someone being awake.

Hour (launch timezone)ActivityOwner
T-1hLeader runs the final check (page, tracking, schedule)Leader
0:00Publish the official announcementWriter
+0:30Turn on BOFU ads (Meta, TikTok, Google)Media buyer
+1:00Email and SMS blast: "We're live"Leader
+2:00Data check 1: page views, form submits, ad deliveryLeader
+4:00Second post (different angle — social proof or urgency)Writer
+7:00Mid-day review — adjust or holdLeader
+12:00Evening push at peak time: stories, repostsWriter
+15:00Day-1 wrap: numbers, anomalies, decisions for day 2Leader
Show full SKILL.md (570 more words)Show less
D+1 to D+7
DayActivityOwner
D+1Follow-up email to non-buying leads — handle objectionsLeader
D+1Mark winning and losing creative from day-1 dataMedia buyer + designer
D+2Post social proof: first buyers, early resultsWriter
D+3Media buyer report > leader decides scale, hold, or cutLeader
D+5Urgency push: "X seats left" or "bonus ends [date]"Writer + leader
D+7Last call: email, SMS, post > close cartLeader + writer
Escalation matrix
SituationSeverityActionHandled by
Tracking not firingUrgentPause ads, fix immediatelyMedia buyer + engineering
Landing page downUrgentRedirect or fix within 30 minutesEngineering
Payment failingUrgentNotify engineering and leader immediatelyEngineering
Ads rejected by platform policyHighActivate backup creative, file appealMedia buyer
CPA above 3x targetHighNotify leader immediately, wait for decisionMedia buyer
Negative comments spreadingHighNotify leader, do NOT self-handle — follow 66-crisis-playbook-globalWriter + leader
Claim challenged or complaint alleging deceptive advertisingHighPause the asset, escalate to leader and legalLeader
Roll-back criteria

Roll-back means pausing part or all of the launch to fix it. The leader decides.

SituationThresholdRoll-back action
Tracking wrong or not firingAnyPause all ads until fixed — do not burn budget blind
CPA above threshold> 3x target after the first 24hPause BOFU ads, keep organic; review creative and audience before restarting
Landing page CVR far below expectation< 1/3 of expected after 48hKeep TOFU, pause BOFU push; fix headline, form, and speed, then restart
Offer displayed wrong (price or bonus)AnyRemove the post, fix, repost — faster than apologizing on the broken post
Reputation issue or complaints spreadingSpreadingSwitch to 66-crisis-playbook-global, stop all sales posts until resolved

Roll-back is not failure. Continuing while knowing you are wrong is.

Phase 3 — Post-launch (D+8 onward)

  • D+8 to D+14: pull all data (revenue, leads, ROAS, CPA, CVR, top channels); media buyer writes the performance report; collect new customer feedback; 30-minute team debrief
  • D+14 onward: decide on an evergreen campaign (if yes, always-on ads with an explicit ROAS target); document testimonials and case studies from the first customers
  • Update this playbook with lessons from the retrospective (63-campaign-retrospective-global) — mandatory, never skipped because the team is busy

Output structure

File name: launch-playbook-[product-name]-[YYYYMMDD].md — contains the T-30 to D+7 timeline with owners and deadlines filled in, the 5 function checklists, the war room roster, the escalation matrix, the roll-back criteria, and a "lessons applied from last launch" section.

  • 59-go-to-market-global: run first — the GTM plan is the strategic input, this playbook is the execution layer.
  • 02-campaign-brief-global: brief the team before entering the timeline.
  • 41-campaign-asset-list-global: enumerate the assets to produce at the T-30 to T-21 checkpoint.
  • 63-campaign-retrospective-global: run after every launch — lessons feed back into this playbook.
  • 66-crisis-playbook-global: activate when negative sentiment spreads or a reputation issue appears.

Quality checklist

  • Timeline complete from T-30 to D+7, planned backwards from D-day
  • Every task has exactly one owner and a deadline with a time and timezone
  • Checklists cover all 5 functions: content, design, ads, sales/support, engineering
  • T-1 go/no-go checklist complete — leader signs off
  • War room has an hourly roster and a named point of contact per function
  • Escalation matrix is explicit: situation > severity > action > owner
  • Roll-back criteria use concrete numeric thresholds, not judgment calls
  • Ads are built and left Paused — only turned on at D-day
  • A one-day buffer exists before launch
  • Claim substantiation and endorsement disclosure are verified before assets go live
  • The playbook update step after launch is included

© minhnv0807, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/en/60-launch-playbook-global of minhnv0807/ai-business-skills.

Open the folder on GitHubat commit 0360adc

Compare with similar skills

60 Launch Playbook Global next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

60 Launch Playbook Global compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
60 Launch Playbook Global this skillminhnv0807/ai-business-skills609—~3kAutomated safety check: PassMIT
Gingiris Go GlobalGingiris-1031/Competitor-analysis-tool110—~868Automated safety check: PassNone
Building Gtm SystemGTM-Strategist/gtm-strategist-skills264—~6.1kAutomated safety check: PassMIT
Early Access Designeraaron-he-zhu/aaron-marketing-skills2.9k—~3.4kAutomated safety check: PassApache-2.0
Mvp Launchooiyeefei/ccc495—~1.1kAutomated safety check: PassMIT
Launch Strategyfreekmurze/dotfiles1k22 repos~3.1kAutomated safety check: PassNone

Similar skills

  • Gingiris Go Global

    Gingiris-1031/Competitor-analysis-tool

    🇺🇸 AI Product / SaaS Go-Global Complete SOP — From competitor research to launch to monetization.

    110 GitHub stars~868 tokensUpdated 2 days ago
    Marketing & SEOAuto-check passed

  • Building Gtm System

    GTM-Strategist/gtm-strategist-skills

    A skill your agent uses when the user has already launched and wants to build repeatable growth systems, set up a CRM, create SOPs, or run growth experiments.

    264 GitHub stars~6.1k tokensUpdated 2 mo ago
    Marketing & SEOAuto-check passed

  • Early Access Designer

    aaron-he-zhu/aaron-marketing-skills

    A skill your agent uses when the user asks to "design an early access program", "set up a waitlist and beta stages", or "define beta graduation criteria"; produces a waitlist→concept→alpha→beta→GA…

    2.9k GitHub stars~3.4k tokensUpdated yesterday
    Marketing & SEOAuto-check passed

  • Mvp Launch

    ooiyeefei/ccc

    Web app MVP launch checklist knowledge. An agent skill from ooiyeefei/ccc.

    495 GitHub stars~1.1k tokensUpdated 2 mo ago
    Marketing & SEOAuto-check passed

  • Launch Strategy

    freekmurze/dotfiles

    When the user wants to plan a product launch, feature announcement, or release strategy.

    1k GitHub starsUsed in 22 repos~3.1k tokens
    Marketing & SEOAuto-check passed

  • Gingiris Opensource

    Gingiris/gingiris-opensource

    🇺🇸 Open Source Marketing Playbook — How to get 10k+ GitHub stars.

    257 GitHub stars~1.4k tokensUpdated 5 mo ago
    Marketing & SEOAuto-check passed

More from minhnv0807/ai-business-skills

All 142 skills in this repo

  • Design Master

    minhnv0807/ai-business-skills

    Handles eight kinds of marketing visual requests, from logos and campaign key visuals to infographics and quote graphics, by generating images or writing paste-ready prompts.

    609 GitHub stars~4.6k tokensUpdated 29 days ago
    Auto-check passed

  • Offer Design

    minhnv0807/ai-business-skills

    Designs or repairs what a business sells, covering the promise, value stack, bonuses, guarantee, honest scarcity and a tiered ladder, rather than price or copy.

    609 GitHub stars~1.1k tokensUpdated 29 days ago
    Auto-check passed

  • Global SEO Growth

    minhnv0807/ai-business-skills

    Covers six SEO layers for a website: crawl and index audit, local SEO, search-intent content, AI search visibility, schema markup and backlink or directory distribution.

    609 GitHub stars~5k tokensUpdated 29 days ago
    Auto-check passed

  • B2B Lead Generation

    minhnv0807/ai-business-skills

    Plans B2B pipeline work from ICP definition and prospecting through lead scoring, outbound sequences, sales assets and MQL to SQL handoff, aiming at qualified pipeline.

    609 GitHub stars~1.2k tokensUpdated 29 days ago
    Auto-check passed

  • Community Seeding Plan

    minhnv0807/ai-business-skills

    Plans honest participation in outside communities such as Reddit, Discord and Facebook Groups, with a rules-based community list, roster, posts, replies and calendar.

    609 GitHub stars~3.2k tokensUpdated 29 days ago
    Auto-check passed

  • Ad Conversion Tracking Setup

    minhnv0807/ai-business-skills

    Sets up and verifies conversion tracking before ad spend: Meta Pixel and CAPI, Google Ads, GA4, TikTok, server-side GTM, consent mode, UTMs and a pre-launch checklist.

    609 GitHub stars~3.7k tokensUpdated 29 days ago
    Auto-check passed

Categories

Questions about 60 Launch Playbook Global

What does 60 Launch Playbook Global do?

A skill your agent uses when a launch needs a repeatable EXECUTION playbook — a T-30 to D+7 timeline, per-function checklists for content, design, ads, sales, and engineering, a launch-day war room…. 60 Launch Playbook Global is an agent skill from minhnv0807/ai-business-skills. Use when a launch needs a repeatable EXECUTION playbook — a T-30 to D+7 timeline, per-function checklists for content, design, ads, sales, and engineering, a launch-day war room, an escalation matrix, and roll-back criteria.

When should I use 60 Launch Playbook Global?

60 Launch Playbook Global fits situations like: A launch needs a repeatable EXECUTION playbook — a T-30 to D+7 timeline; per-function checklists for content; A launch-day war room; an escalation matrix.

How do I install 60 Launch Playbook Global in Claude Code?

Run `npx skills add minhnv0807/ai-business-skills --skill 60-launch-playbook-global -a claude-code`. Or copy the skill folder (skills/en/60-launch-playbook-global in minhnv0807/ai-business-skills) into .claude/skills/60-launch-playbook-global in your project. Claude Code loads it when a task matches its description.

How do I install 60 Launch Playbook Global in Codex?

Run `npx skills add minhnv0807/ai-business-skills --skill 60-launch-playbook-global -a codex`. Or copy the skill folder (skills/en/60-launch-playbook-global in minhnv0807/ai-business-skills) into .agents/skills/60-launch-playbook-global in your project. Codex loads it when a task matches its description.

Can I use 60 Launch Playbook Global in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add minhnv0807/ai-business-skills --skill 60-launch-playbook-global -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/60-launch-playbook-global, .gemini/skills/60-launch-playbook-global, .github/skills/60-launch-playbook-global and .opencode/skills/60-launch-playbook-global in your project.

What does 60 Launch Playbook Global need to run?

SKILL.md names no scripts, command-line tools or credentials: 60 Launch Playbook Global is instructions for the agent only.

Does 60 Launch Playbook Global access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is 60 Launch Playbook Global safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does 60 Launch Playbook Global use?

60 Launch Playbook Global is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does 60 Launch Playbook Global use?

About 3k tokens (SKILL.md is roughly 12k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to 60 Launch Playbook Global?

Skills that share tags, products or a category with 60 Launch Playbook Global: Gingiris Go Global (Gingiris-1031/Competitor-analysis-tool, 110 stars), Building Gtm System (GTM-Strategist/gtm-strategist-skills, 264 stars), Early Access Designer (aaron-he-zhu/aaron-marketing-skills, 2.9k stars) and Mvp Launch (ooiyeefei/ccc, 495 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains 60 Launch Playbook Global?

minhnv0807 (a GitHub user) maintains it in minhnv0807/ai-business-skills, which has 609 GitHub stars. The repository holds 142 skills in this directory. The repository was last updated on September 12, 2026.

Source: minhnv0807/ai-business-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.