positioning-basics

Generate product positioning statements, competitive maps, and messaging hierarchies from structured questions.

3|1|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/ever-just/agentskills --skill positioning-basics-ever-just
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: positioning-basics
Source: https://github.com/ever-just/agentskills/tree/main/skills/white-paper-writing/ai-marketing-skills/positioning-basics
Command: npx skills add https://github.com/ever-just/agentskills --skill positioning-basics-ever-just

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Founders and marketers often produce vague positioning statements that name no specific customer, claim differentiators any competitor could also claim, and fail to articulate why buyers should act. This Skill enforces a structured method that turns real customer and competitor data into a specific, differentiated positioning statement. ## Core Features & Use Cases - Core 5 Questions Framework: Forces specific answers on WHO the customer is, WHAT pain triggers action, HOW the mechanism works, WHY it is defensible, and SO WHAT transformation results. - Competitive Mapping: Builds a comparison table with real competitor names, including an honest "they win when" column to sharpen the position. - Three Modes: quick for a one-line statement, standard for full positioning with messaging hierarchy, and deep for a full differentiation map and messaging matrix. - Use Case: A startup founder preparing a new website runs the standard mode, answers the five questions with real customer data, and receives a positioning statement, one-liner, elevator pitch, ICP profile, and competitive map that pass a 5-point quality test. ## Quick Start Help me create a positioning statement for my product using the positioning-basics skill, starting with the five core questions about my target customer and competitors.

Frequently Asked Questions about positioning-basics

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a positioning statement for my product?▼

Answer five core questions with specifics: who the customer is, what pain triggers action, how your mechanism works, why you are defensibly different, and what transformation results. Then fill the template: For [customer] who [problem], [product] is a [category] that [benefit], unlike [named alternatives], we [differentiator].

What makes a good value proposition versus a generic one?▼

A good value proposition names a specific role and situation, cites a concrete trigger event, and claims a differentiator competitors cannot also say. Generic ones target "businesses," promise "efficiency," and fail the test of whether a competitor could make the identical claim.

How do I define my ICP or ideal customer profile?▼

Define the ICP as a named role plus situation and company stage, including what they use today and the event that triggered their search. Avoid demographic segments; the profile should match a specific real person who has already paid or shown strong intent.

Can I do positioning without knowing my competitors?▼

No. The method requires real competitor names, not placeholders, because differentiation is only meaningful relative to actual alternatives. If names are unknown, run a web search for category competitors first, then map where each alternative wins.

Why does my positioning statement sound like every competitor?▼

The differentiator likely fails the "could a competitor say this" test, using claims like "easy to use" or "AI-powered." Push for an "only we" claim grounded in a specific mechanism, outcome, or customer segment that rivals cannot or will not serve.