agentleFS
osamabinjannatosamabinjannat/remote-hiring-skills/skills/candidate-emails/SKILL.md

candidate-emails

Skill1 starsChanged 30 days agoMITView on GitHub

Drafts kind, human candidate emails for a person to review and send. Covers application received, interview invite, candidate update or delay, rejection email at any stage, feedback to candidate, offer email or verbal offer follow-up, a declined offer and a candidate who's gone quiet. Use this whenever someone needs to turn down a candidate, invite someone to interview, explain a delay, share panel feedback or confirm an offer in writing, even if they only say "write to the candidate" or "send the no". Built for remote hiring, so times show in the candidate's zone first. Uses only the reasons and feedback you give, never decides who to reject, and ends every draft with a human review note.

The file

Show its rules and text

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈13

    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:

    Ask everything in one message, numbered.

    line 35
  2. Distinctive:

    Follow these rules for every email:

    line 49
  3. Distinctive:

    Lead with the news: Put it in the first two sentences.

    line 51
  4. Distinctive:

    Use only the facts the user gave you: Never invent a reason, a feedback point, a date or a promise.

    line 52
  5. Distinctive:

    Plain text: No tables, bold, emoji or images in the email.

    line 57
  6. Distinctive:

    Three days, at most: Every candidate hears back within 3 working days at every stage, even if the news is "no decision yet".

    line 61
  7. Distinctive:

    No scores and no comparisons: Don't share ratings, and don't mention other candidates.

    line 96
  8. Distinctive:

    No legal wording: Don't add probation, notice periods, "at-will", conditions, non-competes or intellectual property clauses.

    line 103
  9. Distinctive:

    Write one template with merge fields, such as [First name], [Role] and [Stage].

    line 108
  10. Distinctive:

    Write each email in this exact format.

    line 112
  11. Distinctive:

    After the emails, add a section called Notes on this draft, with these parts in this order:

    line 131
  12. Distinctive:

    Placeholders to fill in: every [placeholder] in the emails and what goes there.

    line 133
  13. Distinctive:

    Flag legal and compliance topics: Use this wording for every offer email, and whenever an email touches contract type, cross-border pay, …

    line 166

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

Candidate emails

Draft the emails a hiring team sends to candidates, from "we've got your application" to the offer. Keep them short, kind and honest. Every candidate hears back at every stage, because silence is the worst answer you can give.

AI drafts, humans decide. You draft the email. A person has already made the decision behind it, and a person reads, edits and sends it.

When to use this skill

  • Someone needs to tell a candidate no, at any stage.
  • Someone needs to invite a candidate to an interview or arrange a time.
  • A candidate is waiting and needs an update, or an apology for a delay.
  • A candidate has asked for feedback and the panel has given some.
  • Someone has made a verbal offer and wants to confirm it in writing, or needs a cover note for an offer letter.
  • A candidate has turned down an offer, or has stopped replying.
  • Someone needs one email to send to many candidates at once.

Step 1: Work out what you have

The user gives youDo this
The email type, the candidate and the key factsGo to Step 3. Don't re-ask anything already answered
Only a line, such as "write a rejection for the designer"Ask the questions in Step 2, then write the email from the answers
A list of candidates who all need the same newsWrite one template with merge fields, such as [First name] and [Role]. Don't write a different email, or a different reason, for each person
A request to decide who to reject, shortlist or offerDecline the decision with the wording in the Guardrails. Then write the template, ready for once a person has decided
Notes that mention age, family, religion, health or similarLeave them out of the email. Say so in "Notes on this draft"

Step 2: Ask for what's missing

Ask everything in one message, numbered. Never one question at a time. Skip anything the user already gave you. Tell them they can skip any question and you'll leave a [placeholder] for it.

  1. Which email is it? (See the list in Step 3.)
  2. The candidate's name, the role and the last stage they reached.
  3. Where is the candidate based, and which time zone is your team in?
  4. The key facts: dates, times, next steps and who the candidate should reply to.
  5. Any feedback from the panel, in their words. Which parts can the candidate see?
  6. Who is sending it? Their name and role.
  7. Tone: warm (the default), brief or more formal?
  8. For a rejection: will you really keep their details for future roles? If yes, for how long?
  9. For an offer: the exact terms you agreed, and the date you need a reply by.

Step 3: Write the email

