Search-hypothesis validation checklist. Use when the task requires interview, search-term, or page evidence needed for each hypothesis. Apply this method to the specified inputs and verify the deliverable
Installs into .claude/skills of the current project.
Sponsors
SSkills DirectorySkills Directory
Know which skills are safe — weekly.
SSkills DirectorySkills Directory
Is that skill safe to install?
Are you the author of Mk 044?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/backtrue-mk-044)
---
name: mk-044
description: "Search-hypothesis validation checklist. Use when the task requires interview, search-term, or page evidence needed for each hypothesis. Apply this method to the specified inputs and verify the deliverable"
---
# MK-044 | Search-hypothesis validation checklist
For a regular chat, upload `packs/mk-044.md`. It includes the shared rules, this method, and required references
## Purpose
This skill delivers: **Interview, search-term, or page evidence needed for each hypothesis**
Task stages are analytical categories, not a claim that every customer follows the same path
## Required inputs
Provide: The product or service, customers' own words, existing pages, and actions the company can support
## Method
1. List the hypotheses to validate for each need path: event, search phrase, intent, ad answer, page, and next step
2. Prioritize verification through interviews, search terms, customer-service records, and existing pages
3. Ask four self-check questions: Is the event specific? Does the search phrase sound natural? Do the ad, page, and action address the same question? Which part still lacks evidence?
## Calculations and interpretation
Search phrases and paths are planning hypotheses; check them against real search terms and evidence of how pages support the need
## Required output fields
| Order | Field | How to complete |
|---:|---|---|
| 1 | Trigger event | Use source evidence, an intermediate method result, or an explicit unknown; do not invent information |
| 2 | The customer's current problem | Use source evidence, an intermediate method result, or an explicit unknown; do not invent information |
| 3 | Available answer | Use source evidence, an intermediate method result, or an explicit unknown; do not invent information |
| 4 | Supporting page/creative | Use source evidence, an intermediate method result, or an explicit unknown; do not invent information |
| 5 | Gap | Use source evidence, an intermediate method result, or an explicit unknown; do not invent information |
| 6 | Reasonable next step | Use source evidence, an intermediate method result, or an explicit unknown; do not invent information |
| 7 | Basis | Use source evidence, an intermediate method result, or an explicit unknown; do not invent information |
## Verification cases
**MK-044-C05 | An ad promotes a service that the page does not explain**
Expected: Record a verifiable promise gap; do not immediately conclude it caused all abandonment
**MK-044-C06 | No verbatim customer statements are available**
Expected: Produce only a need map awaiting validation, not a claimed finding from actual research
## Method sources
Source file: Google Ads 第一堂|看懂需求,才知道廣告怎麼接
Location: Hypothesis
Source basis: extracted from course materials
Source URL: https://docs.google.com/presentation/d/15ZOg0pX_xikpdA3FwGEoCSVgWortvCnxSe4hz4ugizg/edit
English translation of source excerpt:
> Use a hypothetical dehumidifier example to explain the event, problem awareness, search, answer, and action