AGENT SKILLBY BRIANRWAGNER
Positioning basics
AT A GLANCE
Positioning basics is an agent skill for brand. Provides positioning expert. It is published by brianrwagner in the brianrwagner/ai-marketing-claude-code-skills GitHub repository (344 stars), which does not specify a license. Its SKILL.md runs to about 1,600 words. Install it with: npx skills add brianrwagner/ai-marketing-claude-code-skills --skill positioning-basics
- REPO STARS
- SOURCE REPOSITORY
- LICENSE
- Not specifiedCHECK THE REPO
- CATEGORIES
- SKILL.MD SIZE
- 9.8 KB284 LINES
QUICK ANSWER
- WHAT IT IS01
- Provides positioning expert. Its edge is a particular angle on brand and messaging, giving the agent tighter constraints than a plain positioning basics request.
- INPUTS02
- Context for brand and messaging: your goals, audience, constraints, and any source material the skill asks for.
- OUTPUT03
- A ready-to-use result for brand and messaging: the analysis, copy, or recommendations the agent produces.
INSTALL
One command adds this skill from its source repository.
npx skills add brianrwagner/ai-marketing-claude-code-skills --skill positioning-basicsREAD THE SKILL.MD BELOW BEFORE YOU RUN IT. SKILLS INSTRUCT YOUR AGENT.
SKILL.MD
The full file, as published in the source repository. Copy it, download it or open it on GitHub.
ON THIS PAGE · 22
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?"
| Mode | What you get | Best for |
|---|---|---|
quick | One-line positioning statement from 5 core questions | Elevator pitch, bio, quick clarity |
standard | Full positioning with messaging hierarchy and ICP clarity | Website, sales deck, marketing foundation |
deep | Full positioning + competitive differentiation map + messaging matrix | Brand 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:
- Ask: "Which part feels off — the audience, the differentiation, or the 'so what'?"
- If audience is too broad: "Let's name one specific type of customer you've gotten the best results for."
- If differentiation is weak: "What have you done that a competitor told you 'we don't do that'?"
- 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 positioningSkill by Brian Wagner | AI Marketing Architect | brianrwagner.com
Supporting file: SKILL-OC.md#
Platform: OpenClaw (token-optimized)
Required Inputs (collect before starting)#
- Product/service name + what it does (1–2 sentences)
- Current customers — who is actually paying today?
- Alternatives they've tried — what did customers use before?
- Prior positioning attempts — existing copy, pitch, one-liner
- Top 3 competitors — real company names
If none provided → ask. Without real customer data and real competitor names, output will be generic.
Mode#
| Mode | Output | Use when |
|---|---|---|
quick | One-line positioning statement from 5 questions | Elevator pitch, quick clarity |
standard | Full positioning + messaging hierarchy + ICP clarity | Website, sales deck |
deep | Full + competitive differentiation map + messaging matrix | GTM, rebrand |
Phase 1: Core 5 Questions (all required — no skipping)#
Do not output a statement until all 5 have specific answers.
- WHO — named role + situation + company stage + what they use today
- WHAT — the pain + trigger event that makes them act now + cost of doing nothing
- HOW — your actual mechanism (not "we use AI" — what specifically?)
- WHY — your "only we ___" claim (must fail the "could a competitor say this?" test)
- SO WHAT — transformation: Tier 1 = number, Tier 2 = named change, Tier 3 = directional
Phase 2: Competitive Mapping#
Run: web_search('[Company] competitors alternatives 2026') if names unknown.
Fill with real company names (no placeholders):
| You | Competitor A | Competitor B | DIY | |
|---|---|---|---|---|
| Best for | ||||
| Approach | ||||
| Tradeoff | ||||
| They win when |
"They win when" — fill this honestly. Naming it sharpens your position.
Phase 3: 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].Phase 4: 5-Check Test (run before delivering)#
- Specific — names a clear customer (not "businesses")
- Differentiated — says something competitors can't claim
- Credible — believable based on actual evidence
- Meaningful — addresses pain they'd pay to fix
- Memorable — easy to repeat without looking at notes
If any fail → revise → re-run test.
Self-Critique (required)#
- Used real competitor names, not placeholders?
- One-liner passes "dinner party test" (non-industry person understands it)?
- Differentiator is something a competitor CANNOT also say?
- ICP matches someone real, not a demographic segment?
- If user had existing copy — does this actually differ from their old framing?
Skill by Brian Wagner | AI Marketing Architect
FAQ
07 QUESTIONS
01What is the Positioning basics agent skill?
Provides positioning expert. It is listed under brand in the 100xLab agent skills directory.
02How do I install Positioning basics in Cursor, Claude Code, or Codex?
Run npx skills add brianrwagner/ai-marketing-claude-code-skills --skill positioning-basics in the project where you want it, then ask your agent for the skill by name. The --skill flag installs only Positioning basics, not every skill in the repository.
03What does the Positioning basics SKILL.md cover?
The SKILL.md includes sections on Mode, Context Loading Gates, Phase 1: Core 5 Questions (All Required — No Skipping), WHO is this for?, WHAT problem do you solve? and HOW do you solve it?. Read the full text on this page or in plain markdown at /resources/agent-skills/brianrwagner-ai-marketing-claude-code-skills--positioning-basics--m1wubk/raw.
04Which agents can use Positioning basics?
Positioning basics installs with the cross-agent skills installer (npx skills add), which sets it up for agents such as Claude Code, Cursor and Codex. Each agent loads the SKILL.md when you ask for the skill by name.
05What license is Positioning basics under?
No license was detected on the brianrwagner/ai-marketing-claude-code-skills repository, so the license is not specified. Check with brianrwagner before you redistribute or build on the skill.
06Is Positioning basics free to use?
Reading and installing Positioning basics costs nothing, because it is published in a public GitHub repository. The repository specifies no license, so ask brianrwagner before you reuse or redistribute it.
07Where is the source of Positioning basics?
Positioning basics comes from https://github.com/brianrwagner/ai-marketing-claude-code-skills, which has 344 GitHub stars. The SKILL.md is at https://github.com/brianrwagner/ai-marketing-claude-code-skills/blob/HEAD/positioning-basics/SKILL.md. The author is brianrwagner.
Need an agent workflow built around your stack?
Tell us the workflow you want automated. We reply within 4 working hours (IST).
ATTRIBUTION
Positioning basics was written by its original authors and is published in brianrwagner/ai-marketing-claude-code-skills (opens GitHub in a new tab) under no license stated in the repository. All rights stay with the original authors.
100xLab did not write, maintain or endorse this skill. This page lists it for discovery. Repo stars belong to the source repository, not to the skill. Review any skill before you install it.