onboarding

Name: onboarding
Author: anthropics

2.0kinstalls2.7kforks

How to install onboarding?

anthropics/knowledge-work-plugins/onboarding

$npx -y skills add anthropics/knowledge-work-plugins --skill onboarding

Installs into the current project.

Summary

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.

Files · 1

View on GitHub

SKILL.md

1	# /onboarding
2
3	> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../../CONNECTORS.md).
4
5	Generate a comprehensive onboarding plan for a new team member.
6
7	## Usage
8
9	```
10	/onboarding $ARGUMENTS
11	```
12
13	## What I Need From You
14
15	- New hire name: Who's starting?
16	- Role: What position?
17	- Team: Which team are they joining?
18	- Start date: When do they start?
19	- Manager: Who's their manager?
20
21	## Output
22
23	```markdown
24	## Onboarding Plan: [Name] — [Role]
25	Start Date: [Date] \| Team: [Team] \| Manager: [Manager]
26
27	### Pre-Start (Before Day 1)
28	- [ ] Send welcome email with start date, time, and logistics
29	- [ ] Set up accounts: email, Slack, [tools for role]
30	- [ ] Order equipment (laptop, monitor, peripherals)
31	- [ ] Add to team calendar and recurring meetings
32	- [ ] Assign onboarding buddy: [Suggested person]
33	- [ ] Prepare desk / remote setup instructions
34
35	### Day 1
36	\| Time \| Activity \| With \|
37	\|------\|----------\|------\|
38	\| 9:00 \| Welcome and orientation \| Manager \|
39	\| 10:00 \| IT setup and tool walkthrough \| IT / Buddy \|
40	\| 11:00 \| Team introductions \| Team \|
41	\| 12:00 \| Welcome lunch \| Manager + Team \|
42	\| 1:30 \| Company overview and values \| Manager \|
43	\| 3:00 \| Role expectations and 30/60/90 plan \| Manager \|
44	\| 4:00 \| Free time to explore tools and docs \| Self \|
45
46	### Week 1
47	- [ ] Complete required compliance training
48	- [ ] Read key documentation: [list for role]
49	- [ ] 1:1 with each team member
50	- [ ] Shadow key meetings
51	- [ ] First small task or project assigned
52	- [ ] End-of-week check-in with manager
53
54	### 30-Day Goals
55	1. [Goal aligned to role]
56	2. [Goal aligned to role]
57	3. [Goal aligned to role]
58
59	### 60-Day Goals
60	1. [Goal]
61	2. [Goal]
62
63	### 90-Day Goals
64	1. [Goal]
65	2. [Goal]
66
67	### Key Contacts
68	\| Person \| Role \| For What \|
69	\|--------\|------\|----------\|
70	\| [Manager] \| Manager \| Day-to-day guidance \|
71	\| [Buddy] \| Onboarding Buddy \| Questions, culture, navigation \|
72	\| [IT Contact] \| IT \| Tool access, equipment \|
73	\| [HR Contact] \| HR \| Benefits, policies \|
74
75	### Tools Access Needed
76	\| Tool \| Access Level \| Requested \|
77	\|------\|-------------\|-----------\|
78	\| [Tool] \| [Level] \| [ ] \|
79	```
80
81	## If Connectors Available
82
83	If ~~HRIS is connected:
84	- Pull new hire details and team org chart
85	- Auto-populate tools access list based on role
86
87	If ~~knowledge base is connected:
88	- Link to relevant onboarding docs, team wikis, and runbooks
89	- Pull the team's existing onboarding checklist to customize
90
91	If ~~calendar is connected:
92	- Create Day 1 calendar events and Week 1 meeting invites automatically
93
94	## Tips
95
96	1. Customize for the role — An engineer's onboarding looks different from a designer's.
97	2. Don't overload Day 1 — Focus on setup and relationships. Deep work starts Week 2.
98	3. Assign a buddy — Having a go-to person who isn't their manager makes a huge difference.

