outreach

Every outward message obeys one principle: earn trust and make one clear ask, without over-promising. A cold email earns a reply when a stranger recognizes their own problem and one easy next step. For a sales asset, closing takes obvious value and credible proof, with the live objection already answered. A customer message holds trust by naming the situation plainly and owning it, then stating what happens next.

This skill drafts only. Sending anything (an email, a public post, a status-page update, an in-app banner, a sequence handed to an automation tool) is an external mutation against real recipients, a sender's domain reputation, or what every customer sees, and it cannot be taken back. So this skill never sends and never schedules a send: the user reviews every message and the user sends it. Hand the finished draft back and stop.

Route the request to one of three jobs first, then follow that job's depth:

• Cold outbound to strangers. See the cold-email reference for anatomy, personalization tiers, deliverability and spam, the one-CTA rule, follow-up cadence, CAN-SPAM and GDPR, and a worked sequence.
• Sales assets that close a known deal. The sales-enablement reference covers the asset taxonomy, value-led drafting, proof structures, the acknowledge→reframe→evidence→confirm objection framework, battlecards, ROI framing, and a worked objection.
• Customer and PR messages. See the customer-comms reference for message types, tone calibration, the hard-news five-beat structure, incident and crisis basics, saying sorry well, avoiding legalese and over-promising, and a worked outage apology.

Steps

1. Route the request and name the one job. Pick the lane (cold outbound, sales asset, or customer/PR message) and write one sentence stating the single job this piece must do for its reader. Done when the lane is named and the job is one sentence, with no second job blended in.

2. Gather what the lane requires. Pull the inputs that lane demands from the matching reference. A cold email needs a named persona plus a named trigger, and a sales asset needs the deal stage plus the one blocker. A customer message needs whatever facts its message type requires (for an incident: what happened, impact, status, fix, prevention). Done when every required input is recorded or marked as a gap to confirm with the user, with no invented detail.

3. Draft to the lane's structure, reader-first, one ask. Write to the shape the matching reference specifies (the six-part cold email, the value-led asset opening on the buyer's outcome, or the hard-news beats leading with the news), keeping the reader as the subject and carrying exactly one call to action or next step. Done when the draft follows its named structure and contains exactly one ask.

4. Attach proof and calibrate tone. Bind each value claim to evidence (a named result, a metric, a quote, a third-party signal) and set the register the situation demands (researched specificity for cold outbound, outcome-led credibility for a sales asset, the tone-calibration register for a customer message). Done when no value claim stands without evidence beside it and the register matches the news the reader is about to receive.