Use when a researched prospect row needs its opening message by email, social, phone, or short public post.
Instructions your experts follow when using this skill.
Use this when a researched row needs its opening message. If the row has not been enriched yet, stop and route it to research before writing a word.
The target-list row with its hook and sources, the user's voice sample, the ask, and the proof they are allowed to cite.
Write from the row only:
Match the user's voice sample; if there is none, keep it plain and under 100 words for email, under 60 words for a social message, under 280 characters for a short public post, and under 30 seconds spoken for phone with a voicemail fallback line.
Email carries a subject in sentence case, four to five words; a short question naming the trigger is fine. Never use Re:/Fwd:, colons, or ALL CAPS in a subject.
Never invent a fact. No assumed funding, no guessed headcount, no quote they never said, no "I noticed you" without the link underneath. Proof points come only from what the user gave you.
Skip the banned openers: no "hope you're well", no "just bumping", no "pick your brain", no flattery without a fact behind it. No emoji and no exclamation points in any draft.
Show the draft in chat with the source links under it and one line on what you left out. Mark the row drafted with today's date in drafted_on, and save. The draft is unsent, so log no outreach touch: that entry goes in only after the user confirms the send, or the row reads as contacted when nobody was.
Output: the unsent first-touch draft with sources, plus the row update.
A thin row with no hook means you say so and offer the two weakest lines to fix by research, or a plain intro draft they approve as-is. A channel you cannot shape for means you ask which of the four to use.
Approval gate: 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.