agentleFS
SkillMedevSkillMedev/people-ops-recruiting/skills/offer-rejection-writer/SKILL.md

offer-rejection-writer

Skill0 starsChanged 40 days agoMITView on GitHub

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.

The file

We split this skill into the rules it gives an agent

9 rules. About 0 are common, 9 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈9

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Check the legal and fairness bounds (see below) before finishing.

    line 15
  2. Distinctive:

    Every compensation figure traces to an external, approved source - never a model guess.

    line 23
  3. Distinctive:

    Do not invent, estimate, or suggest a compensation, equity, or vesting number.

    line 31
  4. Distinctive:

    Do not use pressure tactics, artificial scarcity, or exploding-deadline theatrics in an offer - flag any response window under 72 hours.

    line 32
  5. Distinctive:

    Do not state or imply a rejection reason connected to age, race, gender, religion, disability, family status, national origin, or any other …

    line 33
  6. Distinctive:

    Do not speculate about the candidate, use comparative ("we found someone stronger"), promissory, or defamatory language.

    line 34
  7. Distinctive:

    Do not bury the no, leave a fake door open, or promise feedback you cannot deliver.

    line 35
  8. Distinctive:

    Do not present the offer as the final binding legal contract.

    line 36
  9. Distinctive:

    Do not send anything yourself - output a draft for a human to review and send.

    line 37

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.
  • Detail given in rejections is consistent across candidates for the same role.
  • Every compensation figure traces to an external, approved source - never a model guess.
  • Timing matches stage: late-stage candidates get a personalized note or call; nobody waits in silence.

Deliverable

Produce a send-ready draft (email or letter, as requested) marked "DRAFT - for human review," containing every required element for its type in the order above, with any missing input rendered as a bracketed placeholder (e.g., [BASE SALARY - confirm with comp owner]) plus a short reviewer's checklist listing: placeholders to fill, items needing legal or comp sign-off, and the recommended send-by date.

Do NOT

  • Do not invent, estimate, or suggest a compensation, equity, or vesting number.
  • Do not use pressure tactics, artificial scarcity, or exploding-deadline theatrics in an offer - flag any response window under 72 hours.
  • Do not state or imply a rejection reason connected to age, race, gender, religion, disability, family status, national origin, or any other protected characteristic.
  • Do not speculate about the candidate, use comparative ("we found someone stronger"), promissory, or defamatory language.
  • Do not bury the no, leave a fake door open, or promise feedback you cannot deliver.
  • Do not present the offer as the final binding legal contract.
  • Do not send anything yourself - output a draft for a human to review and send.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.