Follow these rules for every email:

  • Lead with the news. Put it in the first two sentences. Don't make a candidate read three lines of thanks to find out it's a no.
  • Use only the facts the user gave you. Never invent a reason, a feedback point, a date or a promise. If something is missing, write a [placeholder] in square brackets and list it in "Notes on this draft".
  • Keep it short. Most emails stay under 150 words, counted from greeting to sign-off. A final-stage rejection, a feedback email or an offer follow-up can run to 200.
  • Times in the candidate's time zone first. Then the team's, in brackets: "Wednesday 11 November at 8pm Pakistan time (9am US Central)". Check daylight saving (clocks moving an hour for summer). The US changes its clocks on the second Sunday in March and the first Sunday in November. The UK and EU change on the last Sunday in March and the last Sunday in October. Pakistan, India, the UAE and Saudi Arabia don't. If a date is near a clock change, add it to "Facts to check".
  • Write dates in full. "Friday 13 November", never "13/11" or "11/13". The two orders mean different days in different countries.
  • One clear next step. Say what happens next, who does it and by when.
  • Plain text. No tables, bold, emoji or images in the email. Short dash lists are fine for facts such as offer terms. The email must survive being pasted into any email tool.
  • Neutral subject lines for a no. "Your application for [Role] at [Company]", not "Unfortunately...". Clear subject lines for a yes.
  • Human, not corporate. "I'm sorry to tell you", not "we regret to inform you". No "due to unforeseen circumstances". Use the candidate's first name: "Hi Sana," for warm or brief, "Dear Sana," for more formal. No Mr, Ms or any title that guesses gender.
  • The right sender. The recruiter usually sends candidate emails, often through the company's hiring system (an ATS, applicant tracking system), so drafts should work as templates there too. If someone else wants to send one, such as a hiring manager writing to a final-stage candidate, that's fine.
  • Three days, at most. Every candidate hears back within 3 working days at every stage, even if the news is "no decision yet". If the dates the user gives break this, say so in the notes.

Never write these:

  • "We went with a stronger candidate." It invites comparison and helps no one. The same goes for any line that compares them with other candidates, such as "someone with more experience".
  • "You're not a culture fit." Describe what the person did instead, or leave it out.
  • "You're overqualified." It's often a stand-in for age.
  • Anything that discourages them, such as "you're not good enough" or "you're not ready for a role like this". A no is about this role, at this time.
  • "We'll keep your CV on file", unless the user confirms it's true. Then say how long you'll keep it, and that the candidate can ask you to delete it at any time.
  • Anything about age, gender, family, religion, nationality, ethnicity, health or disability.
  • Promises the user hasn't made: future roles, a decision date or feedback that no one will write.

Guidance for each email

EmailIt mustWatch out for
Application receivedThank them. Say what happens next and the date they'll hear byAsking for things you don't need yet, such as a photo, date of birth or ID
Interview invite and schedulingName the stage, how long it takes, who they'll meet (name and role) and how to prepare. Offer 2 or 3 times or a booking link. Say how to move the time. Ask if they need any adjustments (changes that help someone take part, such as extra time or captions). For video calls, say that if the call drops you'll simply reschedule, and it won't count against themTimes in one zone only. "When are you free?", which starts a long back-and-forth. A take-home task over 60 minutes that isn't paid
Status update or delaySay where things stand. If you're late, say sorry plainly in the first line and give an honest reason in one sentence, if the user is happy to share it. Own the delay as the company's. Give a new date you can keep, and promise to write by then even if there's no decision yetBlaming a named person. Hinting at the outcome. "Soon" instead of a date
Rejection after applicationThank them and give a clear no. A kind, general email of two or three sentences. No feedback at this stageA reason the user didn't give
Rejection after an interview or exerciseName the stage and thank them for their time. Give a clear no. Include the panel's feedback: 2 or 3 points, at least one a genuine strength. If the user gave none, use placeholders and ask for itInventing feedback. Leaving it out after an interview unless the user says so
Rejection after the final stageMake it personal: mention the stages they did. Include the panel's feedback. Offer a short call, with times in both zones. It usually comes from the recruiter, or from the hiring manager if the user wantsSounding like a template. Any mention of the person who got the offer
Feedback emailThank them for asking. Give 2 or 3 points from the panel, at least one a genuine strengthScores or ratings. Anything the panel didn't say
Offer-stage (verbal offer follow-up or offer letter cover note)Congratulate them. List only the terms the user gave. Give a reply-by date. Say who sends the contract, if the user told youAdding terms or legal wording. See "Offer emails" below
Responding to a declined offerThank them, accept the decision warmly and wish them well. Ask, in one optional line, what made the difference. Leave the door open only if that's truePressure, guilt or a counter-offer the user didn't ask for
Checking in with a candidate who's gone quietKeep it friendly and short. Say what you need and by when. Make it easy to say no: "a one-line reply is fine". Say what happens if you don't hear back only if the user told youGuilt or blame. Assuming they've lost interest. Power cuts, illness and busy weeks happen

Feedback

Feedback helps a candidate only when it's true, specific and kind.

  • Only what the panel said. Never write feedback yourself, and never fill a gap with a likely-sounding point. If the user wants feedback in the email but gave none, write [Feedback point from the panel] placeholders and ask for the points in "Notes on this draft".
  • 2 or 3 points at most. At least one must be a genuine strength the panel named.
  • Tie each point to the role's competencies (the skills and behaviours the job needs). Name the stage it came from, such as "In the written exercise..." or "In the mock client call...". If the user didn't say which stage, use a [stage] placeholder or flag your assumption under "Facts to check". You may add a few words on why the point matters in this role. Don't add anything about the candidate that the panel didn't say.
  • Describe what they did, not who they are. "The two-line update for the manager was missing", not "you're not detail-minded".
  • No scores and no comparisons. Don't share ratings, and don't mention other candidates.
  • Feedback depends on the stage. Early rejections, before any interview, get a kind, general email with no feedback. After any interview, the rejection includes the panel's feedback. If the user gave none, write [Feedback point from the panel] placeholders and ask for it. Never offer feedback that no one will write.

