Individual skill
research-market
Market 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.
skills/marketing/research-market/SKILL.md
Source commit df8298140d434a6363de0c265eb6af2e571d97a5
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 11, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,315
- Repository last updated
- Nov 6, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- claude Repository topic
- claude-skills Repository topic
- claudecode Repository topic
- claudecode-skills Repository topic
- codex Repository topic
- cursor Repository topic
- gtm Repository topic
- skills Repository topic
- marketing Derived category
- research Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 10,829 bytesreferences/idea-validation.mddoc · 3,011 bytesreferences/listening-craft.mddoc · 11,837 bytesreferences/positioning.mddoc · 6,022 bytesreferences/report-format.mddoc · 8,677 bytesreferences/run-memory.mddoc · 9,627 bytesskill.meta.jsonasset · 5,051 bytestests/examples/2026-10-22/positioning.mddoc · 8,143 bytestests/fixtures/positioning-evidence.mddoc · 3,264 bytestests/test-by-hand.mddoc · 6,897 bytes
Read excerpt
# research-market
Market research decides **which market the brand is in, how big the reachable part is, and what's changing in it** — then what that means for the brand. It reads the buyer groups research-audience owns and sizes them; it doesn't build its own. Rivals get one short section that points to competitor research. It also runs a light **brand watch**: risk first, alerts only. The worker briefs are its step skills (`research-market-<step>`) and the craft is in `references/`, next to this file.
**The rule that matters most: free pass first, ask nothing, report once** (`../marketing-guide/research-pattern.md` (in the `marketing-guide` skill) — read it before the first search). Do every dimension before the first message to the marketer; never stop to ask "go deeper?"; never ask for free work. A broad ask gets everything; an ask that names an area — **the market** · **what people are saying** — gets that area covered completely, with news first.
## Before you start
1. **Setup first:** do the `marketing-guide` skill (`../marketing-guide/SKILL.md`) §1–2 (connect, brand, brain read) before anything else; the job line is "I research your market and save what I find through it." Here: call `get_started` with `wants: "more"`; a named brand not in the account → create it from its website (`gooseworks:brand_setup_create`) without asking and wait for its research (`gooseworks:job_get`); don't show a menu unrelated to research. Fallback brand read: `gooseworks:brand_read` (`summary`, `kit`, `products`, `competitors`, `learnings`, `sources`, `organic`, `accounts`) and `gooseworks:knowledge_search`. Either path: `gooseworks:competitor_read`; workspace: `research/market/` (the last report and watch log), `research/audience/` (`buyer-groups.md` — the groups with their counts — and the latest audience report), `research/competitors/` (the latest report), `plans/`, `research/credits-log/`. Where the brain and the website differ on a brand fact, say so and use neither as a claim. Claims: only the read step of the `claims-gate` skill (`../claims-gate/SKILL.md`) now.
2. **Positioning ask:** when the user wants positioning choices, a new position or finished messages, complete `references/positioning.md` after setup and return. It reuses the saved research and fills only its evidence gaps; a full market-size report is not a prerequisite.
3. **Run memory:** job `market research`, `market pulse` or `brand watch`; what this job hands the atom is in `references/run-memory.md`. Its "since last time" opens the chat and the report's story.
4. **An idea, not a market?** When the ask names a product, offer or concept that doesn't exist yet ("is there demand for …?"), run the same steps pointed at it, with `references/idea-validation.md`.
5. Never change the host's settings, and never seed a search with names or claims from memory.