message-architecture

Structures messaging hierarchies, hook banks, and CTA playbooks for campaigns.

1|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/AlexYedi/Empire_State_Events_Pipeline_Take_3 --skill message-architecture-alexyedi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: message-architecture
Source: https://github.com/AlexYedi/Empire_State_Events_Pipeline_Take_3/tree/main/.claude/skills/content-quality/message-architecture
Command: npx skills add https://github.com/AlexYedi/Empire_State_Events_Pipeline_Take_3 --skill message-architecture-alexyedi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Marketing teams often produce inconsistent messaging across channels, campaigns, and writers, leading to diluted value propositions and off-brand copy. This Skill provides a repeatable framework for organizing messaging so every asset ladders up to the same promise, proof, and calls to action. ## Core Features & Use Cases - Messaging Framework: A five-part structure covering audience insight, promise, proof, hooks, and CTAs for any campaign, feature, or persona. - Reusable Templates: Includes a message house diagram, a hook bank sheet with formulas and examples, and a CTA matrix mapping persona to funnel stage. - Governance Guidance: Documents banned phrases, compliance notes, and proof-point freshness rules to keep messaging accurate over time. - Use Case: When launching a new product feature, use this Skill to build the message house, generate channel-specific hooks, and define stage-appropriate CTAs before handing copy briefs to writers or agencies. ## Quick Start Use the message-architecture skill to build a messaging hierarchy with hooks and CTAs for our upcoming product launch targeting operations managers.

Frequently Asked Questions about message-architecture

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a messaging hierarchy for a product launch?

Start with audience and insight (persona, pain, desired outcome), then define the promise, supporting proof points, channel-specific hooks, and stage-appropriate CTAs. The message house template organizes these layers into a single reference document.

What is a hook bank and how do I build one?

A hook bank is a sheet of proven hook formulas with examples, mapped to specific channels. Build one by listing formulas that fit each channel, then filling in examples grounded in your persona's pain points and desired outcomes.

How do I audit messaging consistency across channels?

Compare each channel's copy against the documented promise, proof points, and banned phrases in the messaging framework. Flag assets that use retired metrics, off-framework claims, or CTAs mismatched to the funnel stage.

When should I update or retire proof points in messaging?

Retire proof points when the underlying metrics become outdated or the customer quotes no longer reflect the current product. The framework recommends keeping proof fresh and pairing with voice guidelines to maintain tone consistency.

What are the limitations of a messaging framework for copywriting?

A messaging framework defines structure and governance but does not write final copy or enforce tone by itself. Pair it with a voice-guidelines skill for tone consistency and with channel-specific execution for finished assets.