Token导航 LogoToken导航TokenDH.com
研究检索需要联网github未标认证来源可访问许可证需确认审计通过

startup-go-to-market启动进入市场

Agent Skill

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

总安装

194

周安装

8

GitHub Stars

40

下载量

63
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/manojbajaj95/gtm-skills --skill startup-go-to-market

简介

startup-go-to-market 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。

  • 适用于初创企业市场进入策略、渠道选择或增长方案设计等场景。
  • 通过 npx skills add 命令从指定 GitHub 仓库安装,需确认权限范围和操作边界。
  • 建议结合原始 README 核验具体用法,注意是否会触发联网、命令执行或文件读写。
  • 使用前请检查维护状态,确保技能在当前宿主环境中可用且稳定。

SKILL.md

Startup Go-to-Market

Systematic workflow for designing and executing market entry, launch, and growth.

Modern Best Practices (Jan 2026): Start from ICP + positioning, pick 1-2 channels to sequence, instrument the funnel end-to-end, use AI for execution (not strategy), align RevOps across sales/marketing/CS.


When to Use

  • Designing go-to-market strategy for new product
  • Choosing between PLG and sales-led motion
  • Planning product launches (soft, beta, ProductHunt, full)
  • Defining ICP and channel strategy
  • Implementing AI-powered GTM automation

When NOT to Use


Quick Start (Inputs)

Ask for the smallest set of inputs that makes decisions meaningful:

  • Stage: pre-PMF, early PMF, growth, scale
  • Product and category: what it is, who uses it, and what "first value" looks like
  • ICP and buyer: firmographics, pains, procurement constraints, economic buyer vs champion
  • Pricing and economics: current/target ACV/ARPA, COGS drivers (include variable compute), payback constraints
  • Motion constraints: self-serve possible, sales cycle expectations, implementation/onboarding complexity
  • Channel constraints: budget, time, audience access (communities, lists, partnerships), geo, compliance limits
  • Baseline metrics: traffic, signup/demo rate, activation, retention, win rate, sales cycle length, pipeline
  • Team and tooling: who executes (founder/marketing/sales/CS), CRM + analytics stack

If numbers are missing, proceed with ranges + explicit assumptions and list what to measure next.

Workflow

  1. Define ICP and the buying path
  • Primary/secondary ICP, anti-ICP, trigger events, and an "activation" definition.
  • Use assets/icp-definition.md to draft.
  1. Align on positioning and proof
  1. Choose the motion (PLG / sales-led / hybrid)
  • Use the decision tree below for a fast cut.
  • For details: references/plg-implementation.md and references/sales-motion-design.md.
  1. Pick 1-2 channels to sequence (not parallelize)
  • Use a bullseye-style test plan: quick tests, measure, double down.
  • For execution details: references/channel-playbooks.md.
  1. Define measurement and RevOps alignment
  • Define shared lifecycle stages and the "one source of truth" for metrics (product + CRM).
  • Ensure handoffs are measurable (e.g., PQL -> SQL routing rules and SLAs for hybrid).
  1. Produce deliverables + operating cadence
  • Draft GTM plan (assets/gtm-strategy.md) and launch plan (assets/launch-playbook.md).
  • Run a weekly GTM review: 30 minutes on pipeline + funnel, 30 minutes on experiments, 30 minutes on decisions.

Decision Tree