People who liked this also viewed

6 picks

Type

onboarding

2.0kinstalls2.7kforks

View on GitHub

How to install onboarding?

anthropics/knowledge-work-plugins/onboarding

$npx -y skills add anthropics/knowledge-work-plugins --skill onboarding

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# /onboarding
2
3	> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../../CONNECTORS.md).
4
5	Generate a comprehensive onboarding plan for a new team member.
6
7	## Usage
8
9	```
10	/onboarding $ARGUMENTS
11	```
12
13	## What I Need From You
14
15	- New hire name: Who's starting?
16	- Role: What position?
17	- Team: Which team are they joining?
18	- Start date: When do they start?
19	- Manager: Who's their manager?
20
21	## Output
22
23	```markdown
24	## Onboarding Plan: [Name] — [Role]
25	Start Date: [Date] \| Team: [Team] \| Manager: [Manager]
26
27	### Pre-Start (Before Day 1)
28	- [ ] Send welcome email with start date, time, and logistics
29	- [ ] Set up accounts: email, Slack, [tools for role]
30	- [ ] Order equipment (laptop, monitor, peripherals)
31	- [ ] Add to team calendar and recurring meetings
32	- [ ] Assign onboarding buddy: [Suggested person]
33	- [ ] Prepare desk / remote setup instructions
34
35	### Day 1
36	\| Time \| Activity \| With \|
37	\|------\|----------\|------\|
38	\| 9:00 \| Welcome and orientation \| Manager \|
39	\| 10:00 \| IT setup and tool walkthrough \| IT / Buddy \|
40	\| 11:00 \| Team introductions \| Team \|
41	\| 12:00 \| Welcome lunch \| Manager + Team \|
42	\| 1:30 \| Company overview and values \| Manager \|
43	\| 3:00 \| Role expectations and 30/60/90 plan \| Manager \|
44	\| 4:00 \| Free time to explore tools and docs \| Self \|
45
46	### Week 1
47	- [ ] Complete required compliance training
48	- [ ] Read key documentation: [list for role]
49	- [ ] 1:1 with each team member
50	- [ ] Shadow key meetings
51	- [ ] First small task or project assigned
52	- [ ] End-of-week check-in with manager
53
54	### 30-Day Goals
55	1. [Goal aligned to role]
56	2. [Goal aligned to role]
57	3. [Goal aligned to role]
58
59	### 60-Day Goals
60	1. [Goal]
61	2. [Goal]
62
63	### 90-Day Goals
64	1. [Goal]
65	2. [Goal]
66
67	### Key Contacts
68	\| Person \| Role \| For What \|
69	\|--------\|------\|----------\|
70	\| [Manager] \| Manager \| Day-to-day guidance \|
71	\| [Buddy] \| Onboarding Buddy \| Questions, culture, navigation \|
72	\| [IT Contact] \| IT \| Tool access, equipment \|
73	\| [HR Contact] \| HR \| Benefits, policies \|
74
75	### Tools Access Needed
76	\| Tool \| Access Level \| Requested \|
77	\|------\|-------------\|-----------\|
78	\| [Tool] \| [Level] \| [ ] \|
79	```
80
81	## If Connectors Available
82
83	If ~~HRIS is connected:
84	- Pull new hire details and team org chart
85	- Auto-populate tools access list based on role
86
87	If ~~knowledge base is connected:
88	- Link to relevant onboarding docs, team wikis, and runbooks
89	- Pull the team's existing onboarding checklist to customize
90
91	If ~~calendar is connected:
92	- Create Day 1 calendar events and Week 1 meeting invites automatically
93
94	## Tips
95
96	1. Customize for the role — An engineer's onboarding looks different from a designer's.
97	2. Don't overload Day 1 — Focus on setup and relationships. Deep work starts Week 2.
98	3. Assign a buddy — Having a go-to person who isn't their manager makes a huge difference.

People who liked this also viewed

6 picks

Type