gooseworks-ai/goose-skills / skills/marketing/research-market
research-market
VerifiedMarket research and brand watch: which market the brand is in, how big the reachable part is, what's changing, how buyers buy and what they pay, what people are saying now, and what it means for positioning. Use when the marketer asks for market research, "how big is my market", "what's changing in my category", "what do others charge", "what are people saying about us", "is there demand for <idea>", or "watch my brand / tell me if something blows up" (alerts only, risk first). Also writes positioning choices and finished messages ("position my product", "write our positioning"). Researches first, asks only decisions at the end, and saves the output to the brand. Not for who the buyers are and their own words — use research-audience; not for a deep look at rivals — use research-competitors.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 10.6 KB |
| references/idea-validation.md | markdown | 2.9 KB |
| references/listening-craft.md | markdown | 11.6 KB |
| references/positioning.md | markdown | 5.9 KB |
| references/report-format.md | markdown | 8.5 KB |
| references/run-memory.md | markdown | 9.4 KB |
| skill.meta.json | config | 4.9 KB |
| tests/examples/2026-10-22/positioning.md | markdown | 8.0 KB |
| tests/fixtures/positioning-evidence.md | markdown | 3.2 KB |
| tests/test-by-hand.md | markdown | 6.7 KB |
references/idea-validation.md
View on GitHub# Idea validation — "is there demand for this?"
Load when the ask names a product, offer, feature or concept that doesn't exist yet ("would people buy a …?", "is there demand for …?", "should we launch …?"). It's the same market research, pointed at one idea: the report keeps write-report's shape, and its first line is the verdict. Directional evidence, never proof of product-market fit and never a replacement for the brand's own sales data.
## 1. Write the hypotheses first
Three to five, each with what would support it and what would weaken it. Typical ones: the problem is frequent · it is urgent · today's alternatives fall short · people would pay roughly <price> · the message "<promise>" lands with <buyer>. Write them before reading anything, so the evidence can't be bent to fit.
## 2. Collect the evidence
From the same free pass as a market report, aimed at the hypotheses: what buyers say about the problem (reviews of today's alternatives, threads, comments, video transcripts), what they use instead (direct rivals, substitutes, workarounds, doing nothing), rivals' offers and prices, search phrasings and their direction. When the category sells through social commerce, add a pass on TikTok Shop and Amazon: listings, prices, offers, ratings, review themes, which creators already sell nearby products. A shop listing or a creator showcase is not proof of sales.
## 3. Separate attention from buying
Views, likes and saves are **attention**. Questions about price or availability, comparisons, "I bought it", repeat use and recommendations are **buying signals** (the buying scale in `listening-craft.md` § Classify). Product requests and workarounds are the strongest signs of an unmet need. Count each kind separately.
## 4. Score each hypothesis
On five things, in words: how strong the evidence is · how consistent it is across sources · how recent · how varied the sources are · how close it is to an actual purchase. A hypothesis resting on one source, or only on attention, is "weak".
## 5. Recommend the cheapest next test
One test with a pass mark, chosen to settle the weakest important hypothesis cheaply: five buyer interviews · a landing page with a waitlist (pass: <n> sign-ups from <n> visitors) · a pre-order or deposit · an offer test to existing customers · one creator test · an ad-message test (pass: <click or sign-up rate> against the brand's usual).
## The report's top
- **In short** (write-report §1): "What we looked at" (the idea, the sources, the date, the main limit); then "**Verdict:** proceed · refine · test further · weak evidence", with the 2–3 findings behind it, each with how sure; then "So, do this first (because of …)": the test and its pass mark.
- **Decisions for you:** go or no-go on the test, the price to test, who runs it.
- In the story, a hypothesis table: hypothesis · what supports it (linked) · what weakens it (linked) · score in words. No market-size claims beyond what a source supports.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| add-product-e2e-evalpaperclipai/paperclipAdd or extend a Paperclip full-stack runner E2E workflow, fixture, matcher, or report evidence path for local or Daytona execution. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| add-runner-evalpaperclipai/paperclipAdd or extend a Paperclip Runner protocol evaluation definition, roster, assertion, or report fixture with provenance and narrow validation. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| diagnose-why-work-stoppedpaperclipai/paperclipCompatibility entry point for failed, stalled, looping, or over-recovered Paperclip work. Use fix-failed-paperclip-run for the full diagnosis, regression, repair, real verification, and green-PR workflow; honor an explicitly requested diagnosis-only scope. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| fix-failed-paperclip-runpaperclipai/paperclipDiagnose and fix failed, stuck, slow, or incorrectly blocked Paperclip tasks and runs. Use with a task/run URL or failure report to trace the root cause, prove a regression red then green, check second-order effects, verify the real workflow, and deliver a PR with passing checks. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |