Skill de IABuild onboarding planHR & Recruiting
Create new-hire onboarding plans with pre-start tasks, Day 1 schedule, Week 1 checklist, and 30/60/90 goals. — Claude Skill
Un Skill de Claude para Claude Code por Anthropic✓ — ejecutar /onboarding en Claude·Actualizado el 13 jun 2026·vmain@da04ccb
Generates a practical onboarding plan for a new hire, including account setup, equipment, buddy assignment, Day 1 agenda, Week 1 tasks, key contacts, and role-specific goals.
- Turns a start date into a full pre-start, Day 1, Week 1, and 30/60/90 plan.
- Makes tool access, equipment, documents, meetings, buddy, and manager actions visible.
- Adapts onboarding to the new hire's role and team.
- Creates a checklist managers can actually run instead of a generic welcome note.
TúHoy
Onboarding relies on a few calendar invites, missing access requests, and manager memory.
Con /onboarding
Run /onboarding to create a role-specific onboarding plan with pre-start tasks, Day 1, Week 1, contacts, tools, and goals.
1 Share new hire details2 Generate checklist3 Assign owners4 Review 30/60/90 outcomes
Para quién es
People Operations Manager
Standardize onboarding so every new hire starts with access, context, contacts, and goals.
Ver skills para este rolRecruiter
Transition accepted candidates smoothly into employee onboarding.
Ver skills para este rolHR Manager
Make onboarding quality visible across teams.
Ver skills para este rolQué hace
New hire start prep
Create everything needed before a new employee's first day.
Manager onboarding checklist
Give managers a concrete plan for meetings, documents, and first tasks.
Remote onboarding
Make equipment, access, calendars, and buddy support explicit before Day 1.
Cómo funciona
1
Collect new hire name, role, team, start date, manager, location, and needed tools.
2
Prepare pre-start tasks for HR, IT, manager, and buddy.
3
Build Day 1 schedule and Week 1 checklist.
4
Draft 30/60/90 goals and key contacts table.
Opciones de entrada
New hire details
Name, role, team, location, start date, and manager.
Ejemplo
New hire context
New hire: Jordan Lee Role: Customer Success Manager Team: Enterprise CS Start date: July 8, 2026 Manager: Priya Shah Location: Remote, US East Tools: Gmail, Slack, Salesforce, Gainsight, Zoom, Notion Need: onboarding checklist, Day 1 schedule, Week 1 plan, 30/60/90 goals, key contacts, and access list.
Onboarding plan
Pre-start checklist
- [ ] Send welcome email with start time, Zoom link, and first-week expectations - [ ] Set up Gmail, Slack, Salesforce, Gainsight, Zoom, and Notion access - [ ] Ship laptop, monitor, headset, and security key - [ ] Add Jordan to Enterprise CS calendar and recurring account meetings - [ ] Assign onboarding buddy: Senior CSM on Enterprise team - [ ] Prepare first customer account shadowing list
Day 1 schedule
| Time | Activity | With | |---|---|---| | 9:00 | Welcome and onboarding overview | Manager | | 10:00 | IT setup and security walkthrough | IT / Buddy | | 11:00 | Team introductions | Enterprise CS team | | 12:00 | Welcome lunch | Manager + Buddy | | 1:30 | Company, customer segments, and CS motion | Manager | | 3:00 | Role expectations and 30/60/90 plan | Manager | | 4:00 | Explore tools and docs | Self-guided |
Week 1 checklist
- [ ] Complete required compliance and security training - [ ] Read Enterprise CS playbook, renewal process, escalation guide, and QBR template - [ ] 1:1 with Support Lead, Sales counterpart, Product PM, and RevOps partner - [ ] Shadow two customer calls and one renewal risk review - [ ] Complete first small task: draft account summary for one assigned customer - [ ] End-of-week check-in with manager
30/60/90 goals
| Timeframe | Goals | |---|---| | 30 days | Understand CS process, own internal account summaries, shadow renewal and escalation workflows | | 60 days | Co-own 5 customer accounts, run one QBR prep, identify customer health risks with manager review | | 90 days | Own first portfolio segment, run customer check-ins independently, present one process improvement idea |
Key contacts and access
| Person / Tool | Role | For What | |---|---|---| | Priya Shah | Manager | Priorities, feedback, account ownership | | Senior CSM buddy | Buddy | Culture, process questions, day-to-day navigation | | IT contact | IT | Equipment and tool access | | Salesforce | CRM | Account and opportunity context | | Gainsight | CS platform | Health scores and customer success plans |
Métricas que mejora
Onboarding Completion
Tracks whether setup, access, meetings, and learning tasks are completed on time.
HR & RecruitingTime to Productivity
Connects onboarding tasks to first 30/60/90 outcomes.
HR & RecruitingFeedback Quality
Creates manager check-ins that produce actionable feedback early.
HR & RecruitingFunciona con
Google Calendar
manualCreate Day 1 and Week 1 meetings.
Slack
manualCoordinate buddy, team introductions, and onboarding reminders.
BambooHR
manualUse HRIS onboarding and employee profile details.
Workday
manualUse HRIS new-hire records, manager, location, and employee data.
Notion
manualLink onboarding docs, team wiki, and role playbooks.
¿Quieres usar Onboarding?
Elige cómo empezar.
Ejecutar en Claude Code
Gratis. Código abierto.
Instala y ejecuta este skill localmente en tu computadora.
1
Instalar Claude Code
Abre una terminal en tu computadora y pega este comando:
2
Instalar el skill
Esto descarga el skill con todos sus archivos en tu computadora:
Añade -g al final para tenerlo disponible en todos tus proyectos.
3
Ver código en GitHub Ejecútalo
Inicia Claude Code, luego escribe el comando:
luego
/onboarding
If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.
Generate a comprehensive onboarding plan for a new team member.
Usage
/onboarding $ARGUMENTS
What I Need From You
- New hire name: Who's starting?
- Role: What position?
- Team: Which team are they joining?
- Start date: When do they start?
- Manager: Who's their manager?
Output
## Onboarding Plan: [Name] — [Role]
**Start Date:** [Date] | **Team:** [Team] | **Manager:** [Manager]
### Pre-Start (Before Day 1)
- [ ] Send welcome email with start date, time, and logistics
- [ ] Set up accounts: email, Slack, [tools for role]
- [ ] Order equipment (laptop, monitor, peripherals)
- [ ] Add to team calendar and recurring meetings
- [ ] Assign onboarding buddy: [Suggested person]
- [ ] Prepare desk / remote setup instructions
### Day 1
| Time | Activity | With |
|------|----------|------|
| 9:00 | Welcome and orientation | Manager |
| 10:00 | IT setup and tool walkthrough | IT / Buddy |
| 11:00 | Team introductions | Team |
| 12:00 | Welcome lunch | Manager + Team |
| 1:30 | Company overview and values | Manager |
| 3:00 | Role expectations and 30/60/90 plan | Manager |
| 4:00 | Free time to explore tools and docs | Self |
### Week 1
- [ ] Complete required compliance training
- [ ] Read key documentation: [list for role]
- [ ] 1:1 with each team member
- [ ] Shadow key meetings
- [ ] First small task or project assigned
- [ ] End-of-week check-in with manager
### 30-Day Goals
1. [Goal aligned to role]
2. [Goal aligned to role]
3. [Goal aligned to role]
### 60-Day Goals
1. [Goal]
2. [Goal]
### 90-Day Goals
1. [Goal]
2. [Goal]
### Key Contacts
| Person | Role | For What |
|--------|------|----------|
| [Manager] | Manager | Day-to-day guidance |
| [Buddy] | Onboarding Buddy | Questions, culture, navigation |
| [IT Contact] | IT | Tool access, equipment |
| [HR Contact] | HR | Benefits, policies |
### Tools Access Needed
| Tool | Access Level | Requested |
|------|-------------|-----------|
| [Tool] | [Level] | [ ] |
If Connectors Available
If ~~HRIS is connected:
- Pull new hire details and team org chart
- Auto-populate tools access list based on role
If ~~knowledge base is connected:
- Link to relevant onboarding docs, team wikis, and runbooks
- Pull the team's existing onboarding checklist to customize
If ~~calendar is connected:
- Create Day 1 calendar events and Week 1 meeting invites automatically
Tips
- Customize for the role — An engineer's onboarding looks different from a designer's.
- Don't overload Day 1 — Focus on setup and relationships. Deep work starts Week 2.
- Assign a buddy — Having a go-to person who isn't their manager makes a huge difference.
Documentos de referencia
name: onboarding description: Generate an onboarding checklist and first-week plan for a new hire. Use when someone has a start date coming up, building the pre-start task list (accounts, equipment, buddy), scheduling Day 1 and Week 1, or setting 30/60/90-day goals for a new team member. argument-hint: "<new hire name and role>"
/onboarding
If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.
Generate a comprehensive onboarding plan for a new team member.
Usage
/onboarding $ARGUMENTS
What I Need From You
- New hire name: Who's starting?
- Role: What position?
- Team: Which team are they joining?
- Start date: When do they start?
- Manager: Who's their manager?
Output
## Onboarding Plan: [Name] — [Role]
**Start Date:** [Date] | **Team:** [Team] | **Manager:** [Manager]
### Pre-Start (Before Day 1)
- [ ] Send welcome email with start date, time, and logistics
- [ ] Set up accounts: email, Slack, [tools for role]
- [ ] Order equipment (laptop, monitor, peripherals)
- [ ] Add to team calendar and recurring meetings
- [ ] Assign onboarding buddy: [Suggested person]
- [ ] Prepare desk / remote setup instructions
### Day 1
| Time | Activity | With |
|------|----------|------|
| 9:00 | Welcome and orientation | Manager |
| 10:00 | IT setup and tool walkthrough | IT / Buddy |
| 11:00 | Team introductions | Team |
| 12:00 | Welcome lunch | Manager + Team |
| 1:30 | Company overview and values | Manager |
| 3:00 | Role expectations and 30/60/90 plan | Manager |
| 4:00 | Free time to explore tools and docs | Self |
### Week 1
- [ ] Complete required compliance training
- [ ] Read key documentation: [list for role]
- [ ] 1:1 with each team member
- [ ] Shadow key meetings
- [ ] First small task or project assigned
- [ ] End-of-week check-in with manager
### 30-Day Goals
1. [Goal aligned to role]
2. [Goal aligned to role]
3. [Goal aligned to role]
### 60-Day Goals
1. [Goal]
2. [Goal]
### 90-Day Goals
1. [Goal]
2. [Goal]
### Key Contacts
| Person | Role | For What |
|--------|------|----------|
| [Manager] | Manager | Day-to-day guidance |
| [Buddy] | Onboarding Buddy | Questions, culture, navigation |
| [IT Contact] | IT | Tool access, equipment |
| [HR Contact] | HR | Benefits, policies |
### Tools Access Needed
| Tool | Access Level | Requested |
|------|-------------|-----------|
| [Tool] | [Level] | [ ] |
If Connectors Available
If ~~HRIS is connected:
- Pull new hire details and team org chart
- Auto-populate tools access list based on role
If ~~knowledge base is connected:
- Link to relevant onboarding docs, team wikis, and runbooks
- Pull the team's existing onboarding checklist to customize
If ~~calendar is connected:
- Create Day 1 calendar events and Week 1 meeting invites automatically
Tips
- Customize for the role — An engineer's onboarding looks different from a designer's.
- Don't overload Day 1 — Focus on setup and relationships. Deep work starts Week 2.
- Assign a buddy — Having a go-to person who isn't their manager makes a huge difference.