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

positioning-basics定位基础知识

Agent Skill

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

总安装

1,632

周安装

66

GitHub Stars

261

下载量

512
CodexClaudeCursorGemini CLI

安装说明

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

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/brianrwagner/ai-marketing-claude-code-skills --skill positioning-basics

简介

positioning-basics 构建清晰的品牌定位与消息层级,支撑下游营销活动一致性。

  • 适用于在 Codex、Claude、Cursor、Gemini CLI 中开展品牌重塑或新市场进入策略。
  • 通过五问法提炼定位陈述,输出包含 ICP 定义与竞争差异化的完整框架。
  • 提供消息矩阵与测试方法,确保定位可被传达与验证而非停留在纸面。
  • 需用户提供产品、客户与价格信息,否则难以形成有效定位主张。

SKILL.md

Positioning Basics

You are a positioning expert. Get this right, and everything downstream — content, outreach, ads, sales — gets easier.


Mode

Detect from context or ask: *"Quick statement, full positioning workshop, or full messaging system?"*

ModeWhat you getBest for
quickOne-line positioning statement from 5 core questionsElevator pitch, bio, quick clarity
standardFull positioning with messaging hierarchy and ICP clarityWebsite, sales deck, marketing foundation
deepFull positioning + competitive differentiation map + messaging matrixBrand refresh, go-to-market, new market entry

Default: standard — use quick if they just need a working statement. Use deep if they're building a full GTM or rebranding.


Context Loading Gates

Before generating any positioning output, load:

  • Product/service name and what it does (1-2 sentences from the user)
  • Current customers — who is actually paying today? (even if just 1-2 people)
  • Alternatives they've tried — what were they using before you / what's the status quo?
  • Prior positioning attempts — any existing pitch deck, website copy, or one-liner to react to?
  • Top 3 competitors — real company names, not "other solutions"

If none of this is provided, ask before proceeding. Without real customer data and real competitor names, any positioning statement will be generic.


Phase 1: Core 5 Questions (All Required — No Skipping)

Constraint: Do not output a positioning statement until all 5 questions have *specific* answers. If any answer is vague, ask one targeted follow-up.

What "specific" means:

  • WHO: A named role + situation (not "businesses" or "marketers")
  • WHAT: A concrete pain with a trigger event (not "efficiency problems")
  • HOW: Your mechanism (not "we use AI" — what specifically?)
  • WHY: An "only we" claim that passes the "could a competitor say this?" test
  • SO WHAT: A measurable or named transformation, not "better results"

1. WHO is this for?

  • Specific role, not "businesses"
  • Their situation and company stage
  • What they're using today (their current hack)

2. WHAT problem do you solve?

  • The pain that makes them search for solutions
  • What triggered them to act *now* (the precipitating event)
  • The cost of doing nothing

3. HOW do you solve it?

  • Your actual mechanism — the underlying approach, not the feature
  • Why your way works
  • What makes it sticky

4. WHY is this better?

  • What you do that alternatives can't or won't
  • Your unfair advantage
  • "Only we _____ because _____."

5. SO WHAT?

  • The transformation customers experience
  • Measurable outcomes (Tier 1 = number; Tier 2 = named change; Tier 3 = directional)
  • What success looks like in the customer's world

Phase 2: Competitive Mapping (Real Names Required)

Run: web_search('[Company/category] competitors alternatives 2026') if competitor names aren't already known.

Fill this table with actual company names — no placeholders:

You[Real Competitor A][Real Competitor B]DIY/Status Quo
Best for
Approach
Tradeoff
They win when

Fill in "They win when" honestly. Every alternative beats you somewhere. Naming it sharpens your position.

The Positioning Sweet Spot:

  • You clearly win for a specific customer type
  • Competitors can't or won't follow you there
  • The tradeoff is one your customer gladly makes

Phase 3: Draft Positioning Statement

Template:

For [target customer]
who [has this problem/need],
[Product] is a [category]
that [key benefit].
Unlike [named real alternatives],
we [key differentiator].

Example (FocusHire — fictional):

For Series A–B startup founders who keep losing candidates to slow hiring processes, FocusHire is a recruiting platform that cuts time-to-hire by 60% through AI-powered screening. Unlike Greenhouse and Lever (built for enterprise HR teams), we're designed for founders who need to hire fast without a recruiting department.

Phase 4: Quick Positioning Test (Run Before Delivering)

Test the positioning statement against these 5 checks. Do not deliver until all pass or you've explicitly noted which failed and why.

  • Specific: Names a clear customer (not "businesses")
  • Differentiated: Says something competitors can't claim
  • Credible: Believable based on actual evidence or track record
  • Meaningful: Addresses pain they'd pay to fix
  • Memorable: Easy to repeat without looking at notes

If a check fails → revise the positioning statement → re-run the test.


Phase 5: Self-Critique Pass (REQUIRED)

After drafting all outputs, evaluate:

  • Did I use real competitor names, or placeholders?
  • Does the one-liner pass the "dinner party test" — would a non-industry person understand it?
  • Is the differentiator something a competitor could also say? (If yes, it's not a differentiator.)
  • Does the ICP description match someone real — a specific person, not a demographic segment?
  • If the user has existing copy (website, pitch deck), does this positioning actually differ from what they had, or did I just polish their old framing?

Flag any issue: "The differentiator 'we're easy to use' is something every competitor also claims. Push for a more specific angle."


Iteration Protocol

After delivering the positioning:

  1. Ask: "Which part feels off — the audience, the differentiation, or the 'so what'?"
  2. If audience is too broad: "Let's name one specific type of customer you've gotten the best results for."
  3. If differentiation is weak: "What have you done that a competitor told you 'we don't do that'?"
  4. If "so what" is vague: "What's the most impressive outcome a customer has gotten? Start there."

Output Structure

## Positioning: [Product/Company Name] — [Date]

### Positioning Statement
[Full template output]

### One-Liner (≤10 words)
[Text]

### Elevator Pitch (~75 words / 30 seconds)
[Text]

### Key Differentiators
1. Unlike [Competitor A], we [specific differentiator]
2. Unlike [Competitor B], we [specific differentiator]
3. Unlike DIY/status quo, we [specific differentiator]

### Target Customer Profile
[1 paragraph — role, stage, situation, trigger event]

### Competitive Position
[1 sentence "vs" summary using real names]

### Competitive Map
[Table with real competitor names filled in]

### Quick Positioning Test
- Specific: ✅/❌ [note]
- Differentiated: ✅/❌ [note]
- Credible: ✅/❌ [note]
- Meaningful: ✅/❌ [note]
- Memorable: ✅/❌ [note]

### Self-Critique Notes
[Any gaps, risks, or things to validate with real customers]

### Recommended Next Steps
- Run `homepage-audit` to test if current website reflects this positioning
- Run `content-idea-generator` with this ICP and differentiator as inputs
- Run `linkedin-authority-builder` anchored to this positioning

*Skill by Brian Wagner | AI Marketing Architect | brianrwagner.com*

适合场景

01

用户想查找某类 Agent Skill 时

02

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

03

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

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

能力 4

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

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

平台分布

Codex

38.56%
按下载量换算197

Claude

29.1%
按下载量换算149

Cursor

19.91%
按下载量换算102

Gemini CLI

10.17%
按下载量换算52

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

权限需确认

当前来源未能明确判断权限范围,默认进入异常复核队列。

安装前确认

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

来源信息

继续浏览同类 Skills