跳到主要内容
知仓学习社ZHICANG

messaging-framework

Build a messaging framework (message house) that the whole company can use consistently. Use when asked to create messaging, a value proposition, a …

不碰外部(只输出文字)无严重或高危命中mohitagw15856/pm-claude-skills

它会碰到什么

扫了多少1 个文本文件,3 KB
它会碰到什么不碰外部(只输出文字)
命中总数0 处
命中统计严重 0 · 高 0 · 中 0 · 低 0

这一栏是扫描器报的事实,不是结论。命中多不等于有毒(安全工具、规则库、示例脚本本来就会包含危险写法),命中少也不等于干净。它和你手上的凭据、文件、网络有什么关系,需要你自己看。

技能内容

Messaging Framework Skill

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.)

Required Inputs

Ask for these only if they aren't already provided:

  • Target audience — who specifically, and the problem they feel (the sharper the segment, the sharper the message).
  • The product & its differentiated value — what it does and why it's better/different, with evidence.
  • Proof — data, customers, results, or mechanisms that back the claims.
  • Competitive frame — what they'd otherwise use, and the objections they raise.

Output Format

Messaging Framework: [product]

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 guidewords 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.

Quality Checks

  • [ ] The value proposition is benefit-led and specific to one audience — not a feature list for everyone
  • [ ] Every pillar is a benefit with at least one concrete proof point — not an unbacked claim
  • [ ] The one-liner uses the customer's language, not internal jargon
  • [ ] Objections are answered honestly with evidence, not dodged
  • [ ] A words-we-use / words-we-avoid list exists so the whole org stays consistent

Anti-Patterns

  • [ ] Do not lead with features — buyers care about the outcome; features are proof, not the message
  • [ ] Do not make claims without proof — an unbacked superlative ("the best", "revolutionary") reads as noise
  • [ ] Do not try to speak to everyone — messaging for all audiences resonates with none; pick the segment
  • [ ] Do not use internal jargon the customer wouldn't say — if they can't repeat it, it won't spread
  • [ ] Do not confuse this with positioning — decide the category/competitive frame first (see product-positioning-doc), then write the words

Based On

Message-house / value-proposition practice (incl. April Dunford-style positioning as the upstream input).

想直接用这个技能?

本站把开放许可(MIT / Apache 等)的技能按仓库打包整理到网盘,点一下转存到你自己的网盘,不用一个个从 GitHub 拉。许可未声明的技能只给原始仓库链接,不打包。

同名技能的其他版本

有 3 个不同仓库或目录里都有叫 messaging-framework 的技能。它们内容并不相同,别混用: