Token导航 LogoToken导航

Agent Skill · 研究检索

launch-gtm-execution(启动 gtm 执行)

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

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

总安装 974周安装 41GitHub Stars 174下载 341核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/nicepkg/ai-workflow --skill launch-gtm-execution

这个 Skill 是做什么的

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

launch-gtm-execution 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词或任务场景快速定位候选结果时使用。适用于研究、信息搜集和线索筛选等需要精准匹配来源仓库内容的场景。

通过 npx skills add 命令从指定 GitHub 仓库安装,需结合原始 README 核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写操作。适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

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

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

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

常见问题

6 条

launch-gtm-execution 怎么安装?

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

launch-gtm-execution 支持哪些 AI 工具?

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

launch-gtm-execution 需要什么权限?

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

launch-gtm-execution 是免费的吗?

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

launch-gtm-execution 用的人多吗?

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

launch-gtm-execution 安全吗?

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

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

值得选的地方

  • 同时适配 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调用外部服务未明确有提醒
launch-gtm-execution

启动 gtm 执行 · 本页

974174需要联网MIT通过

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

SKILL.md 原文

Launch & Go-To-Market Skill

Master the art of successful product launches. From GTM strategy through launch execution, learn to coordinate teams, build momentum, and achieve market success.

Go-To-Market (GTM) Strategy

GTM Framework Decision

1. Direct Sales Model

  • Your team directly sells to customers
  • Best for: High ACV (>$10K), complex product
  • Sales cycle: 3-6 months
  • Team size: 1 AE per $500K-$1M ARR target
  • Examples: Salesforce, HubSpot, Workday

Pros:

  • Control over message
  • Deep customer relationships
  • Higher deal size possible
  • Custom solutions

Cons:

  • Expensive ($200K+ per rep)
  • Slower to scale
  • Long sales cycles
  • Small addressable market needed for ROI

Key Metrics:

  • Sales Qualified Lead (SQL)
  • Close rate (typically 20-40%)
  • Sales cycle length
  • Customer Acquisition Cost (CAC)

2. Self-Service / Freemium Model

  • Customers discover and sign up themselves
  • Best for: Low ACV (<$1K), self-explanatory product
  • Sales cycle: Minutes to days
  • Team: Product + Marketing focused

Pros:

  • Scales without sales team
  • Low CAC
  • Fast adoption
  • Land and expand opportunity

Cons:

  • High churn risk
  • Need viral/network effects
  • Requires excellent product
  • Difficult to reach enterprise

Key Metrics:

  • Free-to-paid conversion (2-5% target)
  • Monthly Recurring Revenue (MRR)
  • Customer Lifetime Value (LTV)
  • CAC < 30% LTV

3. Sales Development (SMB)

  • SDR/AE team for smaller deals
  • Best for: SMB market ($2K-$50K ACV)
  • Sales cycle: 1-3 months
  • Lower cost than enterprise sales

Pros:

  • Better ROI than enterprise sales
  • Faster sales cycles
  • Larger addressable market
  • Still personal touch

Cons:

  • Volume required
  • Lower margins
  • Churn challenges

4. Channel/Partner Model

  • Resellers, integrations, platforms
  • Best for: Reaching wide market cheaply
  • Examples: App stores, Zapier, AWS Marketplace

Pros:

  • Low CAC (partner pays)
  • Wide distribution
  • Established customer relationships

Cons:

  • Less control
  • Lower margins (revenue sharing)
  • Partner incentive alignment

GTM Positioning

Template:

For [target customer]
Who [customer problem]
The [product name]
Is [category]
That [primary benefit]
Unlike [alternative/competitor]
We [unique differentiator]

Messaging Hierarchy:

  1. Hero message (one sentence)

- "Collaborate in real-time, anywhere"

  1. Sub-message 1 (supporting feature)

- "Works offline, syncs when online"

  1. Sub-message 2 (why it matters)

- "No more lost work"

  1. Social proof

- "Used by 100K teams"

Target Customer Profile (ICP)

Define your ideal customer:

Company Characteristics:

  • Company size: 50-500 employees
  • Industry: SaaS companies
  • Revenue: $10M-$100M ARR
  • Geography: US + EU
  • Growth stage: Growth stage

Individual Buyer:

  • Title: VP of Operations
  • Reports to: COO/CFO
  • Budget owner: Yes
  • Decision timeline: 90 days

Why they'll buy:

  • Main pain: 40% time on manual process
  • Impact: Save $500K/year
  • Decision criteria: ROI, ease of use, support

Launch Planning (12-Week Timeline)

Weeks 1-4: Strategy & Preparation

