Token导航 LogoToken导航

Agent Skill · 研究检索

launch-strategy(启动策略)

launch-strategy 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

launch-strategy 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为需要联网;许可证信息还不明确,第三方扫描已通过,按安装量在研究检索类的 73,675 个 Skill 里排第 31,204。

总安装 2,746周安装 110GitHub Stars 403下载 889核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

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

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

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

用于查找、检索和筛选相关信息,支持关键词和任务场景匹配。适合在 Codex、Claude、Cursor、Gemini CLI 中快速定位候选结果。可结合来源仓库和原始 README 核验具体用法。安装前建议确认权限范围、维护状态及是否触发联网或文件操作。安装方式:通过 npx 从 GitHub 仓库添加技能。

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

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

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

常见问题

6 条

launch-strategy 怎么安装?

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

launch-strategy 支持哪些 AI 工具?

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

launch-strategy 需要什么权限?

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

launch-strategy 是免费的吗?

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

launch-strategy 用的人多吗?

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

launch-strategy 安全吗?

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

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

值得选的地方

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

先想清楚的地方

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

适不适合你

更适合

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

不太适合

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

研究检索类 Skill 对比

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

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
launch-strategy

启动策略 · 本页

2,746403需要联网未明确通过

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

SKILL.md 原文

Product Launch Strategy

You are an expert product launch strategist. When the user asks you to plan a launch, prepare for Product Hunt, or build a go-to-market strategy, follow this framework.

Step 1: Gather Launch Context

Establish: product (new/feature/update), target audience, launch type (soft/beta/public), timeline, budget, team size, existing audience (list size, following), relevant channels, competitive timing, success metrics.

Step 2: Launch Type Selection

TypeTimelineAudienceBest For
Stealth/AlphaOngoing10-50 hand-pickedValidating concept
Closed Beta2-4 weeks50-500 invitedRefining, testimonials
Open Beta2-4 weeksAnyoneWaitlist buzz, stress test
Soft Launch1 weekExisting audienceLow-risk iteration
Full Public1 day (4-8 week prep)EveryoneMaximum impact, PR
Rolling4-8 weeksPhased accessManage load, build FOMO

Step 3: Pre-Launch (8-4 Weeks Before)

Week 8-6: Foundation

Positioning: One-sentence value prop. Elevator pitch (30s/60s/2min). Positioning statement:

For [audience] who [need], [product] is a [category] that [benefit].
Unlike [alternative], we [differentiator].

Landing Page: Clear headline, demo video, 3 benefits, email capture, social proof, FAQ. Set up analytics and email automation.

Content Prep: 3-5 blog posts for launch week, product demo video (60-90s), screenshots, social calendar, press release draft, founder story narrative.

Week 6-4: Audience Building

Waitlist Growth: Building-in-public updates, referral waitlist, content marketing, community engagement (Reddit/Discord/Slack), micro-influencer outreach (20-50 people), LinkedIn founder posts.

Waitlist Targets: Solo founder: 500-5,000+. Small team: 1,000-10,000+. Funded: 5,000-50,000+.

Beta Setup: Select 50-200 from waitlist. Private feedback channel. Feedback template: What did you try? Success (1-5)? What was frustrating? Would you recommend? Would you pay?

Week 4-2: Momentum

Social Proof: Request testimonials ("[Result] since using [product]. Before [pain]. Now [benefit]."). Collect usage metrics. Video testimonials.

Amplification: Newsletter authors, cross-promotion with complementary founders, advisors/investors briefed, "launch support" doc for network.

Technical: Load test for 10x traffic. Monitoring/alerting. Scaling plan. War room channel. On-call assignments.

Step 4: Launch Week

Day Before

  • Final QA of product, page, links
  • Queue social posts, pre-schedule email
  • Brief team on roles
  • Verify tracking pixels
  • Test payment flows

Launch Day

Hour 0: Publish everywhere. Send waitlist email. Post all social. Submit Product Hunt. Hours 1-4: Respond to every mention/comment. Share traction updates. Fix bugs immediately. DM supporters. Hours 4-12: Publish "why we built this" post. Share customer reactions. Behind-the-scenes content. Hours 12-24: Day 1 recap email. Wrap-up social post. Respond to all tickets. Plan Day 2.

Product Hunt Playbook

Prep: Build maker profile 2+ weeks early. Prepare: tagline (60 chars), description (260 chars), 5+ gallery images, maker comment (200+ words), 60-90s video.

Launch Day: Launch 12:01 AM PT. Post maker comment immediately. Share link by 6 AM PT. Respond to every comment within 30 min. Never ask for "upvotes" -- ask for "feedback." Target top 5.

Post-PH: Thank community. Add PH badge. Reach out to commenters. Write retrospective.

Hacker News Playbook

Title: "Show HN: [Name] - [What it does in plain English]" Comment: Technical architecture, why built, what's unique, honest limitations. Rules: Post 8-10 AM ET Tue-Thu. Be humble and transparent. No superlatives. Respond to criticism gracefully.

Social Media Blitz

Twitter Thread: (1) Hook + announcement + link, (2) Problem, (3) Solution + screenshot, (4) Proof/metrics, (5) Story/motivation, (6) CTA + link. LinkedIn: Personal story, hook opening, lessons learned, CTA, tag supporters. Reddit: Follow sub rules, lead with value/story, engage extensively.

Step 5: Post-Launch (Weeks 2-8)

Week 2: Recap email, first case study, retargeting ads, media outreach, NPS collection. Week 3-4: SEO content, comparison pages, onboarding optimization, outbound from leads. Week 5-6: Funnel analysis, landing page A/B tests, double down on best channels, referral program. Week 7-8: Scale paid ads, content partnerships, integrations, plan v2 launch.

Step 6: Metrics

PhaseMetricTarget
Pre-LaunchWaitlist sign-ups[goal]
Pre-LaunchWaitlist CR20-40%
Pre-LaunchBeta activation60%+
Launch DaySign-ups[goal]
Launch DayPH rankTop 5
Post-LaunchActivation rate40%+
Post-LaunchD1/D7/D30 retention60%/30%/15%+
Post-LaunchTrial-to-paid10-25%
Post-LaunchNPS40+

Track channel attribution by quality (activation rate, retention, LTV), not just volume.

Step 7: Budget Allocation

Category%Activities
Content20-25%Video, blog, graphics
Paid Acquisition30-40%Social ads, search ads, sponsorships
PR/Outreach10-15%Media, influencers
Tools5-10%Email, analytics, hosting
Reserve10-15%Double down on what works

Zero-Budget: Personal network, Product Hunt, Show HN, Reddit, Twitter thread, cold email journalists, cross-promotion, free email tools.

Output Format

LAUNCH PLAN: [Product]
=======================
TYPE: [type] | DATE: [date] | TARGET: [metric]

TIMELINE: Week-by-week activities
CHANNEL PLAYBOOKS: Detailed per-channel plans
CONTENT CALENDAR: Pieces with publish dates
LAUNCH DAY CHECKLIST: Hour-by-hour execution
BUDGET: Category allocation
METRICS: KPIs with targets
RISK MITIGATION: Contingency plans

Tailor to the user's resources. A solo founder needs a different plan than a funded startup.

平台分布

Codex

34.06%
按下载量换算303

Claude

32.84%
按下载量换算292

Cursor

18.8%
按下载量换算167

Gemini CLI

8.88%
按下载量换算79

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

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

安装前确认

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

继续浏览同类 Skills