candidate-rejection-email

$npx mdskill add Significant-Gravitas/skills-catalog/candidate-rejection-email

Draft only after the named decision-maker confirms the decision and the stage. Harper does not decide who is rejected.

SKILL.md

.github/skills/candidate-rejection-emailView on GitHub ↗
---
name: "candidate-rejection-email"
description: "Draft a clear, kind rejection email from an approved human decision without inventing feedback or sending it."
triggers: ["rejection email", "reject candidate", "candidate decline", "not moving forward", "application rejection"]
version: "1"
---

# Candidate rejection email

Draft only after the named decision-maker confirms the decision and the stage. Harper does not decide who is rejected.

## Inputs

Get the candidate's chosen name, role title, stage, approved sender, whether the company permits feedback, and any feedback the decision-maker has approved verbatim. Do not derive a reason from scorecards or fill a blank with a generic claim.

## Draft

Lead with the decision in the first two sentences. Thank the candidate for the specific time or work they gave. If approved feedback exists, state it in job-related terms and no more broadly than the evidence supports. Do not say another candidate was better unless the owner approved that statement. Do not promise future contact.

For late-stage candidates, include the approved contact and next step for expenses or work-sample handling if applicable. Keep the subject plain.

## Gate

Return an unsent draft plus an approval line naming the decision-maker and sender. Never send it. Never expose panel notes, protected information, legal conclusions, or feedback that was not approved.

More from Significant-Gravitas/skills-catalog

SkillDescription
account-health-and-qbrsUse when a support account wobbles or a quarterly business review looms: read the health signals, run the success plan, and prep the review from evidence.
accounts-receivable-follow-upReview open receivables and draft factual, staged payment follow-ups without inventing status or contacting a customer.
ad-copy-variantsWrite ad variants that each test one idea, within platform limits and supported claims.
alex-getting-startedUse on the first conversation with Alex, or whenever their memory has no product preferences yet: learn what the user is building and who for, where specs, roadmap and numbers live, who decides dates and scope, and get them to a first real product deliverable.
alliance-co-commercializationUse when a strategic alliance needs joint selling governance: operating model, joint targeting, steering prep, and milestone accountability.
anika-getting-startedUse on the first conversation with Anika, or whenever their memory has no partnership preferences yet: learn which partners and alliances the user owns, what motion they run, and get one real partner read on screen in the same session.
assure-partner-led-deliveryUse when partners deliver client work in your name: own the in-flight book, run the weekly delivery review, and rescue engagements before clients feel it.
automate-finance-reportingUse to connect a number source, map an export into the finance ledger, or QA a sheet: the column mapping, the dedupe key, the load summary, and the checks that must pass before a read ships.
billing-refunds-and-exceptionsUse when money is on the table: verify the charge, check the policy, and stage a refund or exception draft that stops at the owner's yes.
board-and-investor-metrics-briefPrepare a concise board or investor metrics brief with definitions, sources, comparisons, drivers, risks, and decisions needed.