Cold outreach email
Writes a short, specific first-contact email from what you know about the company.
Sales · produces a Email · built in, ready to run
What you give it
Something like this:
Company: Kanwal Foods, Lahore. Mid-size frozen food maker, sells through 400 kiryana stores. They just posted on LinkedIn that they are opening two new distribution hubs. Their reps still take orders on WhatsApp and re-type them into Excel. We build order-capture apps for distributors.
What you get back
This is a real run of the skill on the input above, not a mock-up:
**Subject:** Two new hubs—order bottleneck just got bigger
Your new distribution centers will move more volume, but manual WhatsApp-to-Excel order entry scales linearly with headcount, not throughput. We build order-capture apps that let your reps log orders once and sync them straight to your backend, cutting data-entry time by 70%.
With 400 store relationships, you're likely losing orders in transcription and spending cycles on re-keying.
Could a 15-minute call help you see how this works for similar-sized food distributors?
The wording changes a little every run. The shape does not — that is what the procedure below is for.
Tools it uses
None of its own. A skill that only writes needs no tools, so this one inherits whatever your assistant can normally reach.
The procedure it follows
This is the skill, in full. Add it to your own skills to change any of it.
Write a first-contact email to the company described below.
Rules:
- Under 120 words
- Open with something specific to them, never "I hope this finds you well"
- One sentence on what we do, framed as their problem, not our features
- End with one low-friction ask (a 15-minute call, or a yes/no question)
- No buzzwords, no exclamation marks, no fake urgency
Output the subject line and the body. Nothing else.
How to run it
| Where | How |
|---|---|
| Chat | "Run my Cold outreach email skill", or pick it from the + menu |
| Skills page | Find Cold outreach email under Library and press Add & Use |
| Automations | Invoke it on every trigger |
| API | POST /v1/skills/{id}/run — add it to your own skills first, then take the id from GET /v1/skills |
In chat, on the Skills page and in automations you do not have to add it first — a library skill runs as it is. Adding it makes an editable copy under your own skills, which is what you need to change the wording, and what the API works against.
New to skills? Start with what a skill is.