laja-wynter-message-testing
Diagnose and improve B2B page messaging using Peep Laja's Wynter method; use for homepage, landing page, product page, or positioning reviews needing target-buyer feedback.
- License 许可
- Apache-2.0
- 所属仓库
- getedgehq/skills
- 最近更新
- 2026-11-12
- Stars
- ★ 5
- Forks
- 0
01 前言 Front Matter
- name
- laja-wynter-message-testing
- description
- Diagnose and improve B2B page messaging using Peep Laja's Wynter method; use for homepage, landing page, product page, or positioning reviews needing target-buyer feedback.
02 资源文件 7
- 参考文档checklists/review-checklist.md5.5 KB
- 参考文档DERIVATION.json2.2 KB
- 参考文档examples/worked-examples.md6.8 KB
- 许可证LICENSE10.5 KB
- 参考文档references/method.md14.7 KB
- 参考文档references/sources.md2.0 KB
- 参考文档templates/output-template.md6.1 KB
03 SKILL.md 正文
Wynter B2B message testing
Based on Peep Laja's public method. Not affiliated with or endorsed by Peep Laja.
When to use
Use this skill to find why a B2B revenue page fails to communicate its offer or persuade its intended buyers, then produce an evidence-linked revision and retest plan. It fits homepage, campaign landing page, product page, and value proposition reviews before launch or after disappointing results. It is especially useful when internal copy debates lack buyer evidence. Message testing explains interpretation and motivation; conversion measurement requires separate behavioral evidence. [S1][S6]
Start with buyer research if current priorities, buying triggers, alternatives, or decision roles are unknown. Existing recent research can supply this context without another survey. Choose a preference test for two or three viable directions and a pricing page test for price comprehension. Routine message diagnostics should focus on the persuasion path, excluding blogs, careers pages, support material, and late-stage competitor comparison pages. [S4]
The deliverable is a message diagnosis and revision brief, using the output template. If buyer responses are unavailable, produce a clearly labelled provisional expert review and a research plan. Never describe an untested rewrite as validated, invent respondent comments, or manufacture scores.
Procedure
-
Frame the decision. Read method: Scope and evidence. Name the page, intended buyer, next action, and decision the work must inform. Record the message hypothesis and observable success condition before inspecting feedback. Keep the scope to a concrete page or message direction.
-
Check buyer context. Use method: Buyer context to distinguish known facts from assumptions about pains, priorities, triggers, buying roles, and alternatives. Reuse credible recent evidence. Where gaps would change the message, plan focused buyer research before writing the promise. [S2][S4]
-
Choose the study. Follow method: Study selection. Match the question to a message, campaign landing page, pricing, preference, or buyer-context study. If research cannot run, preserve the expert-review label and identify exactly what buyer evidence remains missing.
-
Freeze the stimulus. Follow method: Stimulus and audience. Record the URL or faithful image, version, hero, important sections, and campaign context. Keep enough of the page experience to detect an explanation that arrives too late. Specify respondent criteria and separate prospects from knowledgeable customers. [S5][S6]
-
Plan the sample and questions. Use method: Questions and sampling for neutral comprehension prompts and ratings with explanations. Start with the playbook's 15-person qualitative default where appropriate. Treat sample counts as planning guidance, never a guarantee of saturation or statistical significance. [S4][S6]
-
Collect and organize evidence. Use the evidence fields to retain respondent IDs, segment, page location, rating scale, and feedback. Cluster underlying questions, preserve meaningful disagreement, and distinguish observed interpretation from the agent's explanation. AI summaries must remain traceable to the actual responses.
-
Find the earliest failed layer. Apply method: Ordered diagnosis: clarity, relevance, value, then differentiation. Record the primary failure, evidence, causal hypothesis, and proposed revision. Do not let a favorable downstream score override basic category confusion. [S1]
-
Audit proof and alternatives. Read method: Proof, friction, and sameness. Compare claims with alternatives buyers actually use, including manual work or inaction. Identify unsupported promises and consequential doubts. Distinguish defensible differences from unusual wording. [S1][S3]
-
Rewrite around the diagnosis. Follow method: Revision rules and consult the worked illustrations. Revise the failed buyer question first, connect capabilities to desired outcomes, place proof beside claims, and simplify repeated sections. Preserve strategic tradeoffs instead of implementing every suggestion. [S3][S5]
-
Review the complete brief. Run the pass/fail checklist. Confirm evidence supports the diagnosis, every priority change has a reason, and copy claims are verified or visibly provisional. Correct failed items or record the evidence needed to resolve them.
-
Retest and decide. Apply method: Retest and maintenance. Compare buyer interpretations using a comparable audience, stimulus scope, and questions. Recommend ship, revise, or gather context against the declared decision rule. Specify a follow-up trigger; avoid spending on another message test for typos or design-only changes. [S4]
Files in this skill
- SKILL.md: Entry point, applicability, and the agent's operating loop.
- references/method.md: Detailed principles, decisions, exceptions, and explicit source warnings.
- references/sources.md: Fetched public sources and the contribution of each numbered citation.
- examples/worked-examples.md: Two invented before-and-after illustrations with diagnosis and retest criteria.
- templates/output-template.md: Fill-in message diagnosis and revision brief with field guidance.
- checklists/review-checklist.md: Pass/fail output review and common failure modes with fixes.
04 同仓库更多 Skills
zero-downtime-cloud-move
Runbook for moving a live app from one cloud to another (Google Cloud to AWS, AWS to Google Cloud, a PaaS to your own account, or one storage provider to another) without downtime. The agent inventories what is really running, builds the new stack next to the old one, keeps a one-line rollback for every phase, proves the new stack with real workloads before any traffic moves, cuts over with a checklist, watches a fixed window after the switch, copies data with an idempotent job whose second pass must report 0 left, and deletes the old cloud last. Use when someone asks to migrate, move or replatform a production app, switch cloud providers, move a backend, database files or object storage, plan a DNS cutover, or decommission an old cloud account.
zayats-ceo-branding
Build an evidence-based CEO positioning paper, Personal Branding Roadmap, and editorial workflow using Marina Zayats's public method. Use for executive branding, LinkedIn ghostwriting briefs, profile strategy, and recurring CEO-approved content planning.
yc-app-roast
YC App Roast: roast a YC or a16z Speedrun application. Use when a founder wants their YC or Speedrun answers scored, asks "what would a YC partner think", wants the weak answers found or rewritten, or wants their draft checked before they submit. Scores every answer 0-10 against public advice from YC and Speedrun partners, names the top issue with the exact words that cost points, and writes a rewrite from the founder's own facts. Works for YC and a16z Speedrun. Not affiliated with Y Combinator or a16z.
yc-app-review
YC App Review: get a YC or a16z Speedrun application reviewed by people you trust. Use when a founder wants friends, mentors or alumni to review their YC or Speedrun application, or asks to share their draft for feedback. Builds a shareable review page (one HTML file, application-portal look) where reviewers leave notes per question and press "Send my notes" to send them back as text, then parses the notes into proposed rewrites. Optional tracked private links per reviewer. Works for YC and a16z Speedrun. Not affiliated with Y Combinator or a16z.
x-growth-playbook
X Growth Playbook. Analyse a person's own X (Twitter) posts and tell them what to post next, with the numbers behind every claim. Compares quote posts vs originals, links vs no links, short vs long, time of day in their timezone, media vs text and the topics they name, reports medians with n, then writes a 10-step plan and the next 7 posts in their voice. Use when the user says "analyse my X posts", "what works on my Twitter", "how do I grow on X", "what should I post next on X", "audit my X account", or shares an X data archive, X API export or a list of their posts. Runs on the user's computer.
workplan
Create, update, or close work plans for multi-step tasks. Use when starting refactors, bug lists, feature work, migrations, or any task with 2+ steps. Also use after auto-compaction to re-orient. Triggers: "workplan", "work plan", "create a plan", "what's the plan", "where was I", or when Claude detects a multi-step task that needs tracking.