positioning
Skill70 starsChanged 11 days agoMITView on GitHub
Develops B2B SaaS positioning from your ICP, competitor and win-loss evidence. Maps what buyers compare you to, chooses between leading with a category or a problem, picks a primary and secondary anchor and up to three defensible differentiators, lays out 2 to 4 worked positioning options with a comparison canvas so you can decide, then locks the chosen one and tests it (clarity ladder, guarantee test). Triggers: "positioning", "how do we position", "what category are we in", "how do we differentiate from", "our homepage is confusing", "positioning options". Run before /messaging. Not for taglines or a messaging library (use /messaging).
We split this skill into the rules it gives an agent
5 rules. 0 are common, 3 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 14 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 25
Don't use it for taglines, value props or a full messaging library (/messaging, which runs after this), or for research you haven't done …
- Very specific: line 33
Paths: Write to context/positioning/MMYY-positioning.md.
- Distinctive: line 40
keep a legacy tool
- Distinctive: line 70
Use case: "We help [persona] [do the job] without [friction], by [approach]."
- Distinctive: line 84
No more than three differentiators, each one provable.
“Common” is measured: kept by at least 6 in 10 of the 14 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
Decide what you are, who it's for, what they'd use instead, and why you're the better choice, in words a buyer understands in five seconds. The method follows the public April Dunford school: start from the competitive alternatives buyers actually consider, and build out from there.
When to use it
- The homepage doesn't explain what you do, or demos start with "so what is it exactly?".
- You're choosing between going broad and niching down.
- A new product, a new segment, or a competitor that moved.
Don't use it for taglines, value props or a full messaging library (/messaging, which runs after this), or for research you haven't done yet.
Inputs
Required: company name, a short description and the website URL.
Recommended: context/icp/, context/competitors/, context/win-loss/ and context/expert-pov/. Positioning without ICP and competitor evidence is opinion. If those are missing, say so, run what you can, and offer /icp-research and /competitor-research first.
Paths. Write to context/positioning/MMYY-positioning.md. Agency or consultant? Swap context/ for clients/<client>/context/ throughout.
Steps
- Read the current state. Fetch the homepage, pricing and about pages. Run the five-second test: do the headline and sub-headline say what it is and who it's for? Note the category, differentiation and ICP the site claims today.
Map the alternatives. What would a buyer do if you didn't exist?
- do it manually
- keep a legacy tool
- buy a direct competitor
- stretch an adjacent tool
- do nothing
- build it with a general AI assistant
Rank them by how often they show up in deals.
Map the anchors. What could the positioning hang on?
- an activity
- a product category
- a use case
- a problem
- a persona
- a competitive alternative ("the X alternative for Y")
Score the promising combinations on clarity, differentiation and relevance to the ICP.
- Make the binary choice. Category-led (buyers already know the category and you win inside it) or problem-led (the category is new, crowded or wrong, so you lead with the pain). Use an activity anchor only when no software category fits.
Lay out the options. Take the top 2 to 4 combinations (3 by default) and work each one up:
- primary and secondary anchor
- a hero headline and sub-headline
- the value in three parts: category, problem, differentiation
- who it's for
- the bet it makes
- the risks
Each option must change the anchor or the binary choice. No rewording of the same bet.
- Build the comparison canvas. One column per option, rows for clarity, differentiation, ICP relevance, proof available, competitive exposure and risk. Mark each cell's confidence: verified, inferred, estimated or unknown. Recommend one and name the trade-off each option forces. The user decides.
- Lock the chosen option. Up to three differentiators, each one a thing you'd guarantee with money on the line (pass, partial or fail). Name the primary competitive alternative and the market focus, with simple TAM maths (average deal size × customers needed).
- Run the clarity ladder. Compress the position to one word, one phrase, one sentence and one paragraph. If a level fails, go back to the anchors.
- Write the positioning statement in the form that fits the anchor:
- Use case: "We help [persona] [do the job] without [friction], by [approach]."
- Category: "We are a [category] that [differentiator], unlike [alternative] which [weakness]."
- Alternative: "We're the [leader] alternative that [upgrade], for [persona] who [unmet need]."
- Activity: "We help [persona] [do activity], replacing [manual process] with [mechanism]."
- Map the implications. What changes for messaging, for the ICP, and which channel leads with which facet (homepage: primary anchor; comparison pages: the alternative; case studies: proof that matches the anchor).
- Hand off to
/messaging.
Output shape
Open with a TLDR (the one-sentence position) and one block of open decisions. Then: current state, alternatives, the options with the canvas, the committed position (anchors, differentiators with guarantee verdicts, statement, clarity ladder), implications, and sources. Each caveat is stated once.
What good looks like
- A stranger reads the hero and knows what it is and who it's for in five seconds.
- No more than three differentiators, each one provable.
- The comparison set matches the buyer. Compare to other vendors only when buyers already use the category.
- The options are real choices, not three phrasings of one idea.
- The TAM maths is realistic, not hopeful.
Mistakes to avoid
- "The platform for X" with nothing else.
- "AI-powered" as the main differentiator.
- Inventing a category nobody searches for.
- Choosing the position before mapping the alternatives.
- Differentiators you couldn't prove to a sceptical buyer.
Chain
Part of the free five-skill chain: /icp-research → /competitor-research → /tov-guidelines → positioning → /messaging. The other six context skills (company context, win-loss, founder POV, brand kit, funnel and goals) are in the paid context plugin ($19.99, link in the README).
Other versions17 projects use a version of this.
Word for word · 1
- matteotitta/repo-structure-in-house★ 70100% same
Edited · 1
- matteotitta/claude-marketing-context★ 097% same
Wrote their own version · 15
- RefoundAI/lenny-skills★ 1.3ksame name
- vercel-labs/marketing-team-eve-template★ 459same name
- nahid-sparktales/agent-dispatcher★ 59same name
- Infinite-Labs-AI/infinite-skills★ 43same name
- Dragoon0x/product-skills★ 4same name
- protocol/perun★ 2same name
- remigiusz-antczak/deep-code-review★ 2same name
- solanabr/startup-builder-skill★ 2same name
- buildingwithai/skills★ 1same name
- m-binimran/marketing-pack★ 1same name
5 more not listed
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 repository8 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- context/CLAUDE.mdCLAUDE.md
- outputs/CLAUDE.mdCLAUDE.md
- competitor-researchSkill
- icp-researchSkill
- levelSkill
- messagingSkill
- tov-guidelinesSkill
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.

