message-house-builder

Featured

Use when the user asks to "build a message house", "write a PR-FAQ for our launch", or "define the launch narrative and value pillars"; derives from the positioning canvas a message house — tagline, one-liner, three value pillars, per-persona proof points (each labeled Measured / User-provided / [needs source]) — plus a working-backwards PR-FAQ narrative spine (launch-day tense, empty-chair test, five external + five internal FAQs) and per-channel message angle packs (angles, not finished copy). Not for the positioning canvas itself — use positioning-mapper; not for finished blog posts or pages — use content-writer; not for ad or email units — use each discipline creative builder; not for claim adjudication — use offer-claims-registry. 消息屋/PR-FAQ/价值支柱/发布叙事

AI & Automation 2,354 stars 322 forks Updated today Apache-2.0

Install

View on GitHub

Quality Score: 98/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Message House Builder Derives the launch messaging hierarchy from the positioning canvas — a message house (tagline, one-liner, three value pillars, per-persona proof points), a working-backwards PR-FAQ narrative spine, and per-channel message angle packs. It sits in the **Assemble** phase of the RAMP loop and feeds three [RAMP](../../../references/ramp-benchmark.md)-`A` sub-items: *message house complete*, *narrative spine (PR-FAQ or equivalent) in launch-day tense with numbers over adjectives*, and *announcement ↔ landing ↔ offer message-match*. It is also the upstream of the `A1` claim-integrity veto: every product or comparative claim without substantiation is marked `[needs source]` and submitted to `memory/claims/candidates.md` — this skill never adjudicates a claim. **Scope guard**: this skill turns an existing positioning canvas into messaging only. It does **not** build the positioning itself ([positioning-mapper](../../research/positioning-mapper/SKILL.md) is the sole upstream — if the canvas is missing, route there first and stop), write finished blog posts or pages ([content-writer](../../../seo-geo/build/content-writer/SKILL.md)), produce ad or email units ([ad-creative-builder](../../../ad/orchestrate/ad-creative-builder/SKILL.md) / [email-creative-builder](../../../email/engage/email-creative-builder/SKILL.md)), adjudicate claims ([offer-claims-registry](../../../protocol/offer-claims-registry/SKILL.md) is the sole writer of `memory/claims/claims-ledger.md`...

Details

Author
aaron-he-zhu
Repository
aaron-he-zhu/aaron-marketing-skills
Created
6 months ago
Last Updated
today
Language
Python
License
Apache-2.0

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

Web & Frontend Listed

messaging-hierarchy

Use when turning a positioning statement into actual copy - building the value proposition, message pillars, proof points, and per-channel messaging that keep the website, ads, and sales deck all saying the same thing. Triggers on "write our value proposition", "message pillars", "messaging framework", "messaging house", "key messages", "proof points", "our website and sales say different things", "per-channel messaging", "on-message copy". Takes the positioning-statement as input and feeds landing-page-copy. Do NOT use when you have not yet fixed positioning - use positioning-statement first. Do NOT use when you need the actual hero/landing page words - use landing-page-copy. Do NOT use to sequence launch phases - use launch-plan-sequencer; for the hour-by-hour go-live - use launch-day-runbook; for the sales deck/talk track - use sales-enablement-kit; for the in-product activation flow - use plg-motion-designer.

0 Updated 5 days ago
SkillMedev
Web & Frontend Listed

messaging-hierarchy

Use when turning a positioning statement into actual copy — building the value proposition, message pillars, proof points, and per-channel messaging that keep the website, ads, and sales deck all saying the same thing. Triggers on "write our value proposition", "message pillars", "messaging framework", "messaging house", "key messages", "proof points", "our website and sales say different things", "per-channel messaging", "on-message copy". Takes the positioning-statement as input and feeds landing-page-copy. Do NOT use when you have not yet fixed positioning — use positioning-statement first. Do NOT use when you need the actual hero/landing page words — use landing-page-copy. Do NOT use to sequence launch phases — use launch-plan-sequencer; for the hour-by-hour go-live — use launch-day-runbook; for the sales deck/talk track — use sales-enablement-kit; for the in-product activation flow — use plg-motion-designer.

0 Updated 5 days ago
aouellets
AI & Automation Listed

vantage-messaging

TRIGGER when the user wants to build or sharpen THEIR OWN positioning & messaging — "our positioning", "messaging house", "value proposition", "our one-liner", "homepage copy", "how should we position", "messaging framework", "what's our narrative". Part of the `vantage` (Vantage.os) Positioning Studio pack. Produces a positioning statement, messaging house, hero copy, and narrative. DO NOT trigger for analyzing a COMPETITOR's positioning (use vantage-positioning) or writing long-form content (use vantage-content-plan / copywriting).

0 Updated 3 weeks ago
macmenes