Build a messaging framework from positioning into audience-specific promise, supporting pillars, proof, objections, terminology, message hierarchy, and channel guidance without turning every artifact into identical copy.
Scanned 9/11/2026
Install to Claude Code
npx -y skills add Dadmin88/hermes-profile-packs --skill messaging-framework --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Messaging Framework?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/dadmin88-messaging-framework)More formats (shields.io, HTML) on the badges page.
---
name: messaging-framework
description: Build a messaging framework from positioning into audience-specific promise, supporting pillars, proof, objections, terminology, message hierarchy, and channel guidance without turning every artifact into identical copy.
---
# Messaging Framework
Use when several writers, campaigns, sales materials, or product surfaces need to communicate the same market position coherently.
## Procedure
1. Start from approved positioning and define the audiences or buying roles whose priorities materially differ.
2. Write one core promise that explains the primary customer outcome without stacking every feature into the headline.
3. Define a small set of supporting message pillars, each tied to a distinct customer value and credible proof.
4. Capture common objections, anxieties, misconceptions, or switching barriers and the evidence-based response to each.
5. Define preferred terminology, category language, claims, and words to avoid when they create confusion or unsupported promises.
6. Establish message hierarchy so short formats know what survives first and long formats know how supporting evidence expands.
7. Provide audience or channel adaptation guidance without prescribing finished copy for every format.
8. Review all claims for product truth, current availability, legal or compliance sensitivity, and proof ownership.
## Decision rules
- Messaging translates positioning; it should not invent a different strategy per channel.
- Proof belongs close to important claims.
- A framework should create consistency of meaning, not identical wording.
- Avoid jargon the audience does not use unless education is part of the strategy.
## Quality gate
The framework is ready when core promise, pillars, proof, objections, terminology, and hierarchy are clear, audience adaptations remain strategically coherent, claims are supportable, and downstream writers can create varied channel-native copy without losing the underlying position.Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!