# Draft Personalized Cold Email Sequences

Cold outreach needs relevant contacts, credible personalization, and careful review. This skill guides BeReach list selection, address lookup, and persona-based email drafts for user approval.

## Install

```bash
npx skillstore add bereach-ai/cold-email
```

## Metadata

- Status: approved
- Slug: bereach-ai-cold-email
- Skillstore revision: r1
- Version status: missing
- Tree hash: 04eed354c914e4ed0bb3f46ad2df00d857cbd9c5c2999cbbad1faf3c7275c5d2
- Author: bereach-ai
- GitHub username: bereach-ai
- Repository: https://github.com/bereach-ai/linkedin-prospecting-skills/tree/6967fde3a1b93fd84e2dfa6be39f56113d79ceca/skills/cold-email
- Ref: 0b5375d5ff31ef8f8f23150e2d3ac5978ea0441f
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands
- Quality score: 71
- Public page: https://skillstore.pages.dev/skills/bereach-ai-cold-email
- Manifest: https://skillstore.pages.dev/api/skills/bereach-ai-cold-email/manifest

## Capabilities

- Group BeReach contacts by persona and exclude do-not-contact, previously processed, or out-of-scope people.
- Request approval before paid email lookups and accept only addresses marked verified.
- Draft three- or four-email persona sequences with short subjects, factual personalization, and one offer.
- Provide sending checks, country-specific footer guidance, draft review pages, and copy blocks with CSV handover.
- Record outreach tags and do-not-contact status through BeReach contact tools.
- Summarize user-provided replies, bounces, opt-outs, and batch results without estimating missing counts.

## Use Cases

- Prepare a first outreach batch: Review sending readiness and draft a short sequence for a small, relevant BeReach contact list.
- Coordinate persona-based prospecting: Separate sales prospects by persona, approve lookup costs, and review personalized drafts before manual sending.
- Compare outreach results: Review mature batch results from supplied counts and select one message change for the next test.

## Prompt Templates

### Check sending readiness

```
Review my sending setup: [mailbox], [authentication status], [daily volume], [recipient countries], and [tracking settings]. List issues without looking up addresses.
```

### Draft one persona sequence

```
Draft a four-email sequence for [persona] using [offer] and my saved voice card. Use only supplied facts and include appropriate opt-out wording.
```

### Prepare a reviewed contact batch

```
Prepare campaign [campaignId] in batches of at most 25. Show persona assignments and estimated costs before spending credits. Request approval before lookup and handover.
```

### Design the next batch test

```
Analyze these dated batch counts by persona: [counts]. Exclude immature batches and rates below ten sent. Compare passing versions and propose one change.
```

## Limitations

- Does not send emails, read a mailbox, or run follow-up delivery; the user manages those actions.
- Requires connected BeReach tools for contact operations; address lookup and enrichment can consume credits.
- Relies on saved persona and voice cards, with companion skills needed when those records are missing.
- Does not guarantee deliverability, reply rates, or legal compliance; country rules require independent verification.

## Best Practices

- Confirm recipient eligibility, suppression status, country rules, and lookup costs before approving paid work.
- Use sourced, dated facts and a deliverable offer; review every personalized draft before handover.
- Send from your own mailbox with tracking off, honor objections immediately, and report actual batch counts.

## Anti Patterns

- Sending to guessed addresses, unverified contacts, or people who requested no further contact.
- Inventing personalization, customer results, reply counts, or evidence for an offer.
- Treating draft handover as automatic delivery or using LinkedIn messaging tools to send email.

## Security Audit

- Audited at: 2026-11-14T17:28:09.878\+00:00
- Summary: All 41 static findings are false positives involving Markdown formatting, ordinary writing examples, and email compliance guidance. No evidence found of shell execution, weak cryptography, system reconnaissance, prompt injection, or unauthorized exfiltration in the six reviewed files. The workflow uses BeReach contact tools, requires approval before credit spending and draft handover, and leaves email sending to the user.

## Stats

- Views: 0
- Downloads: 2
- Favorites: 0
- Popularity score: 0
