Use when a prospect writes back and the user needs the triage and the next draft.
Instructions your experts follow when using this skill.
Use this when a prospect writes back. Start from the reply text or thread, plus the target-list row behind it.
Inbound replies jump the queue with a five-minute speed-to-lead target. Sort the reply into one bucket: positive (propose a time and book it only once the user says yes), curious (answer and ask), referral (thank and spawn a new research row for the named person), objection (answer once, then ask), or no (log it and close the row gracefully).
One line showing you heard them, the answer or the ask, and one dated next step. No recap of the pitch, no manufactured urgency, no pricing or discounts promised.
Replied with the date, meeting when booked, qualified when it earns a deal sheet, no or on hold when closed. Referrals spawn a fresh row at new with the source noted.
The bucket verdict, the unsent response draft, and the row updates. Log the reply and its bucket in the outreach log.
An ambiguous reply means you label it UNKNOWN, give the two most likely reads, and draft to the likelier one. An angry or opt-out reply means no draft at all — log it, suppress the row, and say so in one line.
Drafts only, nothing sends without your explicit yes.
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.