Token导航 LogoToken导航

Agent Skill · 待分类

product-launch(产品发布)

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

product-launch 是待分类类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为需要联网;许可证信息还不明确,第三方扫描已通过,按安装量在待分类类的 11,209 个 Skill 里排第 7,593。

总安装 353周安装 15GitHub Stars 7下载 124核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/jk-0001/skills --skill product-launch

这个 Skill 是做什么的

这个 Skill 的分类还没最终确定,用法以来源仓库的说明为准。

product-launch 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中围绕仓库状态和协作事项进行整理。适用于产品发布准备、市场推广计划和用户反馈收集等场景。能辅助整理发布流程和团队协作记录。

安装前建议确认权限范围、维护状态及是否触发联网或文件读写操作。可结合来源仓库和原始 README 进一步核验具体功能和使用方式。

来源仓库内路径:skills/product-launch

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/jk-0001/skills --skill product-launch;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要需要联网,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

product-launch 怎么安装?

在终端执行 npx skills add https://github.com/jk-0001/skills --skill product-launch。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

product-launch 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

product-launch 需要什么权限?

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

product-launch 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

product-launch 用的人多吗?

公开数据是累计安装 353 次,近一周安装 15 次,下载 124 次,GitHub 7 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

product-launch 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理待分类类任务、又不想每次都手写提示词的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

待分类类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
infsh-cli

infsh CLI · Codex、Claude

4,374,576382权限未标注未明确未收录
ai-video-generation

AI 视频生成 · Codex、Claude

4,313,376382调用外部服务未明确有提醒
lark-openapi-explorer

云雀 OpenAPI 浏览器 · Codex、Claude

2,064,1209,011需要联网未明确有提醒
lark-workflow-standup-report

Lark 工作流程站立报告 · Codex、Claude

2,041,6328,978需要联网未明确通过
use-my-browser

使用我的浏览器 · Codex、Claude

1,848,49140操作浏览器未明确未通过
product-launch

产品发布 · 本页

3537需要联网未明确通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

Product Launch

Overview

A launch is your best opportunity to create momentum, generate buzz, and acquire customers at scale in a short window. Most solopreneurs launch quietly and wonder why no one notices. This playbook shows you how to launch with impact — turning launch day into launch week, and launch week into sustained growth.


Step 1: Define Your Launch Goals

A launch without clear goals is just noise. Before planning tactics, answer:

What does success look like?

  • Revenue target? (e.g., $10K in first month)
  • User/customer target? (e.g., 100 signups, 20 paying customers)
  • Awareness target? (e.g., 10K impressions, 500 email signups)
  • Press/social mentions? (e.g., featured on Product Hunt, 3 industry blogs)

Pick 1-2 primary goals. Everything in your launch plan should ladder up to these.

Launch goal → Tactic mapping:

  • Revenue goal → Pre-sales, launch discounts, urgency
  • User growth → Free tier, viral loops, community activation
  • Awareness → PR outreach, influencer partnerships, paid ads
  • Validation → Beta program, early adopter interviews, feedback loops

Step 2: Build Your Pre-Launch Strategy (4-6 Weeks Out)

Great launches are won in the pre-launch phase. You build momentum BEFORE launch day, so when you hit "go," there's an audience ready to act.

Pre-launch timeline:

6 Weeks Before Launch: Build Your Waitlist

Create a simple landing page with:

  • Headline stating the problem + solution
  • Bullet points of key benefits
  • Email signup form ("Join the waitlist — launching [date]")
  • Social proof if you have any (testimonials from beta users, logos, early results)

Drive traffic to the waitlist from:

  • Your existing email list ("something new coming — sign up to get early access")
  • Social media (tease the launch, link to waitlist)
  • Relevant communities (Reddit, Slack, forums — if allowed, or via helpful engagement)

Goal: 50-200 waitlist signups by launch (or 10x your target customer count).

