skills/messaging-framework/SKILL.md
Build a messaging framework (message house) that the whole company can use consistently. Use when asked to create messaging, a value proposition, a message house, key messages, or to make marketing/sales/product say the same thing. Produces a messaging framework — audience & value proposition, the one-line positioning, 3 message pillars with proof points, objection handling, and a words-we-use/avoid list.
npx skillsauth add mohitagw15856/pm-claude-skills messaging-frameworkInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
If marketing, sales, and the website all describe the product differently, customers can't form a clear picture — and confused buyers don't buy. This skill builds the "message house": one value proposition, a few proof-backed pillars, and the exact language everyone uses, so the story is consistent everywhere. (Positioning decides the category and frame; this decides the words.)
Ask for these only if they aren't already provided:
1. Audience & core problem — who it's for and the problem in their words.
2. Value proposition — one sentence: for [audience] who [need], [product] is the [category] that [key benefit], unlike [alternative], because [reason to believe].
3. One-liner — the plain-language tagline a customer would repeat to a colleague.
4. The three pillars — the message house roof + columns:
| Pillar (benefit, not feature) | Why it matters to the buyer | Proof point(s) | |---|---|---| | Pillar 1 | | | | Pillar 2 | | | | Pillar 3 | | |
5. Objection handling — the top 3–5 objections and the honest, evidence-based response to each.
6. Language guide — words we use (the customer's vocabulary, the category we claim) and words we avoid (jargon, overclaimed superlatives, competitor framing). This is what keeps everyone consistent.
Message-house / value-proposition practice (incl. April Dunford-style positioning as the upstream input).
business
Analyze why deals are won and lost and turn it into an action plan. Use when asked to run a win/loss analysis, review closed-won and closed-lost deals, understand why the team is losing to a competitor, or summarize sales feedback into patterns. Produces a structured win/loss report with themes, win/loss rates by segment and competitor, representative quotes, and prioritized actions for product, marketing, and sales.
development
Route a fuzzy request to the right skill in this library. Use when the user is unsure which skill fits, asks 'which skill should I use for X', describes a task without naming a skill, or when a request could plausibly match several skills. Produces a best-fit recommendation with the inputs to gather, a runner-up with the tie-breaker, and a workflow recipe when the job spans multiple skills.
testing
Triage a vulnerability or scanner finding — assess real severity, exploitability, and how urgently to fix. Use when asked to triage a CVE, prioritize scanner/pentest findings, assess a vuln's risk, or decide what to patch first. Produces a triage verdict: CVSS-informed severity adjusted for your context, exploitability, real risk, a fix/mitigation, and an SLA — so you fix what matters, not just what's red.
development
Stand up a Voice of Customer (VoC) program that turns feedback into action. Use when asked to build a VoC program, design a customer feedback loop, consolidate feedback sources, or set up a closed-loop feedback process. Produces a VoC program design — objectives, feedback sources and channels, a taxonomy, collection and analysis cadence, closed-loop routing, ownership, and success metrics.