Skip to content
cccskills
FreePublished on GitHub

cold-email

Write a cold sales/B2B outreach email that earns a reply. Use when asked to write a cold email, a sales outreach email, a prospecting email, or a cold email sequence to a business prospect. Produces a short, personalised email — subject, a relevant opener, one clear value-led ask, and a low-friction CTA — plus 2 follow-ups, written to be replied to, not deleted.

The English summary is being prepared. Showing the original description.

See how to install

Files included (2)

  • SKILL.md3.8 KB
  • references/reply-rate-calibration.md2.0 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Cold Email Skill

Cold email works when it's short, clearly about them, and asks for one small thing. Most cold email fails because it's a feature dump that's all about the sender. This skill writes a tight, personalised email built on a real trigger or relevance hook, with a single low-friction ask — plus the follow-ups that actually drive most replies. (For job-search / networking outreach, use outreach-message; this is B2B sales prospecting.)

Not quite this? Use investor-cold-email when you are writing to investors rather than to prospective customers.

Required Inputs

Ask for these only if they aren't already provided:

  • Who you're emailing — role, company, and the segment/ICP.
  • The relevance hook — a real reason to contact them now (a trigger event, a specific pain in their role/industry, a mutual connection).
  • What you offer — the outcome you drive for people like them (not your feature list).
  • Proof — a comparable customer, a result, a number.
  • The ask — ideally low-friction (a 15-min call, a relevant resource, an "open to it?" reply).

Output Format

Cold Email: [offer] → [persona]

Subject lines — 3 options, short (≤6 words), specific, no clickbait or "Quick question."

The email (≤120 words):

  • Opener — the relevance hook: something true about them (trigger, pain, connection). Not "I hope this finds you well."
  • Value — the outcome you drive for people in their seat, with one proof point. One or two sentences.
  • Ask — one clear, low-friction request, phrased to make "yes" or even "not now" easy.
  • Signature — minimal.

Follow-ups — 2 short ones (send ~3–4 days apart): a value-add nudge (a resource/insight, not "just bumping this") and a graceful breakup email ("I'll close the loop — want me to circle back next quarter?"). Most replies come from these.

Note — what to personalise per prospect (the one line that proves it isn't a blast), and the one metric to watch (reply rate, not open rate).

Deeper Materials

Quality Checks

  • Under ~120 words and skimmable on a phone
  • Opens with a real, specific relevance hook about the recipient
  • Frames value as the prospect's outcome, with one proof point
  • Exactly one low-friction ask
  • Includes 2 follow-ups (value-add + graceful breakup)
  • Subject is specific and honest (no bait)

Anti-Patterns

  • Do not open about yourself ("We're a leading platform…") — lead with them
  • Do not feature-dump — one outcome + one proof beats a capability list
  • Do not stack asks or ask for too much ("30-min demo" cold) — make the first yes tiny
  • Do not use fake personalisation ("loved your post!") — be specifically, verifiably relevant or don't claim it
  • Do not skip follow-ups or make them "just checking in" — each must add a reason to reply

Based On

B2B cold-email practice — relevance/trigger-led openers, one-outcome value, single low-friction ask, value-adding follow-up cadence.

Example Trigger Phrases

  • "Write a cold email."
  • "Write a sales outreach email to this prospect."
  • "Write a prospecting email."
  • "Draft a cold email sequence for a business prospect."

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Design a 360-degree feedback survey or write a structured 360 feedback report. Use when asked to build a 360 feedback process, write 360 feedback for a colleague, design a feedback survey, or produce a feedback report. Produces either a complete survey instrument with rating scales and open-ended questions, or a structured narrative feedback report with themes, strengths, and development areas.

The English summary is being prepared. Showing the original description.

mohitagw15856/pm-claude-skills1.5KUpdated Oct 23, 2026

Decode a 401k or workplace retirement plan — the real cost of its funds, the match's fine print, vesting math, and the plan features worth using or avoiding. Use when someone asks 'is my 401k any good', 'decode my 401k plan', 'which funds should I look at', or 'what fees am I paying'. Produces a fee decode in dollars-over-time, match and vesting math, a fund-lineup triage by cost, and the questions for HR or the plan administrator.

The English summary is being prepared. Showing the original description.

mohitagw15856/pm-claude-skills1.5KUpdated Oct 23, 2026

Design statistically rigorous A/B tests for product features, UI changes, onboarding flows, and pricing experiments. Use when asked to set up an experiment, design an A/B test, calculate sample size, or interpret test results. Produces a complete test plan with hypothesis, variant definitions, sample size, duration estimate, guardrail metrics, and a results interpretation guide.

The English summary is being prepared. Showing the original description.

mohitagw15856/pm-claude-skills1.5KUpdated Oct 23, 2026

Analyse a finished A/B test and write the readout — the result, whether it's statistically and practically significant, what it means, and the ship/no-ship call. Use when asked to analyse experiment results, write an A/B test readout, interpret test data, or decide whether to ship a variant. Produces a clear verdict with the lift and confidence, segment cuts, the risks (peeking, novelty, sample), and a recommendation. Distinct from planning a test — this reads results.

The English summary is being prepared. Showing the original description.

mohitagw15856/pm-claude-skills1.5KUpdated Oct 23, 2026

Build or tailor an academic CV for faculty, postdoc, research or fellowship applications: publications, grants, teaching, supervision and service in the order the field expects, with consistent citations. Use when asked to write my academic CV, update my CV for a lectureship, tenure-track or postdoc application, format my publications list, or adapt my academic CV for an industry research role. Produces the full academic CV, a field-appropriate section order, a clean publications list in one citation style, and a two-page summary version when asked.

The English summary is being prepared. Showing the original description.

mohitagw15856/pm-claude-skills1.5KUpdated Oct 23, 2026

Generate a WCAG 2.2 accessibility audit checklist and remediation suggestions for any UI or design. Use when asked to audit for accessibility, check WCAG compliance, review a design for a11y issues, or create an accessibility remediation plan. Produces a prioritised checklist with pass/fail assessments and specific fixes.

The English summary is being prepared. Showing the original description.

mohitagw15856/pm-claude-skills1.5KUpdated Oct 23, 2026

See all skills by mohitagw15856

Report a problem with this skill