Skip to content

bereach-ai/linkedin-prospecting-skills / skills/cold-email

cold-email

Verified

Writes cold emails and follow-ups for people in a BeReach list: finds work emails, one sequence per persona, drafts the user sends. Use for any cold email or email outreach.

FileKindSize
SKILL.mdskill md8.5 KB
references/artifacts.mdmarkdown7.6 KB
references/deliverability.mdmarkdown3.1 KB
references/frameworks.mdmarkdown12.7 KB
references/legal.mdmarkdown3.5 KB
references/sequence.mdmarkdown2.2 KB

references/sequence.md

View on GitHub
# The sequence

3 or 4 emails over about two to three weeks. The first email brings about half the replies; follow-ups roughly
double the total. Later steps still add a little; we cap at 4 to stay on good terms.

## The default timeline

| Day | Email | Words | What it does |
|---|---|---|---|
| 1 | First email | 50 to 90 (body, footer not counted) | About them, who writes, one yes/no question |
| 4 | Reply in the same thread | 20 to 40 | One new angle or one more proof. Same subject, sent as a reply. |
| 8 | New short email | 30 to 50 | A new angle on the same offer: another problem it solves, a number or peer story the user gave. Never a second offer |
| 14 | Last, easy out | 15 to 30 | The offer and a plain way out in one question where yes moves forward: "Shall I send the checklist, or leave it there?" |

Space 3 to 4 days at first, wider later. Weekdays, in their working hours. No "best hour" is proven.

## Follow-up rules

- Each one adds something and ends on one easy yes/no question. "Just bumping this" adds nothing.
- Step 2 as a reply in the same thread reads like a person and does about 30% better than a formal follow-up
  (one large vendor dataset).
- Stop the sequence the moment they reply, on any channel.

## Subjects

- 1 to 5 words (30 to 40 characters show on a phone). Plain. About them or the topic: "hiring two SDRs", "lists for new reps".
- Matches the body. No "Re:" or "Fwd:" on a first email (misleading subjects are illegal in the US).
- A fake-casual "quick question" did slightly worse than average in one large dataset.

## Length and style

- Short sentences, one idea each, everyday words. Written for a phone.
- No greeting filler, no "I hope you are well", no "I am reaching out because".
- Signature: name, role, company, one line. No banner, no logo, no social icons.

## What to measure

Replies only. Open counts are unreliable (many are automatic loads, not reads). Per persona:

| Count | Healthy | Act if |
|---|---|---|
| Reply rate | depends on market; compare with your own last batch | falls two batches in a row |
| Bounces | under 2% | over 2%: stop, check the list |
| Spam complaints | under 0.1% | 0.1% or more: stop and review targeting |
| Opt-outs | a few | rising: the message or the targeting is off |
slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack."Stars: 198kUpdated Claude CodeCodexVerifiedInstall
ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read.Stars: 196kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 196kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.Stars: 196kUpdated Claude CodeCodexVerifiedInstall