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

product-strategy-and-marketingproduct strategy AND marketing 搜索

Agent Skill

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

总安装

2,962

周安装

121

GitHub Stars

42

下载量

958
CodexClaudeCursorGemini CLI

安装说明

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

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/manojbajaj95/claude-gtm-plugin --skill product-strategy-and-marketing

简介

用于查找、检索和筛选相关信息。

  • 适合在 Codex、Claude、Cursor、Gemini CLI 中根据关键词、任务场景或来源线索快速定位候选结果。
  • 通过 npx skills add 命令从指定仓库安装,需结合原始 README 核验具体用法。
  • 安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。
  • product-strategy-and-marketing 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

SKILL.md

Product Strategy & Marketing

Unified product strategy skill — from vision and market opportunity through competitive positioning, growth loops, PLG, and product marketing context.


Philosophy

Great product strategy asks the right questions and makes reversible decisions quickly while being thoughtful about irreversible ones.

  • Start with the customer problem — not your solution
  • Create optionality — platform thinking enables multiple futures
  • Make trade-offs explicit — strategy is choosing what NOT to do
  • Systems over tactics — growth loops compound; growth hacks don't

Product Strategy Stack

┌─────────────────────────────┐
│          VISION             │  Where are we going? (3-10 years)
├─────────────────────────────┤
│         STRATEGY            │  How will we win? (1-3 years)
├─────────────────────────────┤
│          ROADMAP            │  What are we building? (Quarters)
├─────────────────────────────┤
│         EXECUTION           │  How are we building? (Sprints)
└─────────────────────────────┘

Product-Market Fit Spectrum

Level 0: Problem Fit    → You've found a real problem worth solving
Level 1: Solution Fit   → Your solution addresses the problem
Level 2: PMF            → Customers pull the product from you
Level 3: Scale Fit      → Repeatable growth engine working
Level 4: Moat Fit       → Defensible competitive advantage established

Market Opportunity Framework

TAM → SAM → SOM

MetricWhat It MeansHow to Calculate
TAMEveryone who could theoretically buyTarget customers × avg contract value
SAMThose you can reach and serveTAM × geographic/product constraints
SOMRealistic near-term shareSAM × realistic penetration (1-5%)

Always validate top-down with bottom-up: (realistic customers × conversion rate × ACV). If gap is >3x, revisit assumptions.


Working Backwards (PR/FAQ)

Amazon's product methodology: start with the customer outcome, work backward to the solution.

Write an internal press release BEFORE building anything. If you can't write a compelling press release, you don't have a compelling product.

PR/FAQ Structure

Press Release (~1 page):

  1. Headline — product name, one-sentence customer benefit
  2. Dateline + subheadline
  3. Opening paragraph — who is the customer and what problem is solved
  4. Problem paragraph — the current pain in detail
  5. Solution paragraph — what the product does
  6. Customer quote (fictional) — how it changes their life
  7. Company/founder quote — why this matters
  8. Getting started — how to begin
  9. Closing — call to action

FAQ (External + Internal):

  • External FAQ: Questions real customers would ask
  • Internal FAQ: Questions your skeptical colleagues would ask (the hard ones)

Anti-patterns to avoid:

  • Writing the PR after building (defeats the purpose)
  • Solution-first thinking — retrofitting a problem to your idea
  • Vague customer definition ("everyone could use this")
  • Skipping the hard internal FAQ questions
  • Marketing hyperbole instead of specific, measurable claims

For patterns and examples: see references/ directory


Competitive Positioning & Moats

Moat TypeDescriptionExamples
Network EffectsProduct improves as more users joinSlack, LinkedIn
Switching CostsPainful to leaveSalesforce, Workday
Data AdvantagesProprietary data improves productGoogle, Waze
Scale EconomiesCost advantages at scaleAWS, Stripe
BrandTrust and recognitionApple, Notion

Positioning template:

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

Competitive decision types:

  • Type 1 (irreversible): Business model, platform choice — take your time
  • Type 2 (reversible): Feature prioritization, pricing tiers — decide quickly

