Menu

Individual skill

offer-rejection-writer

0upvotes

Drafts unambiguous candidate offer letters and respectful, legally-careful candidate rejection notes for a human to review and send. Use when you are asked to write, draft, or word an offer letter, an offer email, or a candidate rejection/decline note - or to soften, tighten, or de-risk an existing draft of one. Do NOT use when writing performance feedback for a current employee - use feedback-writer instead.

skills/offer-rejection-writer/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
Yes
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
Draft external candidate offer and rejection communications that are clear, warm, and legally careful; you draft, a human recruiter or hiring manager reviews and sends.

## Workflow
1. Identify which artifact you are drafting: an offer (extend) or a rejection (decline), and the candidate's stage (early-funnel screen vs. late-stage interviewed). Stage sets length, channel, and personalization.
2. Gather the inputs you must not invent. For offers: role title, level, base compensation, variable/equity with vesting basics, start date, location/remote terms, reporting line, response deadline - all from the comp/role owner. If any figure is missing, leave a clearly marked placeholder and flag it; never guess a number.
3. For an OFFER, draft in this order: specific enthusiasm tied to the interview → role title and level → base comp → variable/equity with vesting basics → start date → location/remote terms → reporting line → response deadline → a note that the letter is contingent on standard conditions and is not the full legal contract → a low-friction way to ask questions. A reasonable response window is 5-7 business days; anything under 72 hours reads as a pressure tactic and should be flagged back to the hiring team.
4. For a REJECTION, draft in this order: thank them for the specific time invested → deliver the decision plainly in the first two sentences → a truthful, job-related, non-comparative reason OR an honest statement that you cannot give individualized feedback → an open door only if it is genuinely real. Never bury the no.
5. Match effort to investment. A candidate who completed a screen gets a short, prompt note; one who invested 3+ hours of interviews (onsite, take-home, panel) warrants a personalized note or a call. Rejections should go out within 2-3 business days of the decision - every day of silence past a week actively damages the employer brand.
6. Check the legal and fairness bounds (see below) before finishing.
7. Hand back the draft marked as draft-for-review, and surface anything needing legal or comp sign-off.

## Quality bar
- An offer leaves zero ambiguity about terms: a reader knows exactly what they are being offered and by when to respond.
- Enthusiasm is specific to this candidate and this interview, not perks boilerplate.
- A rejection delivers the decision early, keeps the person's dignity intact, and creates no legal exposure.
Back to top