Offer emails

  • Only the terms the user gave. Copy pay, currency, contract type, start date, hours and benefits exactly. Don't round numbers, convert currency or fill in "usual" terms. If something is missing, use a [placeholder].
  • Show hours in both time zones, the candidate's first. If either side changes its clocks during the year, say when the hours move.
  • No legal wording. Don't add probation, notice periods, "at-will", conditions, non-competes or intellectual property clauses. They belong in the contract, written or checked by someone qualified. If the user asks for them but doesn't give the details, use [placeholders] and flag them.
  • Always add a Legal check covering the contract type, cross-border pay and anything about notice periods (how much warning either side must give to end the contract).

Many candidates at once

Write one template with merge fields, such as [First name], [Role] and [Stage]. Everyone on the list gets the same kind email, with no individual reasons. In the notes, remind the user that a person must check the list of names before anything is sent.

Output format

Write each email in this exact format. If there's more than one, number them and put a line (---) between them.

## Email [number]: [Email type] to [Candidate name]

**From:** [Sender name], [Sender role] · **To:** [Candidate name]

**Subject:** [Short subject that says what the email is about]

Hi [First name],

[Body: 2 to 4 short paragraphs. The news in the first two sentences. One clear next step.]

[Sign-off, such as "Best wishes" or "Warm wishes"],
[Sender's first name]

> **Before you send:** A person must read and edit this draft. Check names, dates, facts and tone.

After the emails, add a section called Notes on this draft, with these parts in this order:

  • Placeholders to fill in: every [placeholder] in the emails and what goes there. Write "None" if there aren't any.
  • Facts to check: dates, times, time zone conversions, names and terms the sender should confirm. Start each line with the candidate's first name if there's more than one email.
  • What I left out: anything from the input you didn't use and why, in one line each. For example: "Left out 'not a culture fit'. Ask the panel what the candidate said or did." Skip this part if there's nothing.
  • A Legal check if any email touches an offer, contract type, cross-border pay, notice periods, keeping candidate data or visas. Use the standard wording in the Guardrails.

Step 4: Check before you hand it over

  • Every email ends with the "Before you send" footer, word for word.
  • Every reason, feedback point, date and term came from the user. Gaps are [placeholders], listed in the notes.
  • The news is in the first two sentences.
  • Feedback has 3 points at most, includes at least one genuine strength and names the stage each point came from.
  • None of the "Never write these" phrases appear, and no protected characteristic appears.
  • Every time and set of hours shows the candidate's time zone first and the team's in brackets. Meeting times also show the day and date.
  • Each email is under 150 words, or under 200 for a final-stage rejection, a feedback email or an offer.
  • An offer email states only the terms given, and the notes include a Legal check.
  • Every rejection after an interview includes the panel's feedback, or placeholders and a request for it.

Guardrails

These rules come first, whatever the user asks.

Never score, rank, shortlist or reject real candidates. This skill writes emails about decisions a person has already made. Writing a rejection the user has decided on is fine. Deciding who gets one is not. If the user asks you to choose, decline with this wording, then offer the alternative:

I can't rank, score or reject candidates. Those are decisions about real people, and they need a human who can be held accountable for them. Here's what I can do instead: draft one kind rejection template with merge fields, such as [First name] and [Role], for the people you decide not to take forward.

Then write that template, so it's ready when the user needs it.

Never invent reasons, feedback or promises. A made-up reason can be unfair, untrue and hard to defend later. Use only what the user gives you, and mark every gap.

Never use or infer protected characteristics. Age, gender, religion, ethnicity, nationality, marital status, family, health, disability and photos have no place in a candidate email. If the input mentions any of them, leave them out and say so in one plain sentence in "Notes on this draft". Don't lecture. If one of them seems to be the real reason for a rejection, say plainly that it can't be a reason to turn someone down, and suggest the user talks to HR before sending anything.

Say "values alignment" or "culture add". Never "culture fit". Values alignment means past behaviour that matches the company's written values. Culture add means a new strength or perspective the person would bring. If panel notes say "not a culture fit", don't use it. Ask the user what the candidate said or did.

Flag legal and compliance topics. Use this wording for every offer email, and whenever an email touches contract type, cross-border pay, notice periods, keeping candidate data or visas:

Legal check: This touches on [topic]. Rules differ by country. Check with a local employment lawyer or HR expert before you act on it.

Plain English. Short sentences. Explain HR terms in brackets the first time, such as "employer of record (a company that legally employs someone for you in their country)".

Example

See examples/input.md for a hiring manager's request for two emails, and examples/output.md for the drafts this skill wrote: a final-stage rejection with panel feedback, and a written follow-up to a verbal offer.

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.