Draft relevant outreach without inventing familiarity
Use only information supplied in the conversation and this skill text. Do not browse, call tools, inspect files, execute code, create artifacts, or take external actions. Return the work directly in chat. Attribute material claims to supplied source labels or quotations; a pasted URL is a source label, not evidence that its contents were checked. Distinguish supplied facts, reasonable interpretations, proposals, and unknowns.
Inputs and scope: Obtain the recipient or audience, relationship context, supplied facts and source labels, approved offer, actual available assets, channel, tone, and desired call to action. Contact discovery and qualification are separate tasks. If a decision-changing input is absent, ask the smallest useful question and complete the portions supported by available material. State assumptions explicitly; do not manufacture facts, approvals, dates, or completion evidence.
Method 1. Identify the reason this recipient might find the message relevant using supplied evidence. Distinguish an observed event from inferred pain; a vacancy or website feature is not proof of a business problem. 2. Select the message objective and appropriate channel style based on the user's choice. Do not impose a universal phone-first order, fixed scoring weights, or a private founder's voice. 3. Write a grounded opener that acknowledges the observed context without claiming a prior relationship, conversation, or research that did not occur. Avoid intrusive personalization and exaggerated familiarity. 4. Connect the approved offer to a plausible benefit with supporting proof and necessary conditions. Mention a useful checklist, analysis, attachment, or demo only if it actually exists in the supplied material. 5. Use one clear, proportionate next step such as a short question, an invitation to compare priorities, or a proposed conversation. For phone scripts include an opener, permission-sensitive transition, key question, and natural close without claiming a call occurred. 6. Review brevity, tone, evidence, and recipient burden. Provide variants when they differ meaningfully in angle or relationship context, and return plain unsent text without contact verification, mailbox draft creation, or delivery claims.
Output: Return the message or script, optional subject line and variant, plus a brief note on material assumptions or unsupported personalization removed.
Quality checks: Check recipient facts, offer authorization, evidence specificity, asset existence, tone, and CTA consistency. Do not expand into list enrichment or claim the recipient has buying intent.
Worked example: The user supplies that a local distributor opened a second location and approves offering a free inventory-process conversation. Draft an opener about the expansion and ask whether inventory coordination is on the team's agenda. Do not assert that stock is being lost, claim an audit attachment exists, or say the recipient's email was verified.