4 Weeks Before Launch: Create Launch Content

Prepare content to go live on launch day and the week after:

  • Launch blog post (the story, the problem, the solution, the demo)
  • Demo video (2-3 min walkthrough showing the product in action)
  • Social posts for launch week (7-10 posts across platforms)
  • Email sequence for waitlist (3 emails: 1 week before, launch day, 3 days after)
  • FAQ or help docs (so people can self-serve questions)

Rule: All content should be DONE 1 week before launch. Launch week is for execution, not creation.

2 Weeks Before Launch: Seed Early Reviews

Reach out to:

  • 5-10 people in your network who would be ideal customers
  • Ask them to try the product early (give them beta access or a preview)
  • Request honest feedback + a testimonial if they like it
  • If appropriate, ask if they'd share on launch day

Why this matters: Social proof on day 1 builds credibility. "Just launched!" with zero reviews = risky click. "Just launched — here's what early users are saying" = trust.

1 Week Before Launch: Notify Your Audience

Send an email to your list and post on social:

  • "Launching [Product] in 7 days"
  • Brief reminder of what it does
  • Exclusive launch offer or bonus (e.g., "First 100 customers get 30% off")
  • CTA: "Mark your calendar" or "Reply with questions"

Goal: Build anticipation. Prime people to act on launch day.


Step 3: Launch Day Execution

Launch day is a coordinated push across all channels. Treat it like an event, not a quiet announcement.

