Read survey results at group level with response rates, themes, and a minimum group size.
Instructions your experts follow when using this skill.
Use this after a survey closes, before results are shared.
Record invited, responded, and response rate, overall and per group. Apply the agreed minimum group size, five by default. Merge or hide any group below it, and do not show a breakdown that could be subtracted from another to reveal a small group. Say when a low response rate limits what the results can show.
For each theme give the score or share, the change from last time if the questions match, and two or three paraphrased comments. Remove names, roles, places, and phrasing that could identify the writer. Separate what the data shows from what it might mean.
Suggest no more than three actions, each tied to a theme, with an owner, a date, and how progress will be reported back to staff.
Never try to identify a respondent, guess who wrote a comment, or break results into groups below the minimum. Do not share the readout with staff; the people lead approves it.
Phrases that help your experts find this skill.
When the user wants to create or update their product marketing context document. Also use when the user mentions 'product context,' 'marketing context,' 'set up context,' 'positioning,' 'who is my target audience,' 'describe my product,' 'ICP,' 'ideal customer profile,' or wants to avoid repeating foundational information across marketing tasks. Use this at the start of any new project before using other marketing skills — it creates `.agents/product-marketing.md` that all other skills reference for product, audience, and positioning context.
When the user wants to research, profile, or analyze competitors from their URLs. Also use when the user mentions 'competitor profile,' 'competitor research,' 'competitor analysis,' 'profile this competitor,' 'analyze competitor,' 'competitive intelligence,' 'competitor deep dive,' 'who are my competitors,' 'competitor landscape,' 'competitor dossier,' 'competitive audit,' or 'research these competitors.' Input is a list of competitor URLs. Output is structured competitor profile markdown files. For creating comparison/alternative pages from profiles, see competitors. For sales-specific battle cards, see sales-enablement.
When the user wants to conduct, analyze, or synthesize customer research. Use when the user mentions "customer research," "ICP research," "talk to customers," "analyze transcripts," "customer interviews," "survey analysis," "support ticket analysis," "voice of customer," "VOC," "build personas," "customer personas," "jobs to be done," "JTBD," "what do customers say," "what are customers struggling with," "Reddit mining," "G2 reviews," "review mining," "digital watering holes," "community research," "forum research," "competitor reviews," "customer sentiment," "PMF survey," "product/market fit survey," "customer interview questions," "interview outreach," "Sales Safari," or "find out why customers churn/convert/buy." Use for analyzing existing research assets, mining online sources, AND running primary research (interviews and surveys). For writing copy informed by research, see copywriting. For acting on research to improve pages, see cro.