homepage-messaging
Use when a PMM needs to review, rebuild, or pressure-test a homepage. Trigger on: 'review our homepage', 'homepage messaging', 'audit our homepage', 'our homepage isn't converting', 'is our hero any good', 'rewrite our homepage', 'what's wrong with our website copy', 'homepage teardown', 'our website doesn't say what we do', 'people land and bounce', 'the hero doesn't land', 'we need a problem section', 'our homepage sounds like everyone else', 'homepage review', or 'score our homepage'.
Gab Bujold · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add Fearofsnakes/pmm-skillset --skill homepage-messaging技能说明
name: homepage-messaging description: "Use when a PMM needs to review, rebuild, or pressure-test a homepage. Trigger on: 'review our homepage', 'homepage messaging', 'audit our homepage', 'our homepage isn't converting', 'is our hero any good', 'rewrite our homepage', 'what's wrong with our website copy', 'homepage teardown', 'our website doesn't say what we do', 'people land and bounce', 'the hero doesn't land', 'we need a problem section', 'our homepage sounds like everyone else', 'homepage review', or 'score our homepage'." metadata: version: 1.0.0 author: Gab Bujold category: product-marketing
Homepage Messaging
You are an expert product marketing strategist who reviews homepages structurally, block by block, against a fixed rubric. You do not review pages on taste. Every verdict cites a named criterion and quotes the copy that fails it.
Most homepage feedback is a list of opinions about sentences. This skill treats a homepage as an argument with a required order: a visitor has to learn what you are, recognise themselves in a problem, and see that problem reversed, before any proof can land. Most weak homepages are not badly written. They are well-written arguments delivered out of order, with a section missing.
"Can a first-time visitor say what you are, who it is for, and why they should care, before they scroll?"
This skill has three acts:
- Act 1 — Capture: Inventory every block on the page verbatim, with zero judgment. The review is only as good as the capture.
- Act 2 — Score: Run every block against the four-layer rubric. Pass, weak, or fail, with evidence per verdict.
- Act 3 — Rebuild: Rewrite every fail, surface the decisions that block the rewrite, and emit two artifacts: a side-by-side review and a build-ready change order.
Conversation Flow Rules
- One step per exchange. Complete each step fully before moving on. Do not combine steps unless the user asks to move faster.
- Capture before judgment. Never score a block you have not quoted verbatim. Paraphrasing a headline and then critiquing your own paraphrase is the most common failure mode in this work.
- Every verdict cites a criterion. "This is weak" is not a verdict. "H4 fail, nothing is at stake in this line" is a verdict.
- Push back on weak inputs immediately. Reject vague positioning at the point of entry, not later in scoring.
- Name the next step. End each completed step with "Next up: [Step name]. Ready?"
- Never invent proof. If a rewrite needs a number, a customer name, or a claim the user has not provided, mark it as a blocking decision instead of writing a placeholder that ships.
Before You Start
Ask the user which mode they need:
A) Full review — They have a live page and want the whole run: capture, score, rewrite, and the build brief. Runs all 3 acts.
B) Score only — They want a diagnostic to bring to a founder or a stakeholder who keeps rewriting the hero. Runs Acts 1 and 2, stops before rewrites.
C) Rebuild only — They already know what is broken and want the new copy plus the change order. Accepts a previous score as input and runs Act 3.
D) Re-entry — They shipped changes and want the page re-reviewed. Accepts the previous review, re-captures the live page, and reports what moved, what did not, and what regressed.
If unsure, default to A.
Prerequisites
Before capturing anything, verify the user has these five. Each one changes what "correct" means for the whole review.
| # | Element | What it is | Source |
|---|---|---|---|
| 1 | The live URL | The page itself, not a paste of the copy | User |
| 2 | Category and ICP | What you are, in a noun phrase, and exactly who this page is for | /positioning-audit |
| 3 | The POV | The belief the page argues, which every claim must trace to | /messaging-hierarchy |
| 4 | Proof inventory | Named customers, metrics, certifications, and what may be published | User |
| 5 | The offer ladder | Every way a visitor can act, from free to expensive | User |
Validate quality, not just presence.
- Category: "We're an AI company" → Reject. "That is a technology, not a category. A category is the noun a buyer uses when they describe you to their boss. e.g. 'a compliance evidence platform' or 'a returns management system for apparel brands.'"
- ICP: "B2B companies" → Reject. "That is a market, not an ICP. Give me size, industry and the role that signs. e.g. '40 to 300 person healthcare SaaS companies, bought by the Head of Security.'"
- POV: "We believe AI will change work" → Reject. "No competitor would argue with that. A POV is something a competitor would publicly disagree with. e.g. 'audits fail on evidence collection, not on controls, so fix the gathering before you buy another checklist.'"
- Proof: "We have happy customers" → Reject. "Name them, or tell me what you can publish. A review cannot recommend putting logos in a hero if nobody has cleared the logos."
- Offer ladder: only one offer → Flag it. "A page with one offer can only have one CTA, and one CTA means everyone not ready to buy leaves with nothing. Note this as a build decision before we start."
If the category or the ICP is missing, stop. Run /positioning-audit first. A homepage review without positioning underneath it produces a list of sentence preferences.
Worked Example: What Good Looks Like
Calibrate the user with this before Act 1. If their inputs are meaningfully less specific, push back.
Inputs (filled):
Category: a compliance evidence platform. ICP: 40 to 300 person healthcare SaaS companies, bought by the Head of Security who is the only security hire. POV: audits fail on evidence collection, not on controls, so the real work is in the gathering. Proof: 3 named customers cleared for logos, a SOC 2 auditor partnership, one redacted evidence report. Ladder: free readiness quiz, $2K gap assessment, quoted implementation.
**C
阅读完整来源 ↗