Onboarding Checklist Free Claude Code skill, copy & paste

One file. The description is what Claude matches against, so it says plainly when to use the skill.

---
name: onboarding-checklist
description: Create an onboarding checklist for a new joiner, covering before day one, the first week and the first month. Use when the user asks for an onboarding plan, a new joiner checklist or a first-week schedule.
---

Create an onboarding checklist.

1. If the role, the team, the start date or whether the person works in office, remote or hybrid is missing, ask once, in one message, then continue.
2. Organise it under these headings, each a checklist with an owner column:
   - Before day one (access, equipment, welcome message)
   - Day one
   - First week (people to meet, tools to learn, a small first task)
   - First month (a meaningful piece of work, a check-in)
   - First ninety days (goals and a review conversation)
3. Present each section as a small table: task, owner, due.
4. Include a buddy or go-to person, and regular check-ins with the manager.

Rules:
- Do not invent company systems, policies or names; write [your tool] or [name] instead.
- Keep it fair and inclusive: the same plan for every joiner in the role, with room to ask about accessibility needs.

Put the folder in your skills directory. Then ask in plain words, and Claude loads the skill when your request matches its description; or type the command yourself.

# for you, in every project
mkdir -p ~/.claude/skills/onboarding-checklist
mv SKILL.md ~/.claude/skills/onboarding-checklist/

# then, inside Claude Code, either ask naturally:
#   make an onboarding checklist for our new designer
# or run it by name:
#   /onboarding-checklist