Skills › Knowledge Work Plugins › onboarding
onboarding
The facts
Its 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.
The description the agent reads to decide when to use it.
From its settingsline 3
When it starts
A person mentions a new hire with an upcoming start date and wants the pre-start task list, Day 1 and Week 1 schedule, or 30/60/90-day goals put together. It is a human-resources onboarding planner, not a tool-connection or first-run setup skill.
Things a person might say (the model's guesses)
- “Our new account manager starts Monday — can you build the onboarding plan?”
- “I need a first-week schedule and 30/60/90 goals for the engineer joining my team next month”
- “What should we have ready before our new designer's first day — accounts, equipment, a buddy?”
A model's summary of when it is used.
A model's reading
What it takes when started
<new hire name and role>
What to type after its name when you start it.
From its settingsline 4
What leads to it
- recruiting-pipeline hands off to this once an offer is accepted recruiting-pipeline, line 19
Other skills that hand off to this one, call it, require it or offer it instead, as a model read them.
A model's reading
Licence
Apache-2.0, from LICENSE
The terms its author shares it under, which let it be shown here.
From the repositorylicence text
The text
Most marks come from matching words in the file, so treat them as pointers.
1---
2name: onboarding
3description: 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.
4argument-hint: "<new hire name and role>"
5---
7# /onboarding
9> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../../CONNECTORS.md).
11Generate a comprehensive onboarding plan for a new team member.
/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.
Raw lines 1 to 12Boilerplate, lines 13 to 18. The same text appears in 24 other files here. Close
19## What I Need From You
21- **New hire name**: Who's starting?
22- **Role**: What position?
23- **Team**: Which team are they joining?
24- **Start date**: When do they start?
25- **Manager**: Who's their manager?
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?
27## Output
29```markdown
30## Onboarding Plan: [Name] — [Role]
31**Start Date:** [Date] | **Team:** [Team] | **Manager:** [Manager]
33### Pre-Start (Before Day 1)
34- [ ] Send welcome email with start date, time, and logistics
35- [ ] Set up accounts: email, Slack, [tools for role]
36- [ ] Order equipment (laptop, monitor, peripherals)
37- [ ] Add to team calendar and recurring meetings
38- [ ] Assign onboarding buddy: [Suggested person]
39- [ ] Prepare desk / remote setup instructions
41### Day 1
42| Time | Activity | With |
43|------|----------|------|
44| 9:00 | Welcome and orientation | Manager |
45| 10:00 | IT setup and tool walkthrough | IT / Buddy |
46| 11:00 | Team introductions | Team |
47| 12:00 | Welcome lunch | Manager + Team |
48| 1:30 | Company overview and values | Manager |
49| 3:00 | Role expectations and 30/60/90 plan | Manager |
50| 4:00 | Free time to explore tools and docs | Self |
52### Week 1
53- [ ] Complete required compliance training
54- [ ] Read key documentation: [list for role]
55- [ ] 1:1 with each team member
56- [ ] Shadow key meetings
57- [ ] First small task or project assigned
58- [ ] End-of-week check-in with manager
60### 30-Day Goals
611. [Goal aligned to role]
622. [Goal aligned to role]
633. [Goal aligned to role]
65### 60-Day Goals
661. [Goal]
672. [Goal]
69### 90-Day Goals
701. [Goal]
712. [Goal]
73### Key Contacts
74| Person | Role | For What |
75|--------|------|----------|
76| [Manager] | Manager | Day-to-day guidance |
77| [Buddy] | Onboarding Buddy | Questions, culture, navigation |
78| [IT Contact] | IT | Tool access, equipment |
79| [HR Contact] | HR | Benefits, policies |
81### Tools Access Needed
82| Tool | Access Level | Requested |
83|------|-------------|-----------|
84| [Tool] | [Level] | [ ] |
85```
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] | [ ] |87## If Connectors Available
89If **~~HRIS** is connected:
90- Pull new hire details and team org chart
91- Auto-populate tools access list based on role
93If **~~knowledge base** is connected:
94- Link to relevant onboarding docs, team wikis, and runbooks
95- Pull the team's existing onboarding checklist to customize
97If **~~calendar** is connected:
98- Create Day 1 calendar events and Week 1 meeting invites automatically
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
Uses an outside tool ~~knowledge :93
Uses an outside tool ~~calendar :97
100## Tips
1021. **Customize for the role** — An engineer's onboarding looks different from a designer's.
1032. **Don't overload Day 1** — Focus on setup and relationships. Deep work starts Week 2.
1043. **Assign a buddy** — Having a go-to person who isn't their manager makes a huge difference.
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.
From anthropics/knowledge-work-plugins at 2574e29, 2026-10-27. Skills read by DeepSeek V4.1 Flash on 2026-11-04. Summary and techniques by Claude Opus 5.5 on 2026-11-06.