Menu

Individual skill

candidate-outreach-personalizer

0upvotes

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.

skills/candidate-outreach-personalizer/SKILL.md

Read pinned source

Source commit 97a13607d669157a4a16d5ba79b77f208319f7b9

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
24
Repository last updated
Oct 13, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# 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.
Back to top