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

marketing-strategy营销策略

Agent Skill

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

总安装

955

周安装

39

GitHub Stars

42

下载量

309
CodexClaudeCursorGemini CLI

安装说明

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

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

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

命令行安装

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

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

简介

用于查找、检索和筛选相关信息。marketing-strategy 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

  • 适合根据关键词或任务场景快速定位候选结果。
  • 可结合来源仓库和原始 README 核验具体用法。
  • 通过 npx 安装,支持 Codex、Claude、Cursor 和 Gemini CLI。
  • 建议确认权限范围、维护状态及是否触发联网或命令执行。

SKILL.md

Marketing Strategy

Strategy and positioning layer for B2B SaaS — from product-market fit through competitive intelligence, sales enablement, and growth loops. For launch execution and channel strategy, see go-to-market-strategy.


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)

Philosophy: Start with the customer problem, not your solution. Make trade-offs explicit — strategy is choosing what NOT to do. Systems over tactics: growth loops compound; growth hacks don't.


Product-Market Fit Spectrum

Level 0: Problem Fit    → 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

PMF validation signals: 5+ ICP customers, below-median sales cycle, above-median LTV, <5% churn, NPS 9–10.


Market Opportunity (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 × 1–5% penetration

Validate top-down with bottom-up: (realistic customers × conversion rate × ACV). Gap >3x → revisit assumptions.


ICP & Segmentation

ICP Firmographics (Series A sweet spot): 50–5,000 employees, SaaS/Tech/Professional Services, $5M–$500M revenue.

Buyer Personas:

  • Economic Buyer (VP/Director): Cares about ROI, cost reduction → business outcomes + case studies
  • Technical Buyer (Engineer): Cares about integration, security → architecture, uptime, SOC 2
  • Champion (Manager): Cares about ease of use → UX, quick wins

ICP Scoring (HubSpot): A (perfect fit) → D (poor fit). Focus acquisition on A/B, disqualify D.


Positioning (April Dunford Method)

  1. Competitive alternatives — What would customers do without you? (competitors, spreadsheets, DIY, status quo)
  2. Unique attributes — What do you have that alternatives don't?
  3. Value mappingAttribute → Value → Outcome (e.g., AI automation → eliminates manual entry → save 10 hrs/week)
  4. Best-fit customers — Who values this most? Use win/loss data.
  5. Market category — Head-to-head, niche ("CRM for agencies"), or new category
  6. Trend layer — What macro trend makes now the right time to buy?

Value proposition: [Product] helps [Target] [Achieve Goal] by [Unique Approach]

Positioning template:

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

Messaging hierarchy: One-liner → 3–5 key benefits → feature/outcome pairs → proof points (logos, stats, case studies)


Working Backwards (PR/FAQ)

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

Press Release structure (~1 page):

  1. Headline — product name + one-sentence customer benefit
  2. Opening — who is the customer and what problem is solved
  3. Problem paragraph — the current pain in detail
  4. Solution paragraph — what the product does
  5. Customer quote (fictional) — how it changes their life
  6. Getting started + CTA

FAQ (External + Internal): External = questions real customers would ask. Internal = questions your skeptical colleagues would ask (the hard ones).

Anti-patterns: Writing the PR after building, solution-first thinking, vague customer definition ("everyone could use this"), skipping the hard internal FAQ, marketing hyperbole instead of specific measurable claims.


Competitive Intelligence

Tiers: Direct competitors | Indirect/adjacent | Status quo (spreadsheets, DIY, do nothing)

Intel sources: Product trials, website monitoring, customer interviews, Gong/Chorus recordings, G2 reviews, competitor job postings, industry reports.

Battlecard template (one per competitor):

Competitor | Strengths | Weaknesses | Our advantages
When we win | When we lose
Talk tracks for top 3 objections
Proof points (case studies, review comparisons, win rate)

Update monthly. Distribute via Notion/Confluence to Sales, CS, Product.

Win/Loss process: Interview within 2 weeks of close. Track in HubSpot: reason, competitor, price factor, product gap. Share monthly insights report with product and sales.

Competitive moat types:

MoatDescriptionExamples
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

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

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

A good North Star measures value delivered, is a leading indicator of revenue, reflects product strategy, and is actionable by the product team. *Examples: Slack → DAU sending messages; Airbnb → Nights booked*

AARRR Funnel: Acquisition → Activation → Retention → Revenue → Referral. Fix activation before optimizing acquisition — don't fill a leaky bucket.


Business Model Design

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 × Gross Margin %) ÷ Monthly Churn Rate
Target: LTV > 3x CAC, CAC payback < 18 months

Sales Enablement

Core assets: Sales deck (15 slides, visual-first) · One-pagers (product, competitive, case study, pricing) · Battlecards · Demo script (discover → show → Q&A → next step) · Email sequences · ROI calculator

Enablement cadence:

  • Monthly: Competitive update call — product updates, battlecards, win/loss, best practices
  • Quarterly: Half-day workshop — positioning refresh, role-play, customer panel
  • New hire: 4-week ramp — company → ICP/messaging → competitive intel → demo certification

PMM handoffs: Demand Gen (2-week lead time) | Sales (48-hr SLA on competitive questions) | Product (weekly sync) | CS (1-week for launch enablement)


Product Marketing Context Document

Create strategy/brand.md (or .agents/product-marketing-context.md) capturing:

  1. Product Overview — one-liner, what it does, category, business model
  2. Target Audience — company type, decision-makers, use case, jobs to be done
  3. Buyer Personas — user, champion, economic buyer, technical influencer (pain + value promise each)
  4. Problems & Pain Points — core challenge, why alternatives fail, cost of the problem
  5. Competitive Landscape — direct, secondary, 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 customers use for 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: Study the repo (README, landing pages, marketing copy), draft V1, then ask: "What needs correcting? What's missing?"

All other marketing skills reference this file automatically.


PMM KPIs

KPITarget
Feature adoption (90 days)>40%
Win rate (competitive deals)>30%
Sales velocity-20% YoY
Deal size (ACV)+25% YoY
Launch ROMI3:1 (pipeline: spend)

QBR slide structure: Executive summary → KPI dashboard (target vs. actual) → what worked / what didn't → next quarter priorities + budget ask


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

适合场景

01

用户想查找某类 Agent Skill 时

02

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

03

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

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

能力 4

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

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

平台分布

Codex

38.55%
按下载量换算119

Claude

28.11%
按下载量换算87

Cursor

19.86%
按下载量换算61

Gemini CLI

9.54%
按下载量换算29

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

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

安装前确认

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

来源信息

继续浏览同类 Skills