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

gtm-positioning-strategyGTM 定位策略

Agent Skill

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

总安装

32,136

周安装

1,328

GitHub Stars

31,718

下载量

10,088
CodexClaudeCursorGemini CLI

安装说明

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

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/github/awesome-copilot --skill gtm-positioning-strategy

简介

gtm-positioning-strategy 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词快速定位候选结果时使用。

  • 它专注于产品市场定位策略,提供竞争分析和差异化方案。
  • 可通过 npx skills add 命令从指定 GitHub 仓库安装并使用该技能。
  • 安装前建议确认权限范围和维护状态,避免触发不必要的联网或文件操作。
  • 适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

SKILL.md

Positioning Strategy

Find and own a defensible market position. Turn generic messaging into clear differentiation — or at least test whether your differentiation actually resonates before committing to it.

When to Use

Triggers:

  • "Our messaging sounds exactly like competitors"
  • "Brand awareness is strong but conversion is weak"
  • "Sales team can't explain why we're different"
  • "Buyers see us as interchangeable"
  • "Should we reposition before we rebrand?"
  • "How do we test positioning claims?"

Context:

  • Competitive markets with similar offerings
  • Messaging that isn't converting
  • New product launches
  • Repositioning existing products
  • Sales team reports buyer confusion

Core Frameworks

1. One Word Can Change Everything (The "Autonomous" Problem)

The Pattern:

Early enterprise conversations for an autonomous AI product. Positioned as "autonomous AI agent."

Developers: "Cool, but scary." Managers: "Will this replace our team?" Deal progression: Slow. Lots of "we'll think about it."

The Change:

One word: "autonomous" → "AI teammate"

Same product. Same capabilities. Different framing.

Result:

Developers: "This helps me." Managers: "This makes my team more productive." Deal progression: Measurably faster.

Why This Matters:

Positioning isn't what you do. It's what you don't say.

We could've said "replaces developers" (technically true for some tasks). Would've killed every enterprise deal.

The Framework: Word Choice Shapes Buyer Psychology

Words that scare enterprises:

  • Autonomous (implies: no control, replacing humans)
  • Replaces (threatens: job security)
  • Fully automated (removes: human judgment)
  • AI-first (means: unclear, buzzword)

Words that convert:

  • Teammate (implies: collaboration, helping)
  • Augments (helps: makes humans better)
  • You stay in control (reassures: human oversight)
  • Handles repetitive work (specific: saves time)

How to Test Word Choice:

Don't guess. Test.

Test 1: Outbound Email A/B

  • Send 100 prospects Version A ("autonomous agent")
  • Send 100 prospects Version B ("AI teammate")
  • Measure: Reply rate, meeting booked rate
  • Signal strength: High (real buyer intent)

Test 2: Website Homepage A/B

  • Version A: Current positioning
  • Version B: New word choice
  • Measure: Click-through rate on key CTAs
  • Duration: 1-2 weeks minimum
  • Signal strength: Moderate (interest without commitment)

Test 3: Sales Call Scripts

  • Half of AEs use positioning A
  • Half use positioning B
  • Measure: Demo-to-trial conversion
  • Signal strength: High (real sales cycle)

Common Mistake:

Changing positioning based on internal consensus, not customer feedback. Your team isn't the buyer.


2. Test Before You Commit (Crawl-Walk-Run Positioning Rollout)

The Pattern:

Positioning changes create risk. Brand confusion. Sales misalignment. Customer churn (if existing customers don't recognize you).

De-risk through phased rollout:

Crawl Phase (1-2 weeks): Validation

Test messaging without committing product/org resources.

Actions:

  • A/B test website headlines (new vs incumbent)
  • Run two outbound email sequences (different positioning angles) to cold prospects
  • Ask existing customers: "If we described ourselves as [new positioning], would you still recognize us?"

Measurement:

  • Track CTR on web variants
  • Track reply rates on outbound sequences
  • Document qualitative feedback

Go/No-Go:

  • At least one positioning variant outperforms incumbent by 20%+ on reply rate
  • Existing customers don't say "wait, that's not what you do"
  • Proceed if clear winner; if tied, run longer or test new angles

Walk Phase (2-3 weeks): Alignment

If testing validates, align product and sales to new positioning (but don't rebrand publicly yet).

Actions:

  • Rewrite website copy (homepage, enterprise pages, CTAs)
  • Create sales enablement: updated pitch deck, call scripts, email templates
  • Update documentation to match new narrative
  • Build use-case-specific examples

Measurement:

  • Sales team feedback on messaging usability
  • Website analytics on engagement (not conversion yet)
  • Segment analysis (who's responding?)

Go/No-Go:

  • Sales team says new messaging is easier to use
  • CTR metrics improve vs incumbent
  • No major customer confusion
  • Proceed to Run

Run Phase (2-3 weeks and ongoing): Scale

Full commitment. This is the rebrand.

Actions:

  • Launch dedicated landing pages per use case
  • Outbound campaigns per positioning angle
  • Update all customer-facing materials
  • Train customer success team on new narrative
  • Announce repositioning (if appropriate)

Measurement:

  • Pipeline volume by positioning angle
  • Win rate by positioning angle
  • CAC efficiency by channel
  • Customer retention (did we lose anyone?)

Common Mistakes:

  • Skipping Crawl (jumping to full rebrand without validation)
  • Running phases in parallel (creates confusion if messaging changes mid-rollout)
  • Waiting for perfect product before repositioning (product should follow positioning, not precede it)
  • Not measuring at each phase (can't determine if test "won")

3. Positioning Clarity Diagnosis

The Pattern:

If your messaging closely resembles competitors' messaging, you have a positioning problem, not a product problem.

Positioning Failure Manifests As:

  • All competitors describe nearly identical value props
  • Differentiation requires explaining complex technical details
  • Buyers see offerings as interchangeable
  • Marketing metrics (CTR, engagement) weak vs industry benchmarks
  • Sales conversations get derailed by comparison questions

How to Execute:

Step 1: Competitor Messaging Audit

  • Collect homepage headlines from 5-7 direct competitors
  • Identify shared claims (these are commoditized)
  • Map where competitors claim unique value

Example:

If everyone says "fastest," "most reliable," "easiest to use" — these are table stakes, not differentiation.

Step 2: Assess Your Actual Strengths

  • What can you do that competitors can't, without massive R&D?
  • What do your best customers choose you for? (Ask them)
  • What structural advantages do you have? (Deployment model, data ownership, pricing, network effects, etc.)

Step 3: Find Under-Served Position

  • Where do existing solutions fail users?
  • What problem is everyone ignoring?
  • What buyer segment is under-served?

Step 4: Stake a Clear Claim

Must be:

  • Something you can own now (not future roadmap)
  • Something competitors can't easily copy (structural advantage)
  • Resonant with your best customer segments

Common Mistakes:

  • Claiming you're "better" at what everyone does (unbelievable)
  • Positioning on features competitors already have
  • Multiple positions simultaneously (choose one)
  • Waiting for perfect product before positioning shift

4. Market Positioning Architecture (Three Layers)

Layer 1: Market Context

  • What problem is the market experiencing?
  • Why is it experiencing this problem now?
  • What happens if problem goes unsolved?

Example: "Infrastructure teams manage increasingly complex deployments across hybrid environments. Organizations adopt microservices and distributed systems. This creates operational complexity that traditional monitoring tools can't handle."

Layer 2: Positioning Statement (1-2 sentences)

  • Who we serve: What customer segment?
  • What problem we solve: The specific pain
  • How we're different: Why we matter vs alternatives
  • Proof: Why should they believe us?

Example: "We help platform teams ship faster through [core capability] that connects [workflow A], [workflow B], and [business outcome] in real-time."

Layer 3: Narrative

Expand positioning into story:

  • Why the world is changing
  • Why existing solutions don't work
  • Why our approach is better
  • What the future looks like with us

How to Execute:

Write all three layers before testing. Test Layer 2 (positioning statement) first with Crawl-Walk-Run methodology. If that validates, build out Layer 3.


5. Headline and Sub-headline Testing

Principle: Clear positioning requires testable structure: headline (what are you?) + sub-headline (for whom? why?).

Main Headline Formats:

  • "The [adjective] [category] that [differentiator]"
  • "[Product] for [specific use case]"
  • "[Product] that [core benefit]"

Examples:

  • "The customizable platform for [workflow]"
  • "Infrastructure for autonomous teams"
  • "The enterprise-grade alternative to [incumbent]"

Red Flags:

  • Using competitor name (defensive, not confident)
  • Too technical (buyer won't understand)
  • Claiming multiple benefits (choose one)
  • Vague ("the future of X" — unbelievable)

Sub-headline Purpose:

Clarifies who, why, how it's different from status quo.

Examples:

  • "Deploy anywhere. Scale instantly. Your infrastructure, your rules."
  • "For teams drowning in repetitive work. Automation that handles the 80%, humans handle the 20%."
  • "Enterprise-grade. No lock-in. Works with your existing stack."

How to Test:

A/B test headline + sub-headline combinations:

  • Variant A: Current messaging
  • Variant B: New positioning angle
  • Variant C: Different differentiation claim

Measure CTR, reply rates, conversion.

Pick winner based on data, not opinion.


6. Positioning Defensibility Assessment

Principle: A positioning is only valuable if competitors can't easily copy it.

Defensibility Hierarchy:

1. Structural Advantage (Strongest)

  • Hard to copy: unique data ownership, deployment flexibility, pricing model, network effects
  • Example: "Built for regulated industries with on-prem deployment" (can't copy without rebuilding architecture)

2. Market Position (Strong if First)

  • Defensible if you own it first and scale
  • Example: "First AI platform for [specific workflow]" (copycats look derivative)

3. Product Feature (Weak)

  • Easy to copy: UX, specific capability
  • Example: "Faster API calls" (competitor ships speed improvement in 6 weeks)

How to Assess:

For each positioning claim, ask:

  1. Can competitor copy this with single product sprint? (Yes = not defensible)
  2. Do we have structural advantage? (No = temporary positioning)
  3. Is this credible given current product? (No = don't claim it yet)
  4. Can we own this position before competitors react? (No = too slow)

Common Mistake:

Positioning on features competitors can easily match. This creates positioning treadmill — you're always defending, never owning.


Decision Trees

Should We Reposition?

Is brand awareness strong but conversion weak?
├─ Yes → Positioning problem, test new angles
└─ No → Continue...
    │
    Does our messaging sound like competitors?
    ├─ Yes → Positioning problem
    └─ No → Not a positioning issue

Which Positioning Angle Should We Test?

Do we have structural advantage competitors can't copy?
├─ Yes → Position on structural advantage
└─ No → Continue...
    │
    Are we first in a category?
    ├─ Yes → Position on category ownership
    └─ No → Find under-served segment/use case

Should We Move from Crawl to Walk Phase?

Did new positioning outperform incumbent by 20%+?
├─ Yes → Move to Walk (alignment phase)
└─ No → Continue...
    │
    Did we run test long enough (2+ weeks)?
    ├─ No → Run longer
    └─ Yes → Try different positioning angle or stay with incumbent

Common Mistakes

1. Claiming to be "better" at what everyone does

  • Unbelievable. Find different angle.

2. Positioning on easily-copied features

  • Competitors will match. Need structural advantage.

3. Waiting for perfect product before positioning shift

  • Product work should follow positioning, not precede

4. Testing too many positioning angles simultaneously

  • Can't determine what's working. Test one at a time.

5. Skipping validation phase

  • Jumping to full rebrand without testing = risk

6. One positioning for all buyer personas

  • Different personas care about different things

7. Generic positioning that doesn't differentiate

  • "Best-in-class," "innovative" = meaningless

Quick Reference

Crawl-Walk-Run Testing:

  • Crawl (1-2 weeks): A/B test messaging, measure reply rates
  • Walk (2-3 weeks): Align sales/product to winning angle
  • Run (ongoing): Full repositioning, measure pipeline/conversion

Word choice that converts:

  • ✅ Teammate, augments, you stay in control
  • ❌ Autonomous, replaces, fully automated

Positioning audit steps:

  1. Collect competitor messaging
  2. Identify your actual strengths (ask customers)
  3. Find under-served position
  4. Stake clear, defensible claim

Defensibility hierarchy:

  1. Structural advantage (unique data, deployment flexibility, pricing model)
  2. Market position (category ownership)
  3. Product feature (weakest, easily copied)

Testing hierarchy (signal strength):

  1. Outbound reply rates (highest)
  2. Sales call conversion (high)
  3. Website CTR (moderate)

Related Skills

  • ai-gtm: AI-specific positioning (copilot vs agent vs teammate)
  • technical-product-pricing: Price as a positioning signal
  • 0-to-1-launch: Positioning for new product launches

*Based on positioning work at AI agent and developer platforms, including navigating the framing spectrum from "autonomous" to "AI companion" and how category framing changes enterprise buyer perception. Also includes Crawl-Walk-Run rollout methodology from repositioning products without breaking existing customer recognition. Not theory — patterns from testing positioning before committing to rebrands.*

适合场景

01

用户想查找某类 Agent Skill 时

02

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

03

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

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

能力 4

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

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

平台分布

Codex

36.41%
按下载量换算3,673

Claude

32.19%
按下载量换算3,247

Cursor

19.49%
按下载量换算1,966

Gemini CLI

9.34%
按下载量换算942

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

需要联网

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

安装前确认

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

来源信息

继续浏览同类 Skills