Onboarding

Skill VRIL-LABS/skill-jam/skills/ai-ml/knowledge-work-plugins-main/knowledge-work-plugins-main/human-resources/skills/onboarding

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.From its SKILL.md

Install

npx -y skills add VRIL-LABS/skill-jam --skill onboarding

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

3.1 KB, 760 tokens by cl100k_base, as published. Nobody here has run it

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

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most codebase onboarding skills give in 760 tokens

Counted across 307 of the 325 authors here whose files we hold, read 2026-09-06

Focus first session on one successful outcomein 34 of 307, across 15 files
Show progress and celebrate completionsin 32 of 307, across 13 files
Prefer interactive doing over tutorialsin 32 of 307, across 13 files
Remove every step between signup and core valuein 32 of 307, across 13 files
Keep checklists to 3-7 items ordered by valuein 32 of 307, across 13 files
Read product marketing context before asking questionsin 28 of 307, across 13 files
Focus fixes on the biggest funnel drop-offsin 22 of 307, across 7 files
Define activation as the action most correlated with retentionin 20 of 307, across 6 files
Give one clear next action at every stepin 19 of 307, across 8 files
Understand product context and current state before recommendingin 15 of 307, across 3 files
Limit guided tours to five dismissable stepsin 15 of 307, across 6 files
Trace one request from entry to responsein 14 of 307, across 8 files

Said here and by no other author read

Collect new hire name, role, team, start date, manager
List pre-start tasks: welcome email, accounts, equipment
Schedule Day 1 activities hour by hour
Plan Week 1 training, 1:1s, and first task
Set 30, 60, and 90-day goals
List key contacts and their roles

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.