Make it easy with AI

HR & Recruiting Skills Kit / Setup guide

HR & Recruiting Skills Kit — Installation Guide

This pack includes 10 ready-to-use Claude Skills for hiring and people management:

  1. job-description-writer — clear, bias-conscious job descriptions
  2. offer-letter-drafter — turn offer details into a professional offer letter
  3. candidate-screening-summary — turn resume/notes into a structured screening summary
  4. candidate-rejection-email-writer — respectful rejection emails, matched to interview stage
  5. interview-question-generator — role-specific interview questions with notes on strong answers
  6. onboarding-checklist-builder — phased new-hire onboarding plans
  7. performance-review-drafter — turn manager notes into a structured review
  8. exit-interview-question-planner — structured, non-leading exit interview questions
  9. employee-policy-explainer — turn a policy into a plain-language employee explanation
  10. team-announcement-writer — internal announcements for new hires, promotions, and org changes

What is a Claude Skill?

A Claude Skill is an instructions file (SKILL.md) that teaches Claude how to perform a specific task following your format and rules. When you ask Claude something that matches a skill's description, it automatically applies those instructions.

Installing — Claude Code (on your computer / terminal)

A) User-level (works in every project)

  1. Create the skills folder if it doesn't exist yet:
    mkdir -p ~/.claude/skills
    
  2. Copy each skill's folder into ~/.claude/skills/, so the final path looks like:
    ~/.claude/skills/job-description-writer/SKILL.md
    ~/.claude/skills/offer-letter-drafter/SKILL.md
    ~/.claude/skills/candidate-screening-summary/SKILL.md
    ~/.claude/skills/candidate-rejection-email-writer/SKILL.md
    ~/.claude/skills/interview-question-generator/SKILL.md
    ~/.claude/skills/onboarding-checklist-builder/SKILL.md
    ~/.claude/skills/performance-review-drafter/SKILL.md
    ~/.claude/skills/exit-interview-question-planner/SKILL.md
    ~/.claude/skills/employee-policy-explainer/SKILL.md
    ~/.claude/skills/team-announcement-writer/SKILL.md
    
  3. Start (or restart) Claude Code — the skills will be available automatically in any project.

B) Single-project level

Copy the same folders into <your-project>/.claude/skills/ instead, if you only want them in one project.

Using with claude.ai / Claude Desktop

  1. Open Settings.
  2. Find the Capabilities or Skills section.
  3. Upload each skill's SKILL.md file (or its whole folder).
  4. The skill triggers automatically when you ask something matching its description.

Using with ChatGPT

ChatGPT doesn't have a "Skills" system, but each SKILL.md file works just as well as ChatGPT instructions — the part below the --- frontmatter is plain instruction text.

As a Custom GPT (ChatGPT Plus/Team — stays saved for reuse):

  1. Go to Explore GPTs → Create → Configure.
  2. Give it a name (e.g., "Job Description Writer") and a short description.
  3. Open the skill's SKILL.md file, copy everything below the --- frontmatter block, and paste it into the Instructions field.
  4. Save. Reopen this GPT any time you need that skill.

Without Custom GPT access (works on any ChatGPT plan): Paste the same instructions (below the frontmatter) at the start of a new chat, then ask your question. You'll need to re-paste it each time you start a new chat.

How to check it's working

After installing, ask Claude something that clearly matches one skill, for example:

"Write a job description for a Marketing Manager, 5+ years experience, runs paid social and email, remote-friendly."

If the skill triggered correctly, the answer will follow the job-description-writer structure (overview, responsibilities, required vs. nice-to-have qualifications).

Common issues

  • The skill doesn't trigger — check that the SKILL.md file is inside a folder, not dropped directly into .claude/skills/.
  • Changes aren't showing up — restart your Claude Code session after editing a file.
  • Output feels generic — these skills work best with real specifics (actual notes, actual requirements); the more concrete your input, the more specific the output.