Systems Lab

Agent skill

positioning

Establish product positioning and a messaging hierarchy grounded in competitive alternatives, differentiated capabilities, and the value those capabilities enable for a specific segment.

activeSelf-containedInstructions only1,088 words

Filed under Positioning and messaging.

From erickdronski/gtm-skills · 9 skill entries · 0 · pushed 2026-10-06

What it does when it runs

Establish product positioning and a messaging hierarchy grounded in competitive alternatives, differentiated capabilities, and the value those capabilities enable for a specific segment. Use this whenever the user asks about positioning, messaging, value proposition, how to describe or explain their product, what makes them different, homepage or category copy, an elevator pitch, a narrative, or says their messaging is not landing. Also use it when a description of the product is full of adjectives and short of contrast.

Automated analysis of the skill and the 0 files bundled beside it. A skill’s own description is written to be selected by an agent, so it describes the job and not the dependencies.

Keys and connectors you must supply
None found.
Hosts it reaches
No third-party host appears in the skill or its bundled files.
Tool permissions it declares
No allowed-tools in the frontmatter. It only issues instructions, so there is nothing to bound.
Actions present in the files
None. Instructions only.

Ask about positioning

Opens your assistant with this page's verified links already in the prompt.

Is this safe to install?ClaudeChatGPT
Adapt it to my stackClaudeChatGPT
What else do I need for it to workClaudeChatGPT
Rather ask a human? Talk to Cheetah
git clone --depth 1 --filter=blob:none --sparse https://github.com/erickdronski/gtm-skills.git /tmp/gtm-skills
git -C /tmp/gtm-skills sparse-checkout set "skills/positioning"
mkdir -p ~/.claude/skills/positioning
cp -R "/tmp/gtm-skills/skills/positioning/." ~/.claude/skills/positioning/

Picked up without a restart. A project skill of the same name is shadowed by your personal one. For one repository only, swap ~/.claude/skills for .claude/skills. Claude Code docs ↗

Or take the whole library

This repo ships a .claude-plugin manifest, so Claude Code can install all 9 skills at once. Plugin skills are invoked as /<plugin>:<skill>, so they never collide with your own.

/plugin marketplace add erickdronski/gtm-skills
/plugin

The folder is the same in every client that implements the format — 46 of them — so if yours is not above, only the destination changes.

Reproduced in full from erickdronski/gtm-skills/blob/ef1661418836049c4c5abad0c037f9c7e3fa7c6a/skills/positioning/SKILL.md, which is licensed MIT (repository). 1,088 words, 11 headings.

Positioning

Positioning is context-setting. It is the answer to a question the buyer asks before any of your features matter: what kind of thing is this, and compared to what?

Get it wrong and every downstream asset works against you. Buyers evaluate you on criteria that belong to a different category, your strengths read as irrelevant, and your team writes increasingly elaborate copy to compensate for a frame that was wrong at the start.

The single most useful reframe: you do not position against a competitor, you position against the alternative — which is very often a spreadsheet, an intern, or doing nothing at all.

The sequence

This follows April Dunford's method, which is the most reliable framework available for this, and its steps must run in order. Each one constrains the next, and skipping ahead to "what makes us different" without first establishing "different from what" is the failure mode this sequence exists to prevent.

1. Competitive alternatives

What would the customer do if you did not exist? Not "who are our competitors" — what would actually happen. Interrogate this hard, because it is where the real information is:

  • A named competitor
  • An in-house build or an existing internal process
  • A spreadsheet, a shared doc, a person doing it manually
  • Nothing — living with the problem

"Nothing" is the most common alternative and the hardest to beat, because it has no procurement cycle and no switching cost. If it is the primary alternative, the entire positioning has to be about the cost of inaction, and messaging built around beating a named competitor will miss.

Ask the user which of these actually shows up in lost deals. If they do not know, that is the first research task, and it is worth more than the rest of this exercise.

2. Unique attributes

