agentleFS
narenaryannarenaryan/agent-skills/skills/marketing/marketing-positioning-tests/SKILL.md

marketing-positioning-tests

Skill0 starsChanged 41 days agoMITView on GitHub

Use when prospects misunderstand a product, messaging attracts poor-fit buyers, or a positioning or landing-page claim needs evidence before launch.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    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
  1. Distinctive:

    Ask buyers to paraphrase the product, intended buyer, outcome, and difference.

    line 28

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Marketing Positioning Tests

Buyer alternatives determine differentiators; differentiators enable value; value identifies best-fit buyers; category supplies the comparison frame. Copy expresses this dependency chain.

Evidence before wording

Build a claim ledger from interviews, lost deals, and product evidence. Separate facts from assumptions; record source, date, customer context, and counterevidence. Missing evidence requires research, not invented quotes.

DecisionEvidence required
AlternativeWhat buyers actually use or shortlist, including manual work
DifferentiatorCapability demonstrably absent or weaker in that alternative
ValueCustomer outcome enabled by that capability
Best-fit segmentObservable circumstances making that outcome important
CategoryFamiliar frame whose expectations the product can satisfy

Feature comparisons may not resolve migration costs or uncertainty about making the wrong purchase.

Testable recipe

  1. Draft two genuinely different positioning hypotheses. Keep price, offer, and visuals stable when testing wording.
  2. Recruit relevant buyers by problem and purchase context. Show each version without explanation; counterbalance presentation order when people see both.
  3. Ask buyers to paraphrase the product, intended buyer, outcome, and difference. Ask which claim needs proof and what prevents consideration, not which slogan they like.
  4. Record comprehension errors, expectations, relevance, and credibility separately. Preserve disconfirming responses rather than creating one preference score.
  5. Revise the weakest link. Treat qualitative results as diagnostic; validate any claimed conversion lift with an appropriately designed experiment and downstream quality metric.

Example hypothesis: “Release approvals for distributed engineering teams” needs evidence that cross-time-zone handoffs matter and that asynchronous approval reduces them. “Save ten hours weekly” remains unusable until substantiated.

Sources and scope

Pitfalls

  • Competitors found online may never enter buyers' consideration sets.
  • A new category adds an education burden; novelty alone is not differentiation.
  • Friendly existing customers can hide acquisition-stage confusion.
  • Preference scores do not establish lift, and stronger wording cannot repair unsupported claims.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.