Week 1-2: Launch Kickoff

  • Define launch goals (# signups, NPS, revenue)
  • Identify target segments
  • Competitive positioning finalized
  • Go/no-go criteria defined
  • Launch date locked

Week 3-4: Content & Collateral

  • Launch press release drafted
  • Product one-pagers created
  • Demo video script written
  • FAQ documentation started
  • Sales pitch refined

Weeks 5-8: Content Creation & Team Prep

Week 5-6: Marketing Preparation

  • Website landing page built
  • Email campaign drafted
  • Social media content scheduled
  • Influencer outreach list built
  • PR/media contact list built

Week 7-8: Team Training

  • Sales team training (2 days)
  • Customer success onboarding materials
  • Support team training
  • Executive briefing
  • Talking points finalized

Weeks 9-10: Beta & Feedback

Week 9-10: Beta Program

  • 50-100 beta users selected
  • Beta feedback system set up
  • Daily feedback review
  • Bug fixes prioritized
  • Product stability achieved

Weeks 11-12: Final Launch Prep

Week 11: Final Preparations

  • All content finalized and approved
  • Marketing assets tested
  • Sales collateral printed/digital ready
  • Support documentation complete
  • Systems and infrastructure scaling verified

Week 12: Launch Week Readiness

  • Final product testing complete
  • Team communication plan reviewed
  • Monitoring and alerts configured
  • Support team on high alert
  • Celebration planned!

Launch Week Execution

Launch Day Schedule

6:00 AM - Team Standup

  • Goals for the day
  • Potential issues
  • Communication channels

9:00 AM - LAUNCH

  • Press release goes out
  • Email campaign sends
  • Social media posts
  • Website live
  • Sales team activated

9:00 AM - 5:00 PM: Monitoring

  • Metrics dashboard live
  • Support team responding
  • Sales team following up
  • Marketing team posting
  • Exec team celebrating

5:00 PM - 9:00 PM: Close Monitoring

  • Continued metric tracking
  • Issue response
  • Team updates hourly
  • Press/media engagement

Post-Launch Week (Days 2-7)

Day 2 (Friday):

  • Performance review
  • Bug prioritization
  • Customer feedback analysis
  • Day 2 communication push

Day 3-5 (Weekend/Monday):

  • 24/7 support coverage
  • Customer success outreach
  • High-priority fixes
  • Feedback pattern analysis

Day 6-7 (Tuesday/Wednesday):

  • Retrospective planning
  • Performance vs goals review
  • Course correction planning
  • Team debrief

Sales Enablement

Sales One-Pager (2 pages)

Page 1:

  • Product/company logo
  • One-line pitch
  • 3 key features/benefits
  • Comparison vs competitors
  • Pricing

Page 2:

  • Customer testimonial/quote
  • Use case scenario
  • ROI calculator
  • Call to action
  • Contact info

Pitch Structure (3 minutes)

  1. Hook (15 sec)

- Current state: "Teams spend 40% time on manual sync"

  1. Problem (30 sec)

- Real impact: "Causes delays, errors, frustration"

  1. Solution (60 sec)

- How you solve: "We automate the sync process" - Key benefit: "Save 5 hours/week per team member"

  1. Social Proof (15 sec)

- Used by: "100 teams across industries" - Outcomes: "Avg 40% time savings"

  1. Call to Action (15 sec)

- Next step: "Let's run a quick 30-min POC with your team"

Objection Handling

Objection: "We're fine with current solution"

  • Response: "I understand. What if we could cut your manual sync time in half? Worth 20 minutes to see how?"

Objection: "We don't have budget"

  • Response: "What if this saves $50K in productivity? Would you make budget? Let's see if it applies to you."

Objection: "We need to evaluate competitors"

  • Response: "Smart. Here's how we compare to X and Y. What's most important to you - speed, ease of use, or cost?"

Sales Process

  1. Prospecting - Outbound/inbound leads
  2. Discovery Call - Understand needs
  3. Proposal/Demo - Show solution
  4. Negotiation - Pricing/terms
  5. Close - Customer acquisition!

Launch Metrics

Acquisition Metrics:

  • Sign-ups: [Target #]
  • Conversion rate: [Target %]
  • Cost per acquisition: [Budget]

Engagement Metrics:

  • DAU (Daily Active Users)
  • Feature adoption rate
  • Time in app

Retention Metrics:

  • Day 7/30 retention
  • Churn rate
  • NPS score

Business Metrics:

  • MRR (Monthly Recurring Revenue)
  • ACV (Average Contract Value)
  • Payback period

Troubleshooting

Yaygın Hatalar & Çözümler

HataOlası SebepÇözüm
Launch delayProduct not readyParallel tracks, beta extend
Low buzzInsufficient marketing4-week teaser campaign
Sales not readyLate enablementTraining week 6
Support overwhelmedUnder-staffedTemp staff, extended hours

Debug Checklist

[ ] GTM model clearly defined mi?
[ ] Target segments validated mi?
[ ] Messaging tested mi?
[ ] Sales team trained mi?
[ ] Support docs ready mi?
[ ] Rollback plan var mı?
[ ] Monitoring configured mı?

Recovery Procedures

  1. Launch Date Slip → Communicate early, propose new date
  2. Critical Bug → Activate rollback procedure
  3. Low Adoption → Accelerate marketing, CS outreach

Master launch execution and create market momentum!

平台分布

OpenCode

27.9%
按下载量换算95

Cursor

21.24%
按下载量换算72

Claude Code

18.73%
按下载量换算64

github-copilot

13.75%
按下载量换算47

Gemini CLI

8.69%
按下载量换算30

cline

3.24%
按下载量换算11

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

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

安装前确认

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

继续浏览同类 Skills