positioning-messaging
Skill3 starsChanged 8 months agoMITView on GitHub
Build or refine B2B/SaaS positioning, message hierarchy, and proof points from customer pains, differentiation, and market context.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- Theo7777/gtm-skillstheir own version, first seen Sep 28, 2026
- kili-d/pmm-kittheir own version, first seen Jul 15, 2026
- CodeAlive-AI/ceo-ai-ostheir own version, first seen May 18, 2026
- Layneformalized225/ai-cofoundertheir own version, first seen Mar 22, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- CodeAlive-AI/ceo-ai-os★ 9same name
- kili-d/pmm-kit★ 2same name
- Layneformalized225/ai-cofounder★ 1same name
- Theo7777/gtm-skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository19 other files it gives its agents.
- customer-discovery-jtbd-synthesisSkill
- event-tracking-planSkill
- experiment-design-readoutSkill
- launch-planSkill
- north-star-metricSkill
- onboarding-activation-auditSkill
- positioning-messagingSkill
- pricing-packaging-hypothesisSkill
- retention-diagnosisSkill
- seo-geo-content-briefSkill
- customer-discovery-jtbd-synthesisSkill
- event-tracking-planSkill
- experiment-design-readoutSkill
- launch-planSkill
- north-star-metricSkill
- onboarding-activation-auditSkill
- pricing-packaging-hypothesisSkill
- retention-diagnosisSkill
- seo-geo-content-briefSkill
The file
We split this skill into the rules it gives an agent
10 rules. 0 are common, 10 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
10
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 9
Use this skill when the user wants clear product positioning, messaging architecture, or a sharper explanation of who the product is for …
- Distinctive: line 39
If anything is missing, infer cautiously and label it.
- Distinctive: line 46
Avoid jargon unless the audience clearly expects it.
- Distinctive: line 47
Prefer one strong message hierarchy over many weak claims.
- Distinctive: line 48
Ensure positioning can guide decisions, not just sound good.
- Distinctive: line 60
Write the painful before-state in customer language.
- Distinctive: line 163
If the product is product-led:
- Distinctive: line 164
ensure the user-facing message is stronger than buyer jargon
- Distinctive: line 166
avoid over-rotating toward executive ROI language too early
- Distinctive: line 168
If the product is enterprise:
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Positioning and Messaging
Use this skill when the user wants clear product positioning, messaging architecture, or a sharper explanation of who the product is for and why it wins.
What this skill must produce
Always produce:
- ICP and buyer/user framing
- Problem framing
- Alternative / competition framing
- Positioning statement
- Messaging hierarchy
- Proof points
- Tagline / headline options
- Risks / weak spots
- Next validation steps
Inputs to gather
If available, extract:
- product description
- target market
- user vs buyer distinction
- key pains / priorities
- category / alternatives
- unique strengths
- evidence / testimonials / outcomes
- current homepage / pitch / deck copy
- product motion (PLG / sales-led / hybrid)
If anything is missing, infer cautiously and label it.
Working rules
- Position around customer problems and desired outcomes, not feature inventory.
- Distinguish user, buyer, champion, and economic buyer when relevant.
- Make the differentiation believable.
- Avoid jargon unless the audience clearly expects it.
- Prefer one strong message hierarchy over many weak claims.
- Ensure positioning can guide decisions, not just sound good.
Step-by-step method
Step 1: frame ICP and audience roles
Define:
- ideal customer profile
- primary user
- primary buyer
- champion / internal advocate if relevant
Step 2: frame the core pain
Write the painful before-state in customer language. Then write the better after-state.
Step 3: frame the alternatives
List what customers do instead:
- status quo
- incumbent product
- workaround
- internal build
- adjacent category
Step 4: isolate true differentiation
Describe what the product does meaningfully better and why that matters.
Differentiate among:
- capability differentiation
- UX / workflow differentiation
- economic differentiation
- implementation / adoption differentiation
- strategic differentiation
Step 5: write the positioning statement
Use this structure:
For [target market] who [need/problem], [brand/product] provides [primary differentiated benefit] because [reason to believe].
Step 6: create the messaging hierarchy
Produce:
- one-liner
- homepage headline + subhead
- 3 supporting messages
- proof points under each
- objection handling
Step 7: create variants
Create versions for:
- end user
- buyer / executive
- technical evaluator (if relevant)
Output format
ICP and buyer/user framing
- ICP:
- Primary user:
- Primary buyer:
- Champion:
- Why this audience first:
Problem framing
- Current pain:
- Why it matters:
- Desired outcome:
Alternative / competition framing
| Alternative | Why customers choose it | Why it falls short |
Positioning statement
...
Messaging hierarchy
One-liner
...
Headline options
- ...
- ...
- ...
Subhead
...
Supporting messages
| Message pillar | What we claim | Why it matters | Proof needed |
Proof points
- Product proof:
- Customer proof:
- Economic proof:
- Credibility proof:
Objection handling
| Objection | Response |
Tagline / headline options
Provide 5-10 options.
Risks / weak spots
- Where the position sounds generic:
- Where proof is weak:
- Where differentiation may collapse:
- Where the wrong audience may be attracted:
Next validation steps
- customer interviews to run
- copy tests to run
- pages / deck / sales assets to update
Special instructions
If the product is product-led:
- ensure the user-facing message is stronger than buyer jargon
- emphasize end-user value and shareability
- avoid over-rotating toward executive ROI language too early
If the product is enterprise:
- produce both user-level and economic-buyer variants
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

