positioning-messaging-framework

positioning-messaging-framework is a skill for Claude Code from adam-lagerhausen/b2b-marketing-skills. It costs 30 tokens per session (1,970 once invoked), scanned A, a copy of positioning-messaging-framework, MIT.

A framework for deciding how a business product should be described to a specific customer group, and what messages and evidence support that description.

In plain words
What is it for?
It helps shape product or feature positioning, homepage and campaign messages, launch foundations, sales narratives, and reviews of existing positioning.
Why use it?
It separates the strategic choice of where a product fits from the wording used in ads, websites, and sales conversations. This reduces vague claims and messaging that sounds like every competitor.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the b2b-marketing-skills plugin — 9 skills shipped together

Good fit It helps shape product or feature positioning, homepage and campaign messages, launch foundations, sales narratives, and reviews of existing positioning.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/adam-lagerhausen/b2b-marketing-skills/positioning-messaging-framework
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add adam-lagerhausen/b2b-marketing-skills --skill positioning-messaging-framework
Clone the repo
git clone --depth 1 https://github.com/adam-lagerhausen/b2b-marketing-skills

Made for: Claude Code.

Or install b2b-marketing-skills, the plugin that ships this one along with the rest of its 9 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for positioning-messaging-framework

README.md
[![agentmods](https://agentmods.dev/badge/skills/adam-lagerhausen/b2b-marketing-skills/positioning-messaging-framework/github.svg)](https://agentmods.dev/skills/adam-lagerhausen/b2b-marketing-skills/positioning-messaging-framework)
Your own site
<a href="https://agentmods.dev/skills/adam-lagerhausen/b2b-marketing-skills/positioning-messaging-framework"><img src="https://agentmods.dev/badge/skills/adam-lagerhausen/b2b-marketing-skills/positioning-messaging-framework/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for positioning-messaging-framework

Your own site · 80×15
<a href="https://agentmods.dev/skills/adam-lagerhausen/b2b-marketing-skills/positioning-messaging-framework"><img src="https://agentmods.dev/badge/skills/adam-lagerhausen/b2b-marketing-skills/positioning-messaging-framework.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 30 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,970 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 94% copy Near-identical to another mod in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00030 $0.01970
Opus 5 $0.00015 $0.00985
Sonnet 5 $0.00006 $0.00394
Haiku 4.5 $0.00003 $0.00197

Measured 12d ago against content hash d2572d90ae9a, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

positioning-messaging-framework scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

This is a copy

94% identical to positioning-messaging-framework — 9 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

skills/positioning-messaging-framework/SKILL.md · 233 lines

How it starts

The opening of the file, as written. The whole thing — 233 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Positioning Messaging Framework

When to use

Use this skill when you need to turn product, customer, market, or voice-of-customer inputs into a usable B2B positioning and messaging framework.

Use it for:

  • New product or feature positioning
  • Repositioning an existing product
  • Homepage or campaign message strategy
  • Launch messaging foundations
  • Sales narrative inputs
  • Reviewing whether existing positioning is sharp enough

Do not use it to produce generic copy before the strategic choices are clear. Positioning comes first. Messaging turns that positioning into everyday English. Copywriting is the clear wording that gets the message across.

Required inputs

Ask for or infer these inputs. If an input is missing, state the assumption and mark confidence as low.

  • Product or company name
  • Product category or current market frame
  • Target segment and persona
  • Company attributes that make the segment specific
  • Customer economic goal
  • Customer qualitative or emotional goal
  • Current alternative, status quo, or vendor class
  • Pains and consequences of the current approach
  • Job to be done
  • Differentiated capabilities or model
  • Proof points, reasons to believe, or customer evidence
  • Business outcomes the product can credibly support
  • Words, phrases, or stories customers actually use

Core principles

  • Positioning is how you want customers to perceive the product and frame the decision versus a competitor, status quo, or alternative.
  • Messaging translates positioning into everyday English: the messages to get across, not just slogans.
  • The product is the tool. The thing customers buy is usually uptime, safety, reliability, revenue, efficiency, confidence, or the ability to say yes.
  • Always define a clear segment. Curate for the attributes you are optimizing for, and explicitly decide what you are not optimizing for.
  • If you can remove the company logo and replace it with a competitor, the positioning is not sharp enough.
  • Stories beat claims. Use concrete situations, consequences, and before/after change.
  • Avoid jargon, inflated claims, category mush, and copy that sounds like every SaaS homepage.

Read the full file on GitHub · 233 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 12d ago First seen · 233 lines · 30 tokens per session scan A d2572d90ae9a

Subscribe to this mod's changes

positioning-messaging-framework is a skill published in the GitHub repository adam-lagerhausen/b2b-marketing-skills (5 stars, last pushed 2mo ago), licensed MIT. It adds 30 tokens to every session and 1,970 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to positioning-messaging-framework, differing in 9 lines, and is treated as a copy.

Related

Other skills, from other repositories

go-to-market-playbook

A reusable Go-to-Market strategy template for both B2B and B2C launches. Covers positioning, messaging, ICP definition, channel selection, and competitive analysis frameworks. By @WeiYipei.

Gingiris-1031/gingiris-skills · 48 tokens

adoption-leaderboard

Scores a rep's or a team's recent sales calls against a fixed set of five winning-behavior checklists (rapport, upsell signals, renewal risk, customer experience, value realization), then ranks reps lowest-adoption-first so the highest-leverage coaching targets lead. Use when running a team calibration, prepping 1:1…

zime-ai/zime-gtm-skills · 96 tokens

challenger

Audits a B2B sales call transcript against the Challenger Sale framework (teach, tailor, take control, plus the commercial-teaching pitch arc), or sweeps a CRM export for deals with no teaching insight logged. Use when a rep leans on discovery-question skill but rarely brings a point of view, when prepping a rep for a…

zime-ai/zime-gtm-skills · 104 tokens

champion-tracker

Tracks champion strength across a deal's call(s) — builds an action ledger, one row per named contact per cited quote, tagging each as either an act of internal selling (looping in a stakeholder, pushing back for the rep in a room the rep wasn't in) or mere positive sentiment (encouraging words, no action), then reads…

zime-ai/zime-gtm-skills · 112 tokens

end-client-registration

Audits a partner/reseller's end-client deal registration for completeness — partner identity, end-client entity kept distinct from the partner, engagement scope, conflict check against the direct pipeline, confirmed permission to engage the end-client contact, commercial terms, and an expiry window. Use when reviewing…

zime-ai/zime-gtm-skills · 108 tokens

executive-briefing

Writes the short brief a rep sends upward out of one deal — to their own exec or the buyer's exec sponsor — covering deal snapshot, status, what's at risk, and the ask, each claim cited to a quote or a CSV column/cell. Use when someone who will never read the transcript needs to act on one deal, not a call-by-call…

zime-ai/zime-gtm-skills · 86 tokens