GTM QUESTION
  |-- "How do I reach customers?" -> Channel Strategy
  |-- "PLG or Sales-led?" -> Motion Selection
  |-- "How do I launch?" -> Launch Planning
  |-- "Who is my ICP?" -> Segmentation
  `-- "How do I scale?" -> Growth Loops

GTM Motion Types

MotionDescriptionBest ForExamples
PLGProduct drives acquisition, conversion, expansionSMB, developersSlack, Figma
Hybrid (PLG + Sales-Assist)Product drives acquisition; sales assists conversion/expansionMid-market, higher ACV PLGAtlassian, Notion
Sales-LedReps drive deals through outbound/inboundEnterprise, complex salesSalesforce
Community-LedCommunity drives awareness and adoptionDeveloper tools, OSSMongoDB
Partner-LedPartners drive distributionEnterprise, geographic expansionMicrosoft

Motion Selection Framework

ACV < $5K and self-serve possible?
  - yes: PLG (add sales-assist for expansion)
  - no: is buyer technical?
      - yes: developer/community-led (bottom-up)
      - no: sales-led

ICP Components

ComponentQuestionsExample
FirmographicsSize, industry, geography50-500 employees, B2B SaaS, US
TechnographicsTech stack, toolsUses Salesforce, modern data stack
Pain indicatorsSymptoms of problemGrowing support tickets
Success indicatorsSigns of good fitStrong product-market alignment

ICP Scoring

FactorWeight
Budget available20%
Problem severity25%
Technical fit15%
Decision timeline15%
Champion identified15%
Expansion potential10%

Channel Strategy

CategoryChannelsBest For
OrganicSEO, content, social, communityLong-term
PaidSEM, paid social, displayFast, scalable
OutboundEmail, cold calls, LinkedInEnterprise, high ACV
ProductViral, freemium, PLGSelf-serve

Channel Sequencing by Stage

StagePrimary Channels
Pre-PMFFounder sales, communities
EarlyContent, outbound, founder network
GrowthPaid, SEO, partnerships
ScaleAll channels optimized

Measurement (Minimum Viable GTM Analytics)

  • Prefer lifecycle + cohorts over vanity metrics. Always break down by ICP/segment + channel.
  • Define a single funnel per motion (PLG vs sales-led) with clear stage definitions and owners.
  • Track leading indicators (activation/retention, PQL, win rate) before "scale" decisions.

PQL (Product Qualified Lead) Score:

PQL = (Engagement * 0.4) + (Fit * 0.3) + (Intent * 0.3)

Product-Led Sales (Sales-Assist) Basics

Use when PLG brings users in, but conversion/expansion benefits from a human touch.

PQL -> SQL routing checklist:

  • Define PQL triggers (events) and thresholds (e.g., 3 key actions in 7 days)
  • Define disqualifiers (students, competitors, tiny companies, unsupported geo)
  • Set an SLA for first touch (e.g., <24 hours for high-intent PQLs)
  • Define handoff criteria to AE (PQL -> meeting booked, security/procurement requested)
  • Instrument outcomes (PQL->meeting->pipeline->won) and review weekly

Launch Types

TypeGoalTimeline
Soft launchTest, iterate2-4 weeks
Beta launchBuild waitlist, feedback4-8 weeks
ProductHuntAwareness, early adopters1 day + prep
Full launchMaximum awareness1-2 weeks

Growth Loops

LoopMechanismExample
ViralUser invites usersDropbox referrals
ContentContent -> SEO -> UsersHubSpot
UGCUsers create contentYouTube
PaidRevenue -> Ads -> UsersPerformance marketing
SalesPipeline -> close -> revenue -> hiring -> more pipelineSales-led SaaS
PartnerEnable partners -> referrals -> deals -> partner revenue -> more partnersCloud marketplaces

Do / Avoid

Do

  • Define activation as concrete "first value moment"
  • Track leading indicators (activation, PQL, retention)
  • Use AI for execution while humans own strategy
  • Tier ICP based on fit + intent signals

Avoid

  • Content spam without measurement
  • "Do all channels" in parallel
  • Vanity metrics without retention context
  • Over-automating without human oversight
  • Scaling paid before activation/retention is stable
  • Treating benchmarks as targets without segmenting by ICP/channel

Resources

ResourcePurpose
channel-playbooks.mdDetailed channel execution
sales-motion-design.mdSales process + RevOps
plg-implementation.mdPLG execution + PQL frameworks
ai-gtm-automation.mdAI-powered GTM tools

Templates

TemplatePurpose
gtm-strategy.mdFull GTM strategy document
launch-playbook.mdLaunch planning
icp-definition.mdICP documentation

Data

FilePurpose
sources.jsonGTM resources

Related Skills

SkillUse For
startup-competitive-analysisMarket mapping, battlecards
startup-business-modelsPricing, unit economics
marketing-ai-search-optimizationGEO/AI search visibility for content-led GTM
marketing-social-mediaSocial channel execution
marketing-leads-generationLead acquisition

What Good Looks Like

  • One primary ICP with clear anti-ICP and measurable triggers (signals) for targeting.
  • A motion decision with explicit economics (ACV, payback, touch model) and defined handoffs.
  • One primary channel with a test plan, success metrics, and stop/pivot triggers.
  • Instrumented funnel from source -> activation/value -> revenue/expansion (by segment + channel).
  • A weekly operating cadence with a backlog of experiments and a written decision log.

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

38.38%
按下载量换算24

Claude

29.94%
按下载量换算19

Cursor

19.5%
按下载量换算12

Gemini CLI

9.8%
按下载量换算6

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

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

安装前确认

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

来源信息

继续浏览同类 Skills