Token导航 LogoToken导航

Agent Skill · 研究检索

go-to-market-planner(前往市场规划师)

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

go-to-market-planner 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证为 MIT,第三方扫描已通过,按安装量在研究检索类的 73,675 个 Skill 里排第 52,782。

总安装 546周安装 23GitHub Stars 175下载 191核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

请帮我安装这个 Agent Skill:go-to-market-planner(前往市场规划师)
来源仓库:https://github.com/nicepkg/ai-workflow
仓库路径:skills/go-to-market-planner
安装命令:
npx skills add https://github.com/nicepkg/ai-workflow --skill Go-to-Market-Planner
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。不同来源提供的安装方式可能略有差异;本站展示可直接复制的安装命令,安装前请核对来源页面。

skills.shnpx skills
npx skills add https://github.com/nicepkg/ai-workflow --skill Go-to-Market-Planner

这个 Skill 是做什么的

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

go-to-market-planner 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中快速定位候选结果。适用于关键词搜索、任务场景匹配或来源线索梳理等研究检索场景。通过 npx skills add 命令从指定 GitHub 仓库安装并使用该技能。

安装前需确认权限范围、维护状态,以及是否会触发联网或文件读写操作。建议结合原始 README 和仓库路径进一步核验具体用法和功能边界。

来源仓库内路径:skills/go-to-market-planner

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

go-to-market-planner 怎么安装?

在终端执行 npx skills add https://github.com/nicepkg/ai-workflow --skill Go-to-Market-Planner。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

go-to-market-planner 支持哪些 AI 工具?

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

go-to-market-planner 需要什么权限?

权限级别是只读。该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

go-to-market-planner 是免费的吗?

来源标注的许可证是 MIT。本站不代收任何费用,也不托管安装包;能否商用、要不要署名,以许可证原文为准。

go-to-market-planner 用的人多吗?

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

go-to-market-planner 安全吗?

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

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

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 3 个目录同时收录,说明这个 Skill 流传比较广。
  • 许可证明确为 MIT,商用和分发边界好判断。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 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调用外部服务未明确有提醒
go-to-market-planner

前往市场规划师 · 本页

546175只读MIT通过

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

SKILL.md 原文

Go-to-Market-Planner

Plan and execute successful product launches.

Core Principle

Launch is a campaign, not an event. Build momentum before launch, peak at launch, sustain after launch.

5-Phase GTM Strategy

Phase 1: Market Positioning

Goal: Define how product fits in market landscape

Positioning Statement:

For [target customer]
Who [customer need/problem]
[Product name] is a [product category]
That [key benefit/differentiation]
Unlike [competitors]
Our product [unique value]

Competitive Analysis:

CompetitorStrengthsWeaknessesOur Advantage
Competitor AFeature XPriceBetter UX

Validation:

  • Target customer clearly defined
  • Differentiation identified
  • Positioning tested with 5+ customers

Phase 2: Messaging & Content

Goal: Create compelling launch messaging

Message Hierarchy:

  1. Headline: Core benefit in 5-10 words
  2. Sub-headline: How it works or who it's for (1 sentence)
  3. 3 Key Benefits: What users gain (feature → benefit)
  4. Social Proof: Testimonials, case studies, logos
  5. Call-to-Action: Clear next step

Content Types:

  • Launch blog post
  • Product demo video (2-3 min)
  • Landing page
  • Email announcement
  • Social media posts (5-10 ready)
  • Press release (if targeting media)

Validation:

  • Messaging tested with target customers
  • Content created 2 weeks before launch
  • CTAs clear and trackable

Phase 3: Channel Strategy

Goal: Identify where to reach target customers

Channel Options:

Owned Channels (free, full control):

  • Email list (existing customers/subscribers)
  • Blog and SEO
  • Social media (Twitter, LinkedIn)
  • YouTube

Earned Channels (free, limited control):

  • Press and media (TechCrunch, Product Hunt)
  • Influencers and partners
  • Community forums (Reddit, Hacker News)
  • Word of mouth

Paid Channels (cost, full control):

  • Google Ads (search intent)
  • Facebook/Instagram Ads (awareness)
  • LinkedIn Ads (B2B)
  • Sponsorships

Channel Prioritization:

1. Email list (highest ROI, existing audience)
2. Product Hunt (tech products)
3. Twitter/LinkedIn (organic + paid)
4. Google Ads (intent-based)
5. Press outreach (if newsworthy)

Validation:

  • 3-5 channels selected
  • Channel-specific content prepared
  • Budget allocated (if paid)

Phase 4: Launch Timeline