Launch day checklist (complete in this order):

  • 8 AM: Publish launch blog post on your site
  • 8:30 AM: Send launch email to waitlist ("We're live! Here's what's new.")
  • 9 AM: Post on Product Hunt (if relevant — tech/SaaS products perform well here)
  • 9:15 AM: Post on Twitter/X (thread format works best — announce, explain value, demo link, ask for RT)
  • 9:30 AM: Post on LinkedIn (longer post with story + value + CTA)
  • 10 AM: Post in 2-3 relevant communities (Reddit, Slack, Discord — add value, don't spam)
  • 12 PM: Respond to every comment, reply, and question across all channels
  • 6 PM: Send launch email to your main email list (not just waitlist — your full audience)
  • Throughout the day: Engage on social, thank supporters, amplify user posts

Launch day content structure (social posts):

HOOK: "Today's the day — we're launching [Product]!"

PROBLEM: "We built this because [specific pain point we kept hearing]."

SOLUTION: "Here's what it does: [3 key features or benefits]."

DEMO: "See it in action → [link to demo video or site]"

CTA: "Try it free / Grab the launch discount / Let me know what you think"

Pro tip: Schedule posts in advance so you're not scrambling. Use Buffer, Hootsuite, or native platform scheduling.


Step 4: Launch Week Momentum (Days 2-7)

Launch day is just the start. Most solopreneurs go quiet after day 1 and lose all momentum. Extend the launch into a full week.

Daily launch week content (1 post/day on social, 1-2 emails over the week):

  • Day 2: Share a customer testimonial or early result ("Here's what [User] said after trying it")
  • Day 3: Behind-the-scenes content ("Why we built this / What we learned building it")
  • Day 4: Feature deep-dive ("Here's how [Feature X] works and why it matters")
  • Day 5: Use case or case study ("How [Customer] uses [Product] to solve [Problem]")
  • Day 6: Objection handling ("Wondering if this is right for you? Here's who it's for — and who it's not for.")
  • Day 7: Last call + urgency ("Launch week ends tonight — grab your [discount/bonus] before it's gone")

Email sequence (to waitlist + main list):

  • Launch day: "We're live! Here's how to get started."
  • Day 3: "Already seeing results — here's an early win from [Customer]."
  • Day 6: "Launch offer ends in 24 hours — don't miss it."

Step 5: Post-Launch Follow-Up (Week 2+)

The launch window closes, but the work continues. Now you shift from hype to retention and iteration.

Week 2 priorities:

  • Thank everyone who supported the launch (email, DM, or public post)
  • Survey early customers ("What's working? What's confusing? What should we improve?")
  • Fix any critical bugs or UX issues that surfaced during launch
  • Analyze launch metrics (see Step 6)
  • Share a post-launch recap ("Here's what we learned from launch week")

Week 3-4 priorities:

  • Turn early customers into case studies or testimonials
  • Re-engage people who signed up but didn't convert (email: "Still on the fence? Here's what you need to know.")
  • Plan next content or feature announcement to maintain momentum
  • If launch went well, consider a second wave (submit to more directories, reach out to press, run ads)

Step 6: Measure Launch Success

Track these metrics to evaluate how the launch performed:

MetricWhat It Tells YouHow to Track
Waitlist signupsPre-launch interestLanding page analytics
Launch day trafficReach and attentionGoogle Analytics
Conversion rateTraffic → signups/purchasesAnalytics + CRM
Revenue (if applicable)Immediate $ impactStripe/payment processor
Email open/click ratesEngagement with launch emailsEmail tool (ConvertKit, Mailchimp)
Social engagementReach and amplificationPlatform analytics (Twitter, LinkedIn)
Customer feedbackProduct fit and satisfactionSurveys, support tickets, conversations

Post-launch review (1 week after):

  • Did you hit your primary goal(s)?
  • What worked better than expected? (do more of this)
  • What underperformed? (diagnose why — messaging? channel? timing?)
  • What would you do differently next launch?

Rule: Document your learnings. Every launch teaches you something. Write it down so you don't repeat mistakes or forget what worked.


Launch Strategies by Product Type

Different products benefit from different launch strategies.

SaaS Product Launch

  • Pre-launch: Waitlist + beta program (get 10-20 users testing before launch)
  • Launch channels: Product Hunt, Twitter, LinkedIn, email list
  • Launch offer: Free trial + launch discount (30% off first year for first 100 customers)
  • Post-launch: Onboard early users aggressively, collect feedback, iterate fast

Info Product / Course Launch

  • Pre-launch: Waitlist + free mini-course (5-day email course as lead magnet)
  • Launch channels: Email list (this is #1), YouTube, social
  • Launch offer: Early-bird pricing (20-30% off for first week)
  • Post-launch: Deliver value to first cohort, collect testimonials, open cart periodically

Service / Agency Launch

  • Pre-launch: Case study from pilot client + referral outreach
  • Launch channels: LinkedIn, email, direct outreach
  • Launch offer: Founding client rate (discounted for first 5 clients in exchange for testimonial)
  • Post-launch: Overdeliver for first clients, turn them into referral engines

Physical Product Launch

  • Pre-launch: Kickstarter or Indiegogo (if applicable) or pre-orders
  • Launch channels: Email, Instagram, TikTok, Facebook ads
  • Launch offer: Pre-order discount + limited edition bonus
  • Post-launch: Fulfill orders fast, request reviews, retarget buyers with upsells

Launch Mistakes to Avoid

  • Launching with zero audience. Build a waitlist first. Launching to silence is demoralizing and ineffective.
  • Launching without a clear offer or CTA. "We launched!" is not an offer. Tell people exactly what to do: "Sign up free", "Buy now", "Book a demo."
  • Going quiet after launch day. Launch is a week, not a day. Sustain momentum through Day 7.
  • Overpromising during launch. Hype is good, lies are not. Only promise what you can deliver.
  • Not following up with early users. Your first customers are your best advocates. Nurture them.
  • Skipping the post-launch review. If you don't analyze what worked, you'll repeat the same mistakes next time.

平台分布

Codex

34.33%
按下载量换算43

Claude

27.09%
按下载量换算34

Cursor

19.66%
按下载量换算24

Gemini CLI

9.82%
按下载量换算12

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

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

安装前确认

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

继续浏览同类 Skills