Agent Skillsmohitagw15856/pm-claude-skills › messaging-framework

messaging-framework

GitHub

构建统一的消息框架(消息屋),确保营销、销售和产品团队对外宣传一致。包含受众定位、价值主张、三大核心支柱及证据、异议处理和用语指南,旨在消除信息混乱,提升品牌一致性。

plugins/pm-growth/skills/messaging-framework/SKILL.md mohitagw15856/pm-claude-skills

Trigger Scenarios

创建消息框架或价值主张 统一营销与销售口径 制定产品定位话术

Install

npx skills add mohitagw15856/pm-claude-skills --skill messaging-framework -g -y
More Options

Non-standard path

npx skills add https://github.com/mohitagw15856/pm-claude-skills/tree/main/plugins/pm-growth/skills/messaging-framework -g -y

Use without installing

npx skills use mohitagw15856/pm-claude-skills@messaging-framework

指定 Agent (Claude Code)

npx skills add mohitagw15856/pm-claude-skills --skill messaging-framework -a claude-code -g -y

安装 repo 全部 skill

npx skills add mohitagw15856/pm-claude-skills --all -g -y

预览 repo 内 skill

npx skills add mohitagw15856/pm-claude-skills --list

SKILL.md

Frontmatter
{
    "name": "messaging-framework",
    "description": "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."
}

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

Version History

  • a38bc30 Current 2026-07-05 11:21

Same Skill Collection

exports/openclaw/360-feedback-template/SKILL.md
exports/openclaw/401k-plan-decoder/SKILL.md
exports/openclaw/ab-test-planner/SKILL.md
exports/openclaw/ab-test-readout/SKILL.md
exports/openclaw/accessibility-audit/SKILL.md
exports/openclaw/account-plan/SKILL.md
exports/openclaw/acquirer-red-team/SKILL.md
exports/openclaw/ad-copy/SKILL.md
exports/openclaw/aeo-optimizer/SKILL.md
exports/openclaw/agenda-or-cancel/SKILL.md
exports/openclaw/agent-design-review/SKILL.md
exports/openclaw/agent-observability-spec/SKILL.md
exports/openclaw/agent-spec/SKILL.md
exports/openclaw/ai-ethics-review/SKILL.md
exports/openclaw/ai-eval-plan/SKILL.md
exports/openclaw/ai-feature-prd/SKILL.md
exports/openclaw/ai-product-canvas/SKILL.md
exports/openclaw/air-quality/SKILL.md
exports/openclaw/altitude-shifter/SKILL.md
exports/openclaw/ambiguity-resolver/SKILL.md
exports/openclaw/analyst-relations-brief/SKILL.md
exports/openclaw/announcement-card/SKILL.md
exports/openclaw/api-docs-writer/SKILL.md
exports/openclaw/api-test-plan/SKILL.md
exports/openclaw/api-versioning-strategy/SKILL.md
exports/openclaw/apology-letter/SKILL.md
exports/openclaw/architecture-decision-record/SKILL.md
exports/openclaw/architecture-diagram/SKILL.md
exports/openclaw/archive-strategy/SKILL.md
exports/openclaw/assumption-bounty/SKILL.md
exports/openclaw/assumption-mapper/SKILL.md
exports/openclaw/async-update-format/SKILL.md
exports/openclaw/auto-repair-estimate-decoder/SKILL.md
exports/openclaw/autopilot-charter/SKILL.md
exports/openclaw/benefits-decoder/SKILL.md
exports/openclaw/bid-tender-review/SKILL.md
exports/openclaw/board-deck-narrative/SKILL.md
exports/openclaw/board-minutes/SKILL.md
exports/openclaw/board-pre-read/SKILL.md
exports/openclaw/bom-cost-review/SKILL.md
exports/openclaw/bookkeeping-categorization/SKILL.md
exports/openclaw/boolean-search-builder/SKILL.md
exports/openclaw/brag-doc/SKILL.md
exports/openclaw/brainstorming/SKILL.md
exports/openclaw/brief-builder/SKILL.md
exports/openclaw/briefing-note/SKILL.md
exports/openclaw/budget-builder/SKILL.md
exports/openclaw/budget-variance-analysis/SKILL.md
exports/openclaw/bug-diagnosis/SKILL.md
exports/openclaw/bug-report/SKILL.md

Metadata

Files
0
Version
471c606
Hash
7ba66226
Indexed
2026-07-05 11:21

- 위키
Copyright © 2011-2026 iteam. Current version is 2.155.2. UTC+08:00, 2026-07-30 18:11
浙ICP备14020137号-1 $방문자$