skills/recruiter-outreach/SKILL.md
Write personalized candidate outreach that gets replies. Use when asked to write a recruiter InMail, a candidate outreach email, a sourcing message, or a follow-up sequence. Produces a short, personalized first message (hook tied to the candidate, the role's appeal, a low-friction ask) plus a 2–3 step follow-up sequence — honest and candidate-respectful, not spammy.
npx skillsauth add mohitagw15856/pm-claude-skills recruiter-outreachInstall 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.
Passive candidates ignore generic blasts. Replies come from messages that are short, clearly personalized, and about them — why this role fits their trajectory, not a copy-paste pitch. This skill writes that first message and a light follow-up sequence, with a low-friction ask that makes saying "tell me more" easy.
Given "reach out to a senior designer at a competitor for our staff design role", write the message anyway — infer a credible personalization hook and the role's genuine appeal, marking specifics (insert real detail) so the recruiter swaps in something true. Never fabricate a personal detail as if verified; never write a wall of text.
Ask for these only if they aren't already provided (else infer and label):
First message — short (think 4–6 sentences / under ~120 words):
[insert real detail]).Subject line (if email) — 2–3 options, specific not clickbait.
Follow-up sequence — 2–3 spaced messages: a gentle bump, a value-add angle (something new about the role/team), and a polite final "I'll stop here, but the door's open" — each short and non-pushy.
Notes — mark every [insert real detail]; keep claims about comp/role honest.
Candidate-sourcing practice — concise, candidate-centric personalization, benefit-led framing, low-friction asks, and respectful multi-touch follow-up.
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.