Use when a sent opener got no reply and the row needs its next touch in the sequence.
Instructions your experts follow when using this skill.
Run this when a sent opener got no reply and the row needs its next touch. The row must be marked sent by the user; if it is not, ask rather than treating the opener as delivered.
The target-list row, the earlier touches with dates, and any new public fact about the person or company since.
Eight touches, multi-channel, over three to four weeks, front-loaded: days 1, 3, 5, 7, 10, then spaced a week apart. Never stop before attempt five. Rotate the channel per touch — email, call, social — with a new angle on the same pain each time. Touch two lowers the door with a smaller ask; middle touches add a useful link or a referral ask; the last touch closes clean with a graceful no-pressure goodbye, then the row recycles to the nurture pool for a 60-to-90-day revisit. Any reply at any point ends the sequence.
Say the send date on each draft. Each touch holds the no-invented-facts rule and the user's voice. Each touch is shorter than the last; late touches run two sentences. No emoji, no exclamation points, none of the banned openers.
Show the draft in chat with one line on which touch it is and why this angle. Mark the row with next_step, record the draft as pending, and save. Leave last_touch_on alone and log no outreach touch until the user confirms the send — writing either from an unsent draft puts false state in the CRM and shifts every later cadence date.
The unsent follow-up draft with its touch number, plus the row update.
Nothing new to say: say so and suggest waiting for a trigger instead of burning the row. A reply that arrived mid-sequence: stop and switch to Handle a reply.
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.