Draft a short reply in the principal's voice, with any commitment marked to confirm.
Instructions your experts follow when using this skill.
Use this for one email or a short batch of related replies.
Read the full thread. Write down, in one line each, what the sender wants, by when, and what the principal has already said. If the ask is unclear or the principal's answer is not known, say so and ask rather than guess.
Match the principal's sent mail: greeting, length, sign-off, and how direct they are. Keep it short. Answer the question asked, and no more:
Do not carry details from other threads into the reply unless the principal asked you to.
Under the draft, list every commitment it makes: a meeting, a date, a deliverable, money, or a yes to a request. Mark each one for the principal to confirm or remove before sending.
Never send the reply without a clear yes. Do not agree to a meeting, deadline, or favour on the principal's behalf, and never invent what someone said.
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.