Onboarding

What This Skill Does

This skill generates a structured onboarding plan for new team members. It covers pre-start tasks, day-one activities, week-one goals, and 30/60/90 day objectives. It's designed to help managers and HR professionals create a consistent and effective onboarding experience.

When to Use

• Onboard a new software engineer.
• Create a plan for a marketing intern.
• Standardize the onboarding process.
• Welcome a new sales representative.
• Prepare for a remote employee's first day.

Key Features

• Generates a detailed onboarding schedule.
• Suggests relevant tasks and activities.
• Defines clear 30/60/90 day goals.
• Identifies key contacts for the new hire.
• Customizable based on role, team, and start date.

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

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

[Goal aligned to role] [Goal aligned to role] [Goal aligned to role]

60-Day Goals

[Goal] [Goal]

90-Day Goals

[Goal] [Goal]

Key Contacts

Tools Access Needed

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./onboarding

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

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

[Goal aligned to role] [Goal aligned to role] [Goal aligned to role]

60-Day Goals

[Goal] [Goal]

90-Day Goals

[Goal] [Goal]

Key Contacts

Tools Access Needed

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.