Rejection Writer

Write warm, specific candidate rejection emails that protect the employer brand. Use this skill whenever the user wants to "reject a candidate", "write a rejection email", "let a candidate down", "decline an applicant", or needs to close the loop with someone who didn't get the role. Tailors tone to how far the candidate got (applied / screened / interviewed / final round) and avoids the generic, brand-damaging rejection. Drafts only — the user reviews and sends.

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add getclera/claude-skills --skill rejection-writer
Manual install
git clone --depth 1 https://github.com/getclera/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/recruitment/skills/rejection-writer ~/.claude/skills/rejection-writer

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Rejection Email Writer

## What This Skill Does

Writes **candidate rejections that don't damage your reputation.** Most rejections are cold,
generic, and remembered for the wrong reasons — and rejected candidates talk, refer, reapply, and
sometimes become customers. A good rejection is warm, appropriately specific, and leaves the person
feeling respected. This is an employer-brand play disguised as an admin task.

---

## Process

1. **Get the stage:** how far did the candidate get? Applied / screened / interviewed / final round.
   Tone and specificity scale with stage — a final-round candidate deserves real feedback; an
   applicant gets a warm, brief no.
2. **Get the reason** (for the user's reference and to calibrate specificity). Some reasons can be
   shared kindly; some shouldn't be detailed (legal/judgment calls).
3. **Draft to match the stage.** Warmer and more specific the further they got.
4. **Decide on feedback.** Offer concrete, kind feedback for late-stage candidates *if* the user
   wants to give it. Never give feedback that creates legal exposure or reads as a discrimination
   rationale.

> **Boundary:** Drafts only — the user sends. Don't promise feedback the user hasn't agreed to give.

---

## How to Write a Good Rejection

- **Scale warmth and specificity to stage.** A final-round candidate who spent hours deserves more
  than a form letter. An early applicant gets brief and kind.
Read the full skill on GitHub

Details

Skill name
rejection-writer
Path
recruitment/skills/rejection-writer/SKILL.md
License
MIT
Repo updated
7 November 2026

FAQ

What does the Rejection Writer skill do?

Write warm, specific candidate rejection emails that protect the employer brand. Use this skill whenever the user wants to "reject a candidate", "write a rejection email", "let a candidate down", "decline an applicant", or needs to close the loop with someone who didn't get the role. Tailors tone to how far the candidate got (applied / screened / interviewed / final round) and avoids the generic, brand-damaging rejection. Drafts only — the user reviews and sends.

How do I install the Rejection Writer skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add getclera/claude-skills --skill rejection-writer. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Rejection Writer popular?

It lives in getclera/claude-skills, which has 5 GitHub stars and 0 forks.

Related skills

Agentic Todo

5

getclera/claude-skills

Set up a personal, persistent todo list inside Claude that fills itself. Claude scans your email, Slack (DMs, mentions, saved messages), meeting notes and calendar on a schedule and drops suggested todos into an inbox you accept or dismiss. Every task has a "Do it" button that hands Claude a ready-made prompt with the context and a plan. Use when the user asks how to track todos, wants a todo list in Claude, wants todos pulled from email/Slack/meetings, or wants an AI task inbox or an agentic todo list.

Productivity & Notes

Application Post Mortem

5

getclera/claude-skills

Analyze why a job application or interview didn't work out, and turn it into calibration for the next one. Use this skill whenever someone says "I got rejected", "I didn't get the job", "why am I getting ghosted", "what went wrong with my application", "help me figure out why I keep getting rejected", or wants to learn from a failed process. Reviews the role, the candidate's materials, and what happened — including interview transcripts if they have them (via a note-taker MCP or pasted) — and gives an honest read on the likely cause plus what to change. Gather everything about the process firs

Images, Video & Audio

Call Scorer

5

getclera/claude-skills

Score candidate interview and screening calls against a hiring rubric, using meeting transcripts and notes. Use this skill whenever the user wants to "score the interview", "give feedback on a candidate call", "how did that candidate do", "rate the candidates from this week's interviews", "pull my interview notes and score them", or wants structured feedback on a recorded conversation with a candidate. Connects to Granola via MCP to read transcripts and notes, then scores against the rubric-builder framework. Always score against an explicit rubric — build one first if none exists.

Productivity & Notes

Story Bank Builder

5

getclera/claude-skills

Build a bank of strong behavioral interview stories by interviewing the candidate conversationally. Use this skill whenever someone says "help me prep behavioral stories", "I freeze on tell-me-about- a-time questions", "build my STAR stories", "I never know what examples to give in interviews", or wants a ready set of stories for behavioral rounds. Draws stories out of the candidate through RELAXED, casual conversation — not an interrogation — then shapes them into strong, reusable STAR stories mapped to the competencies a target role will test. Gather the candidate's background and target rol

Writing & Content

Outreach Personalizer

5

getclera/claude-skills

Write personalized candidate outreach messages that get replies — not templates. Use this skill whenever the user wants to "reach out to a candidate", "write a sourcing message", "draft outreach", "message this person on LinkedIn/email", or is running a sourcing campaign. Connects to Apollo via MCP to enrich candidate context (role, company, background) so the message references something real about the person. Produces outreach that sounds human and specific, never mass-blast.

Writing & Content

Bootstrapping From Templates

5

tomada1114/tomada-claude-plugins

Cut a new GitHub repository from one of the user's template repositories and bring it to a clean first commit: create it from the template (public by default) with scripts/create_from_template.py, clone it under ghq, follow the template's own starting-an-app procedure for the rename or bootstrap (a script, a just recipe, or a placeholder inventory), write AGENTS.md's Product section from signed-off requirements, copy kickoff drafts into docs/, run the template's checks, sync its labels, and push. Use when creating a repository from a template, running a template's bootstrap or rename, a placeh

Writing & Content

Browse the most popular Claude skills, all writing & content skills, or write your own with the skills generator.