Drafts short, honest recruiting outreach and InMail messages to a passive candidate, anchored on one researched, candidate-published professional fact, for a human recruiter to review and send. Use when someone asks "write an InMail to this engineer", "personalize this sourcing message", "draft outreach from this profile", or is contacting a passive candidate about a specific role. Do NOT use for sales or founder cold email to prospects - use cold-email-craft. Do NOT use for designing the multi-touch cadence, channel mix, and follow-up timing around the message - use outreach-sequence-designer. Do NOT use for writing the job description itself - use job-description-writer.
Click to play with sound.
---
name: Candidate Outreach Personalizer
description: Drafts short, honest recruiting outreach and InMail messages to a passive candidate, anchored on one researched, candidate-published professional fact, for a human recruiter to review and send. Use when someone asks "write an InMail to this engineer", "personalize this sourcing message", "draft outreach from this profile", or is contacting a passive candidate about a specific role. Do NOT use for sales or founder cold email to prospects - use cold-email-craft. Do NOT use for designing the multi-touch cadence, channel mix, and follow-up timing around the message - use outreach-sequence-designer. Do NOT use for writing the job description itself - use job-description-writer.
---
# Candidate Outreach Personalizer
Draft a short, honest, easy-to-decline recruiting message that earns a reply because it is unmistakably about this candidate and this role. The costly mistake this prevents is the template blast: passive candidates receive a steady stream of "your background is impressive" messages, and one more of those doesn't just get ignored - it burns the company's name with exactly the people it wants to hire. One researched fact beats three generic compliments every time.
## Operating procedure
### Step 1: gather inputs
- The candidate's public professional profile (URL or pasted summary).
- The role: title, level, scope, team, location/remote policy, and the pay range where disclosure is required.
- The sender: who the message is from (recruiter, hiring manager, founder) and their real connection to the role.
- Any true, specific reason this candidate surfaced (a project, a talk, a repo - not "the algorithm").
If the role's level or pay range is unknown, ask; guessing either produces a message that misleads.
### Step 2: extract only candidate-published, job-relevant facts
Read the profile and pull role history, projects, talks, published writing, open-source work, and tech stack choices. Discard anything personal, unconfirmed, or found outside a professional context. If a fact's provenance is uncertain, treat it as unusable.
### Step 3: pick exactly one concrete hook… install to load the full skill