Onboarding
AnthropicOfficialPublished by Anthropic
- Skill
- Content generator
- Business and productivity
- Apache-2.0
- No issues found
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
The onboarding skill creates a comprehensive, structured plan for integrating new team members. It produces a detailed roadmap covering pre-start logistics, a Day 1 schedule, Week 1 objectives, and long-term 30/60/90-day goals. By providing a standardized template, it ensures that managers cover essential administrative tasks, cultural integration, and role-specific expectations, helping new hires transition smoothly into their positions.
What it does
- Creates a pre-start checklist for equipment, account access, and buddy assignment.
- Generates a detailed Day 1 schedule for orientation and team introductions.
- Outlines a Week 1 plan including training, documentation review, and initial meetings.
- Structures 30, 60, and 90-day performance and development goals.
- Provides a template for tracking tool access and key internal contacts.
- Integrates with connected systems to pull organizational data and schedule meetings.
When to use it
- When preparing for a new hire's start date.
- When you need to organize logistics like equipment and account provisioning.
- When defining clear expectations and goals for a new team member's first three months.
- When you want to ensure a consistent and welcoming experience for new employees.
Advantages
- Reduces administrative burden by providing a ready-to-use onboarding framework.
- Ensures no critical steps are missed during the transition period.
- Helps align new hires with team expectations and company culture early on.
- Facilitates better communication between managers, buddies, and new hires.
Usage examples
- “/onboarding Alex Smith, Senior Developer, Engineering Team, 2023-11-01, Sarah Jones”
- Generates a complete onboarding plan for Alex Smith, including a pre-start checklist, a Day 1 schedule, and a 90-day goal framework tailored for a Senior Developer role.
Install
Download the skill as a ZIP:
https://autogineer.com/agent-skills/anthropics/onboarding/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip onboarding.zip -d .agents/skills
Documentation by Anthropic
/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 $ARGUMENTSWhat 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.
Files
- ATTRIBUTION.mdAdded by AutoGineer902 B
- LICENSELicence file added by AutoGineer11.3 KiB
- SKILL.md3.1 KiB
SKILL.md
/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 $ARGUMENTSWhat 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.
Requirements and compatibility
Written for: Claude Code, Claude apps
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
Needs: Claude Code frontmatter
Security
No issues found by our static scan· No issues found
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- Published by
- Anthropic
- Publisher
- Anthropic (Official)
- Source
- anthropics/knowledge-work-plugins · human-resources/skills/onboarding · commit e050c2e
- Licence
- Apache License 2.0 (redistribution allowed)
- LICENSE (added by AutoGineer from LICENSE)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
AutoGineer is not affiliated with or endorsed by Anthropic or Anthropic.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download onboarding.zip