What do you have that the alternatives do not? Capabilities, not adjectives. "Powerful", "intuitive", and "enterprise-grade" are things every competitor also claims, which means they carry zero information.

The test: could a competitor say this sentence about themselves without lying? If yes, delete it. What survives is usually shorter and much more specific than what the team started with — and that specificity is the entire asset.

3. Value those attributes enable

For each surviving attribute, ask "so what" until you reach something the buyer cares about independent of your product.

We index the codebase as a graph → so what → queries resolve across files → so what → the agent stops making changes that break callers three files away → so what → review time drops and fewer regressions ship.

Stop at the point where the buyer would nod without needing your product explained. Going further reaches generic business outcomes — "increase revenue" — that no longer distinguish you.

4. Who cares a lot

Which customers care disproportionately about that value? Not everyone who could buy — the segment for whom this is urgent.

Characteristics that make a segment care disproportionately are almost always structural: they have the problem at unusual scale, they have been burned by it recently, or they are regulated into caring. Find the structural reason and the targeting writes itself.

5. Market category

What context makes your value obvious? The category sets buyer expectations — what they compare you to, what they expect to pay, what checklist they evaluate against.

Three moves are available:

Play in an existing category. Easiest. Buyers already have budget and a frame. You have to win on their established criteria.

Position in a subsegment. "Observability, for agent workloads." Inherits budget while shifting the comparison set. Usually the right answer.

Create a category. Enormously expensive — you fund the education of the entire market. Correct only when no existing category makes your value legible, and you have the capital and the years. Most category creation attempts are subsegment plays that would have worked better labeled honestly.

6. Relevant trend, optionally

A trend can make the positioning feel urgent, but only if it is genuinely connected. Bolting a trend onto positioning it does not fit reads as opportunistic, and buyers are unusually good at detecting it.

Turning it into messaging

The positioning is internal. Messaging is what ships. Build the hierarchy in this order and keep it in one document:

One-line positioning statement — internal, precise, not customer-facing:

For [segment] who [situation], [product] is a [category] that [key value]. Unlike [primary alternative], it [key differentiator].

Value pillars — two to four, each stating a differentiated capability and the value it enables. Each pillar needs proof: a metric, a customer outcome, a demo moment. A pillar without proof is a claim, and claims are free.

Proof points — the specific evidence under each pillar. This is where the value case belongs.

Objection handling — the three objections that actually kill deals, and the honest response to each. Not rebuttals; responses. An objection you cannot answer honestly is a product roadmap item, and pretending otherwise wastes everyone's time.

Testing it

Positioning is testable, and most teams never test it:

  • Sales call test. Does a rep get further with it than without? The fastest signal available.
  • The "compared to what" test. Read the copy to someone unfamiliar. Ask what they think the alternative is. If they cannot say, the positioning is not doing its job.
  • The competitor test. Take your homepage headline, swap in a competitor's logo. Does it still read as true? If so, you have written a category description rather than a position.
  • The lost-deal test. Do lost deals cite reasons your positioning claims to address? If so, the positioning is not reaching them, or is not true.

Common failures

Positioning for the team instead of the buyer. Internal language, internal architecture, internal priorities. Buyers do not care how it works until they care what it does.

Leading with the category you wish you were in. If buyers put you in a category, you are in it. Fighting the frame from inside it never works; subsegmenting does.

Feature lists as positioning. A list of capabilities tells the buyer nothing about whether it is for them.

Changing it every quarter. Positioning compounds. Frequent changes reset the compounding to zero and confuse everyone who was starting to understand you.

Positioning against a competitor buyers have never heard of. If the buyer does not know the competitor, the contrast is invisible and you have spent your best sentence on nothing.

Other skills for the same job

Different authors, same problem. Matched on the words in the skill name, across every library in the catalogue except this one.

Need help setting it up?

This page tells you what positioning does and what it needs. Cheetah builds the agent setup it runs inside: data, CRM, sequencing and the guardrails.

Book a call →

The directory stays free. There is nothing gated behind this.