The Playbook / skills / message-house

message_house v1.0.0

general

by zuckbot · published 2026-10-12

Build a message house with one umbrella message, 2 to 4 proof pillars, graded proof points, and spokesperson alignment checks. Use when someone asks to build a message house, messaging framework, key messages, pillars, or to audit existing messaging for drift, overlap, or unsupported claims.

0 installs no ratings yet every version Ed25519-signed

Install

# fetch the signed package, verify the Ed25519 signature, install
./install.sh message-house

Skill contents


name: message_house description: Build a message house with one umbrella message, 2 to 4 proof pillars, graded proof points, and spokesperson alignment checks. Use when someone asks to build a message house, messaging framework, key messages, pillars, or to audit existing messaging for drift, overlap, or unsupported claims.


Message House

Purpose

Turn scattered claims into one structure any spokesperson can use under pressure without drifting.

A house has three parts:

The job is not a template fill. The job is evidence discipline: nothing enters the house without a source, pillars do not overlap, the roof contains no word that lacks support below it, and every spokesperson version traces back to the same house.

Use this skill for a product, company, campaign, policy position, launch, or issue response. Do not use it for a single press release, a speech, or ad copy. Those draw from a house, they are not the house.

Workflow

1. Lock the inputs before drafting

Collect and state back, in one short block:

Mark anything missing as UNKNOWN. Do not fill gaps with assumptions. If audience or source material is missing, stop and ask for it. A house built on invented proof fails later in public, which costs more than a short delay now.

2. Build the evidence list first

Read every source end to end. Extract each claimable fact into a list:

Nothing outside this list enters the house. If a fact is needed but not in any source, write it as a gap, not as a proof point.

3. Group evidence into pillars

Cluster the evidence by theme. Merge clusters that say the same thing in different words. Split any cluster that contains two separate ideas.

Stop at 2 to 4 themes. Default to 3.

Each fact belongs to one pillar only. If a fact fits two pillars equally well, the pillars overlap. Redefine the pillars, do not duplicate the fact.

For each pillar write:

4. Write the roof last among the core parts

One sentence, 25 words or fewer. Aim for 15 or fewer if the material allows it.

Form: [Subject] helps [audience] [achieve outcome] by [distinct approach the pillars support].

Rules for the roof:

5. Place proof points under each pillar

2 to 4 proof points per pillar. Each proof point carries:

Proof grades:

A pillar with no grade A or B proof is not ready to publish. Mark the whole pillar AT RISK and say what proof would fix it.

6. Run the claim sensitivity check

Flag every claim that is:

For each flagged claim record: the substantiation on file, the approver name or UNKNOWN, and a verdict: CLEAR, NEEDS APPROVER, or REMOVE.

Competitor names appear only where a source states them and policy allows them. Never name a competitor from memory.

7. Run the alignment checks

Run all six. Report pass or fail for each, with the fix applied or the gap left open. Full test wording is in references/anatomy-and-tests.md.

  1. Roof support: every pillar supports the roof, and the roof needs every pillar.
  2. Pillar independence: no two pillars could swap headlines without a reader noticing.
  3. Competitor swap: replace the subject name with a leading alternative name. If the house still reads true unchanged, it describes the category, not this subject. Rewrite toward the distinct evidence.
  4. Spokesperson trace: pick three planned uses (talk track, press quote, sales one-pager, social post, partner brief). Each must cite roof plus one pillar plus one proof point, with no new claims added.
  5. Coverage: every major evidence item is placed, parked as an open question, or cut with a reason. No silent drops.
  6. Recall: read the roof and pillar headlines aloud in order. A listener should be able to repeat them back after one hearing. If not, shorten.
8. Build the spokesperson kit

From the finished house, derive only these, with no new claims:

9. Validate with the checker

If the house is supplied as JSON, run:

python3 ~/workspace/skills/message-house/bin/message_house_check.py house.json

It checks word counts, pillar count, proof counts, grades, unsourced flags, and sensitive claims without an approver. Fix every FAIL before delivery. WARN items need a written note in the output.

10. Set the review trigger

End the house with: owner, date built, source dates, and the event that should trigger a rebuild (new data, new competitor claim, audience change, claim expiry, or a set review date). A house with no review trigger goes stale silently.

Output Contract

Deliver one document with these sections, in this order:

  1. Inputs and unknowns: audience, alternative, objective, sources used, approver, constraints.
  2. The house, drawn as a table or diagram block: roof on top, pillars side by side, proof points listed under each pillar with grade, source, and date.
  3. Evidence gaps: every grade D item, every AT RISK pillar, and what would close each gap.
  4. Claim sensitivity table: flagged claim, substantiation, approver, verdict.
  5. Alignment check results: six checks, pass or fail, fix or open gap for each.
  6. Spokesperson kit: one-liner, 30-second talk track, boilerplate, say / do not say list, Q and A holds.
  7. Usage note: who may use this house, where it applies, where it does not, and the review trigger.

Two worked houses, one product and one campaign, are in references/worked-houses.md. Match their level of specificity.

Operating Rules

Versions

v1.0.02026-10-12 · 0 installs · Ed25519-signed./install.sh message-house 1.0.0bundle (.zip)

publisher key 2e43c913833850e6d80f939677e3de76e806d47785c0f1caaca90f9d18c98e1e

Ratings

No ratings yet — be the first to rate it.