Token导航 LogoToken导航

Agent Skill · 研究检索

marketing-strategy(营销策略)

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

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

总安装 955周安装 39GitHub Stars 42下载 309核验 2026-05-01

安装说明

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

安装方式

通过对话安装

复制提示词发给支持本地命令或 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

这个 Skill 是做什么的

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

用于查找、检索和筛选相关信息。marketing-strategy 属于研究检索类 Skill,可作为该场景下的辅助能力补充。适合根据关键词或任务场景快速定位候选结果。可结合来源仓库和原始 README 核验具体用法。通过 npx 安装,支持 Codex、Claude、Cursor 和 Gemini CLI。

建议确认权限范围、维护状态及是否触发联网或命令执行。

来源仓库内路径:skills/marketing-strategy

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

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

常见问题

6 条

marketing-strategy 怎么安装?

在终端执行 npx skills add https://github.com/manojbajaj95/claude-gtm-plugin --skill marketing-strateg…。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

marketing-strategy 支持哪些 AI 工具?

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

marketing-strategy 需要什么权限?

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

marketing-strategy 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

marketing-strategy 用的人多吗?

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

marketing-strategy 安全吗?

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

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

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

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

营销策略 · 本页

95542需要联网未明确通过

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

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 mapping — Attribute → 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

平台分布

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