Token导航 LogoToken导航TokenDH.com
待分类需要联网github未标认证来源可访问许可证需确认审计通过

launch-strategy启动策略

Agent Skill

launch-strategy 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

1,333

周安装

55

GitHub Stars

103

下载量

436
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:launch-strategy(启动策略)
来源仓库:https://github.com/borghei/claude-skills
仓库路径:skills/launch-strategy
安装命令:
npx skills add https://github.com/borghei/claude-skills --skill launch-strategy
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/borghei/claude-skills --skill launch-strategy

简介

launch-strategy 提供产品发布的完整执行手册,区分不同层级发布所需的营销投入与节奏。

  • 适用于产品与增长团队规划发布活动,可在指定宿主环境中使用。
  • 通过 npx skills add 从 GitHub 安装,具体阶段与工具见仓库文档。
  • 安装前建议确认权限范围与维护状态,注意是否触发联网或外部渠道调用。
  • 适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

SKILL.md

Launch Strategy

Category: Marketing Tags: product launch, feature release, Product Hunt, go-to-market, launch playbook, announcement strategy

Overview

Launch Strategy provides the complete playbook for launching products and features that build momentum, capture attention, and convert interest into users. A product launch is not an event -- it is a campaign with pre-launch, launch day, and post-launch phases. Shipping without a launch plan is leaving growth on the table.


Launch Tiers

Not every release deserves the same effort. Classify first.

TierWhat It IsMarketing EffortExamples
Tier 1: Major LaunchNew product, major pivot, rebrand4-8 weeks prep, all channelsNew product launch, platform launch
Tier 2: Feature LaunchSignificant new capability2-4 weeks prep, owned + select channelsMajor feature, integration, new plan
Tier 3: UpdateImprovement to existing feature1 week prep, owned channels onlyPerformance improvement, UI refresh
Tier 4: ChangelogBug fix, minor improvementSame day, changelog onlyBug fixes, minor UX tweaks

The rest of this skill focuses on Tier 1-2 launches. Tier 3-4 follow a simplified version of the same process.


Phase 1: Pre-Launch (4-8 Weeks Before)

Week 8-6: Foundation

Positioning & Messaging

  1. Define the one-sentence value prop for this launch
  2. Identify primary audience segment (who cares most about this?)
  3. Draft the headline you want to see in coverage
  4. Answer the "so what?" question -- why should anyone care?

Positioning Template:

For [target audience] who [need/pain point],
[product/feature] is the [category]
that [key benefit].
Unlike [alternatives],
we [key differentiator].

Asset Checklist:

  • Landing page copy and design
  • Product screenshots / demo video
  • Blog post (announcement)
  • Email announcement draft
  • Social media posts (per platform)
  • Press release / media pitch (Tier 1 only)
  • Internal FAQ for team
  • Customer FAQ

Week 6-4: Build Momentum

Audience Warming

  • Tease the launch in social posts (building in public)
  • Share behind-the-scenes development content
  • Engage with potential users about the problem you are solving
  • Collect early feedback from beta users

Waitlist / Early Access For Tier 1 launches, consider a waitlist to build anticipation:

Waitlist Landing Page Elements:
1. Clear headline: what is coming
2. One-sentence description: why it matters
3. Email capture form
4. Social proof: "Join [X] others waiting"
5. Expected launch date
6. Share incentive: "Move up the list by sharing"

Week 4-2: Prepare Channels

The ORB Channel Framework

Categorize every launch channel as Owned, Rented, or Borrowed:

Channel TypeDefinitionExamplesControl
OwnedYou control the audienceEmail list, blog, product (in-app), changelogFull
RentedYou pay for accessPaid ads, sponsorships, promoted postsHigh (while paying)
BorrowedYou earn access through othersPress, influencer mentions, community shares, Product HuntLow

Channel Strategy by Tier:

ChannelTier 1Tier 2Tier 3
Email (full list)YesYesSegment only
Blog postLong-formShort-formChangelog
Social mediaMulti-post campaignSingle announcementBrief mention
In-app notificationYesYesOptional
Product HuntIf applicableNoNo
Press / mediaTargeted pitchesNoNo
Paid amplificationBudget allocatedSmall budgetNo
Partner co-marketingIf applicableNoNo
Community postsHN, Reddit, DiscordHN maybeNo

Week 2-1: Final Prep

  • All assets created and reviewed
  • Landing page live (or ready to flip)
  • Email sequences loaded and tested
  • Social posts scheduled
  • Team briefed on launch plan and talking points
  • Analytics tracking configured for launch metrics
  • Support team briefed on new feature / expected questions
  • Rollback plan documented (if something goes wrong)

