agentleFS
Sign inStart free
m-binimranm-binimran/marketing-pack/skills/positioning/SKILL.md

positioning

Skill1 starsChanged 5 months agoMITView on GitHub

Define product/brand positioning - target, category, differentiator, and proof - as the foundation every asset works from. Use at the start of a brand/campaign or when messaging feels muddled.

19 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use tov-guidelines, icp-research and 2 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • matteotittaSkill

    tov-guidelines

    Analyzes existing client content (website, blog, social, docs) to extract voice patterns, vocabulary preferences,

    Also in 4 projects that use this

  • growthack88Skill

    icp-research

    Scrapes case studies, testimonials, and solutions pages from a target website to build structured ICP documentation. Produces TAM analysis, firmographic segments, champion and economic buyer personas, use case mapping, customer proof points, and voice-of-customer synthesis with normalized attributes. Requires website URL as primary input. Upstream: recommended company-context. Downstream: feeds positioning, product-messaging, landing-page-copy, content-strategy, and outreach-emails.

    Also in 4 projects that use this

  • dachi-jp3Skill

    level

    表示レベル（auto / low / medium / high）を切り替える。

    Also in 3 projects that use this

  • YepAPISkill

    competitor-research

    Competitive analysis between domains using YepAPI.

    Also in 4 projects that use this

The file

Create a free account to mount
Files
SKILL.md

positioning

Positioning is the decision the rest of marketing executes. Get it sharp before writing copy.

Process (a positioning statement)

  1. Target: the specific customer who feels the problem most acutely.
  2. Category / frame of reference: what you're an alternative to (the mental shelf you sit on).
  3. Differentiator: the one thing you do better/differently that the target values - and competitors can't easily claim.
  4. Proof / reason to believe: why it's credible (substantiated - truth-claims).
  5. Statement: "For [target] who [need], [product] is the [category] that [differentiator], because [proof]."

Output

  • The positioning statement, the differentiator, the proof points, and the messaging hierarchy (1 core message
    • 3 supports) every asset should ladder up to.

Guardrails

  • Differentiate - avoid interchangeable category clichés ("easy, powerful, all-in-one").
  • Proof must be substantiated, not aspirational. One target, one core message.

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.

Check your setup, free