When to use it

Use it when a draft sounds polished but its relevance, proof, or next step is unclear. It can also catch a mismatch between the commercial terms you supplied and the terms implied by the email.

Input
The draft email, audience context, offer terms, approved proof, and sending-platform placeholder format.
Output
The main issues, one revised email, and the facts to confirm before using the draft.
Requirements
Claude Code and your supplied campaign material. The template drafts and reviews; it does not need a sending-platform connection.

Install in your project

  1. Download the file below.
  2. Save it as .claude/skills/cold-email-review/SKILL.md in your project.
  3. Start Claude Code there and invoke /cold-email-review with the required inputs.

Project skill locations and slash commands follow Anthropic’s skills documentation.

Download SKILL.md ↓

Example prompt:

/cold-email-review Review draft.md using brief.md and proof.md. Preserve the offer terms and flag any unsupported claim or uncertain merge-field syntax.

The complete SKILL.md

Copy or download the same file. Adapt the inputs and output to your workflow before using it.

SKILL.md
---
name: cold-email-review
description: Review or rewrite a supplied B2B cold email using an offer, buyer context, approved evidence, and a specific next step.
---

# Cold-email review

Review the supplied draft against the user's offer, audience, and approved proof.
Keep the sender's intent and commercial terms intact. If a missing fact would
change the message, identify it instead of inventing a replacement.

## Review

- Check whether the opening gives this buyer a supported reason to read.
- Connect the proposed benefit to the offer. Keep a business observation separate
  from an assumption about the buyer's priorities or active demand.
- Preserve approved prices, scope, and meeting definitions. In particular, a
  booked appointment is different from an attended conversation.
- Use only supplied, approved customer evidence. Remove unsupported results,
  invented customer relationships, and claims that a demo already exists.
- Keep placeholders in the format supplied by the user's sending platform. Flag
  uncertain conditional or fallback syntax instead of silently changing it.
- Use one clear next step. Retain required sender identity and unsubscribe text
  supplied for the campaign.

## Output

Return the main issues, one revised email, and a short list of facts to confirm
before using it. Explain material edits to proof, offer terms, or personalization.
The revision should be concise, specific, and readable aloud. Do not claim the
email is legally compliant or guaranteed to land in the inbox. This is a drafting
and review task; it does not send messages or enroll contacts in a sequence.

Review the first result

Include a draft with an unsupported result and an uncertain fallback placeholder. Check that the revision uses only approved evidence, preserves the supplied offer, and flags syntax that has not been confirmed for your platform.

Adapt the template to your workflow and review each result before using it in a campaign.

Read the related guide or explore all three starter skills.