菜单
Plan and execute an evidence-based product launch across Product Hunt, Hacker News, Reddit, email, social media, blogs, app stores, and owned channels. Use whenever the user is preparing a launch, submission, gallery, demo, launch calendar, launch-day runbook, analytics plan, or post-launch retrospective.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Discover and validate business opportunities from real customer evidence. Use whenever the user wants startup, SaaS, micro-SaaS, product, niche, or market ideas; wants to assess demand or competitors; or needs a ranked opportunity brief and validation plan.
Design repeatable community-led growth systems. Use whenever the user wants to grow an audience, build in public, launch in Reddit, Hacker News, Product Hunt, Discord, Slack, or niche groups, improve community engagement, or turn participation into qualified demand.
Generate, research, verify, and rank domain names with current registration checks, trademark-risk screening, language and security review, social-handle research, and registration guidance. Use whenever the user needs a product, company, app, project, or personal-brand name or wants to compare domains.
Build evidence-backed B2B account and prospect research for sales, partnerships, pilots, or customer discovery. Use whenever the user wants an ICP, target-account list, qualified leads, account scoring, buying signals, decision-maker roles, outreach angles, CRM-ready research, or deeper analysis of named companies.
Create an attorney-review-ready SaaS legal drafting package from an evidence-based data and product inventory. Use whenever the user needs a privacy notice, terms of service, cookie notice, acceptable use policy, DPA, CCPA/CPRA notice, vendor disclosure, or a gap analysis of existing legal pages. This skill flags issues and drafts language for review.
Scaffold a new Kungfu marketplace or internal maintenance skill with validated trigger metadata, only the necessary resources, correct plugin exposure, documentation, and complete repository checks.
| name | launch-guide |
| description | Plan and execute an evidence-based product launch across Product Hunt, Hacker News, Reddit, email, social media, blogs, app stores, and owned channels. Use whenever the user is preparing a launch, submission, gallery, demo, launch calendar, launch-day runbook, analytics plan, or post-launch retrospective. |
| category | business |
| license | MIT |
| compatibility | Live web access is required to verify current platform fields, limits, eligibility, and anti-manipulation rules before execution. |
Coordinate a launch that the product can support and that produces learning
after the announcement. This skill owns launch strategy, readiness, operations,
assets, analytics, and follow-through. Use product-launch-announcement-writer
for the detailed copy deck.
Assess:
| Area | Ready when |
|---|---|
| Product | Core path works with realistic data and known limitations are disclosed |
| Reliability | Monitoring, backups/rollback, incident owner, and status communication exist |
| Onboarding | A new user can reach first value without founder rescue, or high-touch help is planned |
| Positioning | Audience, problem, outcome, alternative, and differentiator are specific |
| Proof | Demo, real examples, or permissioned customer evidence supports the claims |
| Conversion | Pricing/CTA, signup, email delivery, attribution, and support flow work |
| Compliance | Privacy, terms, consent, claims, licenses, and platform rules are reviewed |
| Capacity | Someone can respond to users and incidents throughout the launch window |
Return launch, soft launch, delay, or cancel, with blockers and owners.
Do not delay merely for cosmetic perfection when the core learning loop is safe
and functional.
Write:
Choose channels based on audience presence and native intent. Do not post everywhere by default.
For each selected platform, record source URL, checked date, account eligibility, fields, limits, media specifications, promotional rules, and moderation risks.
Use current official Product Hunt guidance. As of the latest documented rules, makers should use eligible personal accounts, may schedule/create a draft, can select up to three categories, and should invite people to visit and join the discussion rather than directly asking for upvotes. Current guidance describes a short description field around 260 characters, but verify the live form because Product Hunt changes its workflow.
The product must be usable or meaningfully available; a page that only collects emails may not be homepage-eligible. Review the form guide immediately before submission.
Read current rules for Hacker News, Reddit, Slack/Discord groups, app stores, and newsletters. A native explanatory post usually performs better and is safer than a bare link. Disclose affiliation and do not coordinate artificial engagement.
Create a shot list that tells one coherent story:
Use realistic, permissioned data. Remove secrets, notifications, personal information, test accounts, and misleading dashboards. Verify current dimensions; Product Hunt has historically recommended 1270×760 gallery assets and multiple images, but the current interface is authoritative.
Prepare:
Use first-comment templates for structure, then make the comment specific and candid.
Build a time-sequenced runbook with owner, dependency, status, and fallback for:
Do not optimize solely for “12:01 AM Pacific.” Product Hunt’s day has historically followed Pacific time, but choose a launch time that preserves response coverage and verify current platform behavior.
During the launch:
Within one to three days, reconcile:
Publish a useful follow-up where appropriate, then schedule the next product or distribution experiment. Do not present correlation as causal uplift without a valid comparison.
Return:
product-launch-announcement-writer.