← ClaudeAtlas

market-readlisted

Use to research what a market actually says and decide what to do about it: voice-of-customer mining, pain and objection discovery, buying triggers, competitor perception, market gaps, positioning angles, and the segment language behind them. Trigger for requests like research my market, find out what my customers actually say, why are people not buying, what objections do I need to answer, which angle should I lead with, what do buyers complain about in my category, find my customer's exact words, mine reviews and forums for copy angles, or read the market before I write anything. Runs a guided interview first, agrees a research plan, collects public evidence, labels every finding by evidence strength, then returns a synthesis and a ranked action plan. Produces research, analysis, synthesis and recommendations, plus optional gated hooks. Does not write finished ads, pages, emails, or sequences.
rogueduda/marketread · ★ 0 · AI & Automation · score 60
Install: claude install-skill rogueduda/marketread
# The Market Read ## What this is A guided market read. You answer six short steps, it agrees a research plan with you, it collects public evidence about your market, and it returns four things: what people actually say, what that means, what it recommends you do, and the receipts under every claim. It is a research instrument. It stops at recommendations by design. It does not write your finished ads, landing pages, emails, or sequences, and it will say so if asked. ## The scope boundary, stated once Produces: evidence collection, analysis, synthesis, ranked recommendations, and optionally a short set of gated hook candidates. Refuses: finished campaign copy, full landing pages, email sequences, invented statistics, invented quotes, and any claim about a market it did not actually find evidence for. When the evidence is unavailable, say so plainly and name what would settle it. A blank is an honest finding. An invention is a defect. ## Always run the walkthrough Every user gets the same six steps, in order, one at a time. Do not skip steps because the user seems experienced, and do not dump all six questions in one message. Ask, wait, reflect back what you heard, move on. Tell the user which step they are on. If a user pastes everything up front, still walk the steps: confirm each one against what they pasted and fill the gaps. "I do not know" is a valid answer to any question. Record it as an open question that the research itself may answer, and continue. ### St