Phase 2: Launch Day Execution

Launch Day Checklist (Time-Boxed)

T-2 hours:

  • Final check: landing page, links, tracking all working
  • Team Slack channel open for coordination
  • Support team ready

T-0 (Launch):

  • Flip landing page / feature gate live
  • Send email announcement (Segment 1: most engaged users)
  • Publish blog post
  • Post on social media (all platforms, staggered by 30 min)
  • Submit to Product Hunt (if planned -- see PH section)
  • Post in relevant communities (HN, Reddit, Discord)
  • Notify partners for co-promotion

T+2 hours:

  • Check analytics: traffic, signups, errors
  • Respond to all social media comments/questions
  • Send email announcement (Segment 2: broader list)
  • Monitor Product Hunt ranking (if applicable)

T+6 hours:

  • Share early results with team
  • Address any support issues
  • Engage with community discussion threads
  • Schedule next-day follow-up content

End of Day:

  • Document day-one metrics
  • Thank early adopters publicly
  • Note any issues for immediate fix
  • Confirm next-day plan

Launch Day Communication Rules

  1. Respond to everything -- launch day is not the day to ignore comments
  2. Founder engagement -- CEO/founders should personally reply on HN, Reddit, PH
  3. Celebrate wins publicly -- share milestones as they happen ("500 signups in first 3 hours!")
  4. Address issues immediately -- if something breaks, communicate before people complain
  5. Never argue -- if someone criticizes, thank them and learn

Phase 3: Product Hunt Playbook

Product Hunt is a launch channel, not a launch strategy. It works best when combined with the full ORB approach.

PH Timeline

Week -4: Preparation

  • Create / update Maker profile
  • Engage genuinely in PH community (comment on other products)
  • Build relationships with active PH hunters
  • Draft listing: tagline, description, first comment, media

Week -1: Pre-Launch

  • Confirm launch date (Tuesday, Wednesday, or Thursday -- avoid Monday/Friday)
  • Prepare all PH assets:

- Thumbnail (240x240, clean, recognizable) - Gallery images (1270x760, show the product, not marketing fluff) - Demo video or GIF (under 60s) - First comment (personal, story-driven, not corporate)

  • Notify your network: "We are launching on PH on [date]"
  • Do NOT ask for upvotes (against PH guidelines and counterproductive)

Launch Day (12:01 AM PT)

  • Submit immediately after midnight PT (products are ranked by votes within a 24h window starting at midnight PT)
  • Post first comment within 5 minutes (this is your pitch)
  • Share across channels: "We launched on Product Hunt today" with direct link
  • Respond to EVERY comment on PH within 30 minutes
  • Engage authentically -- answer questions, thank feedback, acknowledge criticism

First Comment Template:

Hey PH! [Name] here, [role] at [Company].

We built [product] because [personal story about the problem].

