skills/cold-email/SKILL.md
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.
npx skillsauth add mohitagw15856/pm-claude-skills cold-emailInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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.)
Ask for these only if they aren't already provided:
Subject lines — 3 options, short (≤6 words), specific, no clickbait or "Quick question."
The email (≤120 words):
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).
B2B cold-email practice — relevance/trigger-led openers, one-outcome value, single low-friction ask, value-adding follow-up cadence.
business
Analyze why deals are won and lost and turn it into an action plan. Use when asked to run a win/loss analysis, review closed-won and closed-lost deals, understand why the team is losing to a competitor, or summarize sales feedback into patterns. Produces a structured win/loss report with themes, win/loss rates by segment and competitor, representative quotes, and prioritized actions for product, marketing, and sales.
development
Route a fuzzy request to the right skill in this library. Use when the user is unsure which skill fits, asks 'which skill should I use for X', describes a task without naming a skill, or when a request could plausibly match several skills. Produces a best-fit recommendation with the inputs to gather, a runner-up with the tie-breaker, and a workflow recipe when the job spans multiple skills.
testing
Triage a vulnerability or scanner finding — assess real severity, exploitability, and how urgently to fix. Use when asked to triage a CVE, prioritize scanner/pentest findings, assess a vuln's risk, or decide what to patch first. Produces a triage verdict: CVSS-informed severity adjusted for your context, exploitability, real risk, a fix/mitigation, and an SLA — so you fix what matters, not just what's red.
development
Stand up a Voice of Customer (VoC) program that turns feedback into action. Use when asked to build a VoC program, design a customer feedback loop, consolidate feedback sources, or set up a closed-loop feedback process. Produces a VoC program design — objectives, feedback sources and channels, a taxonomy, collection and analysis cadence, closed-loop routing, ownership, and success metrics.