Best for
- Use when positioning needs defining or sharpening — a statement built on Promise, Proof, and Path, a differentiation matrix against competitors, category entry points, a three-level message hierarchy, and tagline direct…
minhnv0807/ai-business-skills/skills/en/58-positioning-global/SKILL.md
Use when positioning needs defining or sharpening — a statement built on Promise, Proof, and Path, a differentiation matrix against competitors, category entry points, a three-level message hierarchy, and tagline directions. Trigger on 'positioning', 'positioning statement', 'what makes us different', 'USP', 'why should customers choose us over them', 'we sound the same as everyone else'. Also use when the user can list features but not a reason to pick them. Not for — competitor teardown resear
Decision brief
Positioning is not a pretty tagline. It is an explicit decision: who you serve, what you solve, and who you beat. Sharp positioning gives content an angle, ads a hook, and the team one story. Vague positioning makes everything generic. Run 08-competitor-research-global and 09-cu…
Compatibility matrix
| Platform | Status | Evidence | What to check |
|---|---|---|---|
| Codex | Not declared | No explicit evidence | Portability before use |
| Claude Code | Not declared | No explicit evidence | Portability before use |
| Cursor | Not declared | No explicit evidence | Portability before use |
| Gemini CLI | Not declared | No explicit evidence | Portability before use |
Installation
The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.
npx skills add https://github.com/minhnv0807/ai-business-skills --skill "skills/en/58-positioning-global"Inspect the Agent Skill "58-positioning-global" from https://github.com/minhnv0807/ai-business-skills/blob/958bd43b03afbc5afc42dfdb3fb2c087b23309e4/skills/en/58-positioning-global/SKILL.md at commit 958bd43b03afbc5afc42dfdb3fb2c087b23309e4. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.
Workflow
Six common directions — choose the one your real strengths can defend:
Read .agents/product-marketing-context-global.md and the Brand Hub if available. If missing, ask up to 4 questions:
1. Positioning requires a choice. You cannot be cheapest, most premium, and fastest at the same time. Pick one lead direction and accept losing the others. 2. Every claim needs proof. Differentiation without evidence is a slogan. Buyers do not believe it, and under FTC substanti…
Six common directions — choose the one your real strengths can defend:
Layer 1 — Full statement (internal, used in every brief):
Permission review
No configured static risk pattern was detected
This is not proof of safety. Runtime behavior, indirect dependencies, and hidden external systems are outside the static scan.
Evidence record
| Signal | Value | Evidence type | Meaning |
|---|---|---|---|
| Quality score | 93/100 | Computed | Documentation, specificity, maintenance, and trust rules |
| Repository stars | 553 | Source | Repository attention, not individual Skill quality |
| Compatibility | 0 platforms | Source | Declared in the catalog source record |
| Usage guide | automated source guide | Editorial | Generated or reviewed according to the visible evidence level |
Pinned source
Positioning is not a pretty tagline. It is an explicit decision: who you serve, what you solve, and who you beat. Sharp positioning gives content an angle, ads a hook, and the team one story. Vague positioning makes everything generic. Run
08-competitor-research-globaland09-customer-insight-globalfirst if you do not yet have competitor data and customer insight.
Read .agents/product-marketing-context-global.md and the Brand Hub if available. If missing, ask up to 4 questions:
Six common directions — choose the one your real strengths can defend:
| Strategy | Description | Example message direction |
|---|---|---|
| By attribute | Lead on one distinctive property | "The only CRM built for field service teams" |
| By price and quality | Premium, or value-for-money | "Agency-grade creative at in-house cost" |
| By use case | Own a specific situation | "Built for teams shipping weekly, not quarterly" |
| By user | Aim at one narrow buyer | "For solo founders doing their own marketing" |
| By category | Category creator or leader | "The first compliance layer for AI agents" |
| Against a competitor | Define yourself by contrast | "Not another course. A working system." |
Define your category: narrow enough to win, wide enough to have a market.
Two layers, use both:
Layer 1 — Full statement (internal, used in every brief):
For [target audience] — people who [specific pain or desire],
[brand/product] is the [category]
that helps them [core outcome],
unlike [competitor or alternative], because [real differentiator].
Layer 2 — Promise + Proof + Path (for content, sales, and landing pages):
| Component | Question | Example (DTC skincare) |
|---|---|---|
| Promise | What do you commit to, based on real customer insight? | "Know exactly what your skin needs before you spend on the wrong products" — not "effective skincare" |
| Proof | What evidence shows the promise is real? | Verified before/after photos, dermatologist review, third-party ingredient testing, published pricing with no hidden fees |
| Path | What steps does the buyer walk to get the promise? | 1. Free skin quiz > 2. Personal routine > 3. Follow the routine > 4. Reassess at 8 weeks |
The Promise fails if it is generic. The Path fails if the buyer cannot picture the next step.
Pull data from 08-competitor-research-global:
| Competitor / Alternative | Their positioning | Strengths | Weaknesses | How you differ (with proof) |
|---|---|---|---|---|
| Competitor A | ||||
| Competitor B | ||||
| Alternative (DIY or do nothing) |
Then lock 3 real differentiators — each a Claim plus its Proof:
| # | Claim | Proof / reason to believe |
|---|---|---|
| 1 | ||
| 2 | ||
| 3 |
Primary differentiator: one sentence. This is what every piece of content and every ad will reflect.
Market gap (what nobody does well yet): write it down explicitly so you can take it.
Category entry points are the situations that make a buyer think of the category and start looking. Strong positioning means being remembered first in those moments.
| Trigger situation | What the buyer is thinking or searching | How you want to be remembered | Content / channel that serves it |
|---|---|---|---|
| [e.g. breakout two weeks before a wedding] | [needs a fast fix, afraid of being scammed] | [transparent, diagnosis before selling] | [short-form diagnostic video, search] |
| [e.g. month-end and still no idea if we are profitable] | |||
| [e.g. current vendor raised prices or missed a deadline] |
Pick 2-3 priority entry points and map them to awareness stages: unaware (educate — name the problem) > problem-aware but not motivated (agitate) > solution-aware but undecided (compare — differentiate) > ready (close — offer).
| Level | Where it is used | Content |
|---|---|---|
| Level 1 — Core message | Headline, ad hook | Shortest possible: biggest benefit, clearest audience |
| Level 2 — Supporting messages | Body copy, landing page | 2A proof/social proof · 2B differentiation · 2C objection handling |
| Level 3 — Proof points | Testimonials, case studies | Specific numbers, real customer quotes, outcomes achieved |
Tagline directions: 3-5 options, each 5-8 words, anchored on the primary differentiator or the promise. Note which direction to test — the final tagline is chosen after message testing with real buyers, not in a meeting room.
File name: positioning-[product-name]-[YYYYMMDD].md
# Positioning — [Brand / product]
## 1. Positioning statement
- Full statement: "For... is the... that helps... unlike... because..."
- Promise: | Proof: | Path (steps):
## 2. Target segmentation
| Segment | Description | Main pain | Main desire | Priority |
| Primary / Secondary / Tertiary |
- Who this is NOT for:
## 3. Differentiation matrix
| Competitor | Their positioning | Strengths | Weaknesses | How you differ |
- 3 differentiators (Claim + Proof):
- Primary differentiator (one sentence):
- Market gap:
## 4. Category entry points
| Trigger situation | What they think | How you want to be remembered | Content / channel |
## 5. Message hierarchy
- Level 1 core message:
- Level 2 supporting (proof / differentiation / objection):
- Level 3 proof points:
## 6. Tagline directions
| # | Option (5-8 words) | Anchored on which differentiator | Test note |
## 7. Positioning map
[Two axes fitting the category — your position vs competitors — open space]
## 8. Rollout plan
| Where applied | What to update | Owner | Deadline |
| Ads / Landing page / Content pillars / Sales script / Brand Hub |
Pick two axes that fit the category (price x perceived quality; specialist x approachable; premium x mass; trust x entertainment). Read the map: crowded corners are brutal auctions; empty corners are open space you can take — but verify real demand exists there before jumping in.
08-competitor-research-global: run first — supplies the competitive landscape for step 3.09-customer-insight-global: run first — pain, desire, and triggers are the raw material for the Promise and entry points.31-offer-design-global: run after — offer architecture must align with positioning (do not position premium then discount everywhere).59-go-to-market-global: uses the positioning statement as the source message for the GTM plan.02-campaign-brief-global: the core message in the brief comes from message hierarchy Level 1.Frequently asked questions
Positioning is not a pretty tagline. It is an explicit decision: who you serve, what you solve, and who you beat. Sharp positioning gives content an angle, ads a hook, and the team one story. Vague positioning makes everything generic. Run 08-competitor-research-global and 09-cu…
The source record exposes this install command: npx skills add https://github.com/minhnv0807/ai-business-skills --skill "skills/en/58-positioning-global". Inspect the command and pinned source before running it.
Alternatives
alirezarezvani/claude-skills
App Store Optimization (ASO) toolkit for researching keywords, analyzing competitor rankings, generating metadata suggestions, and improving app visibility on Apple App Store and Google Play Store. Use when the user asks about ASO, app store rankings, app metadata, app titles and descriptions, app store listings, app visibility, or mobile app marketing on iOS or Android. Supports keyword research and scoring, competitor keyword analysis, metadata optimization, A/B test planning, launch checklist
KerberosClaw/kc_ai_skills
Use when the user wants to turn a Markdown report into a presentation-quality .pptx via interactive design decisions and a reusable hand-coded build script. Drives pre-analysis, global style choices, optional per-slide layout dialogue, python-pptx composition, and optional LibreOffice render self-check. NOT a generic auto-converter, NOT for PDF output, and NOT a fixed brand-template pipeline — brand integration is handled ad hoc through helper primitives.
elementalsouls/Claude-BugHunter
Comprehensive OSINT methodology for external red-team operations and authorized attack-surface assessments. Covers the 5-stage recon pipeline (seed discovery, asset expansion, enrichment, exposure analysis, reporting), asset-graph discipline with 29 asset types, severity rubric (CRITICAL/HIGH/MEDIUM/LOW/INFO), confidence upgrade workflows, time budgeting, asset-level triage rules, scale-based tactics, identity-fabric mapping (Entra/Okta/ADFS/Google/SAML/M365 Teams+SharePoint+OAuth), API and auth
maquina-app/rails-claude-code
Create comprehensive MVP documentation for Rails applications. Use this skill whenever a user describes a new app idea, wants to explore a SaaS concept, needs competitor research, or is starting a new project from scratch — even if they don't explicitly say "MVP". Triggers on "I have an idea for...", "I want to build...", "help me plan...", "research competitors for...", "create a business plan for...", "design a brand for my app", "set up Claude for my Rails project", "bootstrap an app", or any