Growth Loops & PLG

Growth Loop Types

LoopMechanismKey Metric
ViralUsers invite usersK-factor
ContentUsers create discoverable contentIndexed pages
PaidRevenue funds acquisitionCAC payback
SEOContent ranks, drives trafficOrganic traffic
SalesPipeline → revenue → more repsACV/CAC

PLG Motion Types

MotionBest ForKey Lever
FreemiumSimple products, network effectsFree → paid conversion
Free TrialComplex productsTrial conversion rate
Reverse TrialHigh-value productsPremium feature discovery
Usage-BasedAPI/variable consumptionUsage expansion

North Star Metric Framework

A good North Star:

  • Measures value delivered to customers
  • Is a leading indicator of revenue
  • Reflects product strategy
  • Is actionable by the product team

*Examples: Slack → DAU sending messages; Airbnb → Nights booked; Figma → Weekly Active Editors*

AARRR Funnel

Acquisition → Activation → Retention → Revenue → Referral

Rule: Fix activation before optimizing acquisition. Filling a leaky bucket wastes spend.


Product Marketing Context

Before any marketing work, create .agents/product-marketing-context.md capturing:

  1. Product Overview — one-liner, what it does, product category, business model
  2. Target Audience — company type, decision-makers, primary use case, jobs to be done
  3. B2B Personas — user, champion, economic buyer, technical influencer (with pain + value promise)
  4. Problems & Pain Points — core challenge, why alternatives fail, cost of the problem
  5. Competitive Landscape — direct, secondary, and indirect competitors + how each falls short
  6. Differentiation — key differentiators, why customers choose you
  7. Objections & Anti-Personas — top 3 objections + who is NOT a good fit
  8. Customer Language — verbatim phrases for how customers describe the problem and your solution
  9. Brand Voice — tone, style, personality (3-5 adjectives)
  10. Proof Points — metrics, notable customers, testimonial snippets

Auto-draft approach (recommended): Study the repo (README, landing pages, marketing copy, package.json), draft a V1, then ask: "What needs correcting? What's missing?"

All other marketing skills reference this file automatically — create it once, update as needed.


Business Model Design

Revenue Model Options

ModelProsCons
SaaSPredictable, high LTVLong sales cycle
FreemiumLow CAC, viralFree → paid conversion hard
Usage-BasedScales with customerRevenue unpredictability
MarketplaceNetwork effectsHigh volume needed

Unit Economics

LTV = (Monthly Revenue per Customer × Gross Margin %) ÷ Monthly Churn Rate
Target: LTV > 3x CAC, CAC payback < 18 months

Key Strategic Questions

  1. Horizontal vs Vertical? — Serve many industries or dominate one deeply?
  2. High-Touch vs Self-Service? — Drives CAC, LTV, and scaling ability
  3. Niche vs Broad? — Start narrow, expand over time
  4. Premium vs Budget? — Rarely can do both
  5. First Mover vs Fast Follower? — Category size determines which matters

Anti-Patterns

  • Vision without strategy — inspiring destination, no map
  • Strategy without trade-offs — if everything is a priority, nothing is
  • TAM theater — unrealistic market sizes to impress investors
  • Feature parity obsession — chasing competitors instead of customers
  • Premature scaling — scaling before PMF
  • Optimizing acquisition before activation — filling a leaky bucket
  • Vanity metrics — MAU without engagement is meaningless

Related Skills

  • go-to-market-strategy — Launch planning and execution
  • pricing-strategy — Pricing decisions and packaging
  • sales-and-revenue-operations — Sales team, RevOps

适合场景

01

用户想查找某类 Agent Skill 时

02

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

03

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

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

能力 4

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

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

平台分布

Codex

32.74%
按下载量换算314

Claude

30.84%
按下载量换算295

Cursor

18.06%
按下载量换算173

Gemini CLI

8.92%
按下载量换算85

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

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

安装前确认

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

来源信息

继续浏览同类 Skills