Goal: Coordinate launch activities

6-Week Launch Timeline:

Week -6 (Planning):

  • Finalize messaging and positioning
  • Create content (blog, video, landing page)
  • Identify launch channels
  • Set success metrics

Week -4 (Pre-launch):

  • Build waitlist or early access program
  • Create social media content
  • Reach out to press/influencers
  • Prepare email sequences

Week -2 (Warm-up):

  • Tease launch on social media
  • Send "coming soon" emails
  • Activate early access users
  • Final QA and bug fixes

Week 0 (Launch Day):

  • Publish landing page and blog post
  • Post on Product Hunt (12:01 AM PT)
  • Send launch email to full list
  • Share on Twitter, LinkedIn
  • Monitor and respond to feedback

Week +1 (Momentum):

  • Share user testimonials
  • Post case studies or results
  • Continue social media engagement
  • Analyze metrics, optimize

Week +2 (Sustain):

  • Publish post-launch analysis
  • Plan ongoing marketing
  • Iterate based on feedback

Validation:

  • Timeline documented with owners
  • Launch day checklist created
  • Post-launch plan defined

Phase 5: Metrics & Success Criteria

Goal: Measure launch effectiveness

Launch Metrics:

  • Awareness: Website visitors, social impressions
  • Acquisition: Signups, trial starts, purchases
  • Activation: Users who complete core action
  • Engagement: DAU/MAU, time in product
  • Revenue: MRR, conversion rate

Success Criteria (Define before launch):

week_1_goals:
  signups: 500
  trial_starts: 200
  product_hunt_ranking: top 5
  social_engagement: 1000+ interactions

month_1_goals:
  paying_customers: 50
  mrr: $5,000
  activation_rate: 40%
  retention_week_1: 60%

Post-Launch Review:

  • What worked? (double down)
  • What didn't? (stop or pivot)
  • Unexpected insights?
  • Next 30-day plan

Validation:

  • Success metrics defined
  • Tracking implemented
  • Daily monitoring during launch week
  • Post-launch review conducted

Launch Checklist

Pre-Launch (2 weeks before)

  • Landing page live with waitlist
  • Launch email drafted
  • Social media content scheduled
  • Product Hunt submission prepared
  • Press list compiled (if applicable)
  • Analytics and tracking set up

Launch Day

  • Product Hunt posted (12:01 AM PT)
  • Launch email sent
  • Blog post published
  • Social media posted
  • Community posts (Reddit, HN, etc.)
  • Monitor and respond to feedback
  • Track metrics in real-time

Post-Launch (Week 1)

  • Thank early adopters
  • Share testimonials and results
  • Engage with comments and questions
  • Analyze metrics vs. goals
  • Plan next 30 days

Launch Strategies

Product Hunt Launch:

  • Post at 12:01 AM PT (most visibility)
  • Engage in comments all day
  • Ask community for upvotes (tastefully)
  • Prepare "Hunter" if possible (influencer posts for you)

Press Launch:

  • Reach out 1-2 weeks before launch
  • Personalize pitches (not mass email)
  • Offer exclusive early access
  • Have assets ready (screenshots, quotes, data)

Email Launch:

  • Segment: existing customers vs. waitlist vs. cold leads
  • Subject line: Clear benefit, create urgency
  • Body: Problem → Solution → CTA
  • Send Tuesday-Thursday, 10 AM-2 PM for best open rates

Community Launch:

  • Be authentic, not salesy
  • Lead with value (solve a problem)
  • Engage genuinely in comments
  • Don't spam multiple communities same day

Common GTM Mistakes

❌ Launching without audience → Build email list first ❌ One-day launch, then silence → Sustain momentum ❌ No clear CTA → Make next step obvious ❌ Launching to everyone → Target specific segment first ❌ No success metrics → Define goals before launch ❌ Ignoring feedback → Respond and iterate quickly ❌ Over-promising → Set realistic expectations


Related Resources

Related Skills:

  • product-strategist - For validating market fit before launch
  • mvp-builder - For building product to launch
  • user-researcher - For understanding target customers

Related Playbooks:

  • PLAYBOOKS/launch-on-product-hunt.md - PH launch guide (when created)
  • PLAYBOOKS/press-outreach.md - Press strategy (when created)

平台分布

OpenCode

29.97%
按下载量换算57

Cursor

23.31%
按下载量换算45

Claude Code

17.16%
按下载量换算33

github-copilot

12.03%
按下载量换算23

Gemini CLI

8.22%
按下载量换算16

cline

3.5%
按下载量换算7

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。

继续浏览同类 Skills