Index of every page on this site: llms.txt
All skills
deanpeters avatar

/message-house

@476ae12
Run it yourself

Build a message house: one roof message, three value pillars, sourced proof, a foundation, and role and channel variants. Use when Marketing, Sales, and partners each tell a different story.

Use this Skill: https://skilld.dev/gh/deanpeters/product-manager-skills/message-house

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

examplessample.md

≈797 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Message House Example: SaaS

Offering: Route Optimizer, an add-on in Fieldlight (field service SaaS) Target: dispatchers and ops managers at 50-300 technician service companies Positioning: "For dispatch teams at mid-size service companies who lose hours each day to manual rescheduling, Route Optimizer rebuilds the day in seconds when the plan breaks..."

Why this example exists: the team's first draft is three features. The rebuild shows the cover test, the trace, and why the foundation matters for a new module.


## Draft critique (first)
Pillars as submitted: "AI routing engine," "Real-time GPS," "Drag-and-drop calendar."
Cover the name and any competitor could claim all three. They are features. No pillar traces to
a customer pain.

## Message House: Route Optimizer

**ROOF**
> When the day falls apart, your schedule fixes itself before the phone stops ringing.

| Pillar | Outcome | Traces to | Cover test |
|---|---|---|---|
| 1 | Fit the emergency job in without wrecking the day | Pain: "a rush call blows up my afternoon" (7 of 9 dispatcher interviews) [FROM YOU] | Passes |
| 2 | Send the right tech the first time | Pain: repeat visits because of wrong skills or parts [FROM YOU] | Passes |
| 3 | Know tomorrow's plan tonight | Gain: dispatchers want to leave on time [AI-SUGGESTED, VALIDATE THIS] | Needs interview evidence |

**Proof**
| Pillar | Proof | Type | Source |
|---|---|---|---|
| 1 | Median reschedule time, before vs after, across pilot accounts | Measured pilot | `[NEEDS SOURCE]`: 14 pilot accounts ran; results not yet pulled |
| 2 | First-visit fix rate change | Measured pilot | `[NEEDS SOURCE]` |
| 3 | Calculation: dispatcher hours saved = reschedules per day x minutes each x days, with *your* numbers | Repeatable calculation | Built from template |

**Foundation:** 11 years in field service software; [N] customers `[NEEDS SOURCE]`; SOC 2 Type II
report dated [date] `[NEEDS SOURCE]`; 24-hour support.

**Superlatives found:** "smartest scheduler on the market." Basis: none. Removed.

## Variants
| Role | Lead pillar | Wording |
|---|---|---|
| Dispatcher | 1 | "A rush call won't blow up your afternoon." |
| Ops manager | 2 | "Fewer repeat visits, more jobs per tech per day." |
| CFO | 3, with calculation | "Hours back each week, from numbers you can check." |
| Reseller | All three, short | "An add-on your customers ask for and you can demo in five minutes." |

## Words
Use: "fix the day," "rush call," "first-visit fix" (customers' words, interviews). Avoid: "AI-powered,"
"optimization engine," "seamless."

## Test plan
Five dispatchers from the interview pool. Read roof and pillars aloud. Ask what they heard,
believe, doubt. Result that changes the house: if fewer than 3 repeat pillar 1 unprompted, re-cut.

What to learn from this

  • The cover test killed all three original pillars in about ten seconds.
  • Two pillars rest on pilot data nobody has pulled. Flagged [NEEDS SOURCE] rather than filled, so they stay out of external material until the numbers exist.
  • The foundation carries the new module. A first-year add-on borrows the company's track record.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 warning7d3 checks · Risk SAFE
  • Gen Agent Trust Hub7d

    This skill provides a strategic framework for creating marketing messaging houses and contains no executable code, network operations, or sensitive data access.

  • Socket7d

    No alerts

  • Snyk7d

    Risk: MEDIUM · 1 issue

Signed by skilld at 476ae12. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last week.

Activeupdated last week
argument-hint
[offering, target customer, and your positioning if you have it]
type
component
theme
strategy-positioning
Other metadata
intent
Give everyone who speaks about the offering one consistent, customer-tested value story built on real customer pains and gains and backed by proof, so the market hears value instead of a feature list. Turns a positioning statement into words customers will read, without inventing proof.
best_for
[
  "Turning a positioning statement into customer-facing messages before a launch",
  "Aligning Marketing, Sales, and partners on one value story",
  "Adapting one core message for different buying-group roles and channels",
  "Reviewing messaging for feature lists, superlatives, and claims nobody can prove"
]
scenarios
[
  "Our website, deck, and sales email all say different things. Build one messaging framework",
  "We have a positioning statement. How do we say it to a dispatcher versus a CFO?",
  "Review our messaging. I think our three pillars are just three features",
  "Build the message house for a new variable-speed controller line"
]
estimated_time
30-45 min

README badge

README badge for deanpeters/product-manager-skills/message-house