[1-2 sentences about what it does and why it's different]

Here's what you get:
- [Key feature 1]
- [Key feature 2]
- [Key feature 3]

Special for PH: [offer -- extended trial, discount, early access to feature]

Would love your honest feedback. Happy to answer any questions!

PH Success Metrics

OutcomeWhat It Means
Top 5 of the dayStrong launch, badge, homepage visibility
Top 10 of the dayGood launch, still gets homepage traffic for 24h
Below top 10Minimal PH-specific value, but launch content still works elsewhere
Product of the week/monthSignificant ongoing PH traffic

Phase 4: Post-Launch Momentum (30 Days)

The launch is not over on day one. Most of the value comes from sustained post-launch activity.

Week 1 (Days 2-7)

  • Publish follow-up content: "What we learned from launching"
  • Share metrics publicly if impressive: "1,000 signups in 48 hours"
  • Create comparison pages: [Product] vs [Competitor A], vs [Competitor B]
  • Reach out to people who engaged on launch day for testimonials
  • Fix any issues reported on launch day

Week 2 (Days 8-14)

  • Publish case study or early user story
  • Create interactive demo or product tour
  • Submit to relevant directories and lists (G2, Capterra, AlternativeTo)
  • Pitch guest posts to relevant blogs / newsletters
  • Run retargeting ads to launch day visitors who did not convert

Week 3-4 (Days 15-30)

  • Publish "roundup" email to full list with launch highlights + social proof
  • Create SEO-optimized content around launch keywords
  • Analyze full launch funnel: what worked, what did not, what to repeat
  • Document launch playbook for next time (what you would do differently)
  • Plan next feature launch using learnings

Launch Metrics

Pre-Launch Metrics

MetricTargetSource
Waitlist signups500+ for Tier 1Landing page
Email list growth10%+ increaseEmail platform
Social engagement on teaser content2x normalPlatform analytics

Launch Day Metrics

MetricTargetSource
Landing page visitors5x normal dailyGA4
Signup/conversion rate5-15% of visitorsProduct analytics
Social shares/mentions50+Social monitoring
Product Hunt rankTop 5Product Hunt

Post-Launch Metrics (30 day)

MetricTargetSource
Total signups attributed to launch2-5x monthly averageAttribution
Activation rate of launch signupsMatch or exceed normal cohortProduct analytics
Press/blog mentions3+ organic mentionsGoogle Alerts
SEO keyword rankingsRanking for launch keywordsSearch console

Proactive Triggers

  • Feature ship date mentioned with no marketing plan: immediately ask about launch strategy
  • Waitlist or early access mentioned: design the full phased funnel, not just a landing page
  • Product Hunt considered: trigger the full PH playbook with the 4-week timeline
  • Post-launch silence: suggest momentum content if nothing published after day 3
  • Pricing change planned: treat it as a Tier 2 launch opportunity

Related Skills

SkillUse When
email-sequenceBuilding launch announcement and post-launch onboarding sequences
social-media-managerCoordinating social strategy around the launch
content-creatorWriting blog posts and landing page copy for the launch
analytics-trackingSetting up tracking for launch conversion metrics
ab-test-setupTesting launch page variants

Troubleshooting

SymptomLikely CauseResolution
Launch day traffic spike but near-zero signupsLanding page value proposition unclear or CTA buriedAudit landing page: headline must answer "what is this and why should I care" in 5 seconds
Product Hunt submission gets below 50 upvotesNo community warm-up, poor listing assets, or launched on wrong dayFollow 4-week PH playbook; launch Tue-Thu; ensure gallery images show product, not marketing graphics
Post-launch momentum dies by day 3No post-launch content plan; team assumes launch day is the endExecute 30-day post-launch plan with follow-up content, testimonials, and retargeting
Email open rate below 15% on launch announcementSubject line not compelling or list not segmented by engagementA/B test subject lines; segment by engagement (send to most engaged first, then broader list)
Support team overwhelmed on launch dayNot briefed on new feature or FAQ not preparedInclude support briefing and FAQ creation in pre-launch checklist, minimum 1 week before launch
Metrics dashboard shows no data on launch dayTracking not configured or UTMs not applied to launch URLsInclude tracking verification in final QA checklist, test all conversion events in staging first

Success Criteria

  • Launch readiness score above 80% on readiness checker before go-live decision
  • Launch day traffic at least 5x normal daily traffic
  • Signup/conversion rate between 5-15% of launch day visitors
  • 50+ social shares/mentions on launch day
  • Product Hunt top 5 finish (for Tier 1 launches using PH channel)
  • Post-launch 30-day signups at 2-5x monthly average
  • Activation rate of launch cohort matches or exceeds normal cohort within 10%

Scope & Limitations

In Scope: Phased launch planning (Tier 1-4), ORB channel strategy, Product Hunt playbook, launch day execution checklists, post-launch momentum campaigns, waitlist management, launch metrics tracking, launch readiness assessment.

Out of Scope: Product development and feature readiness (engineering responsibility), pricing strategy (see marketing-strategy-pmm skill), ongoing marketing operations (see marketing-ops skill), press and media relationship building (PR function).

Limitations: Launch success depends on product-market fit — no launch strategy compensates for a product that does not solve a real problem. Product Hunt effectiveness varies by product category; B2C and developer tools typically perform better than enterprise B2B. Post-launch metrics require 30 days minimum for meaningful assessment.


Scripts

ScriptPurposeUsage
scripts/launch_readiness_checker.pyAssess go/no-go readiness across positioning, assets, channels, team, trackingpython scripts/launch_readiness_checker.py checklist.json --tier 1
scripts/launch_timeline_generator.pyGenerate week-by-week launch timeline with tasks and ownerspython scripts/launch_timeline_generator.py --date 2026-04-15 --tier 1
scripts/launch_metrics_tracker.pyTrack actual vs target metrics across pre-launch, launch day, and post-launchpython scripts/launch_metrics_tracker.py metrics.json --demo

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

37.07%
按下载量换算162

Claude

30.56%
按下载量换算133

Cursor

19.93%
按下载量换算87

Gemini CLI

9.08%
按下载量换算40

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills