Skill detail
hr-onboarding
Produces a single-page new-hire onboarding plan in HTML with first-week schedule, buddy and manager intro, learning track, equipment checklist, and 30/60/90-day milestones.
Why we recommend it: Directly produces new-hire onboarding plans with first-week schedule and 30/60/90 milestones.
Inspect before use
Read the source instructions and check the requirements before you install this skill.
SKILL.md
The saved excerpt is a snapshot from when this skill was listed. The external source remains the complete and most current version.
---
name: hr-onboarding
description: |
A new-hire onboarding plan as a single page — first week schedule,
buddy + manager intro, learning track, equipment checklist, and "you're
set when…" outcomes. Use when the brief mentions "onboarding",
"new hire", "first week plan", or "入职".
triggers:
- "onboarding"
- "new hire"
- "first week"
- "入职"
- "新员工"
od:
mode: prototype
platform: desktop
scenario: hr
preview:
type: html
entry: index.html
design_system:
requires: true
sections: [color, typography, layout, components]
craft:
requires: [accessibility-baseline]
example_prompt: "Build a 30-day onboarding plan for a new product designer joining a 40-person startup."
---
# HR Onboarding Skill
Produce a single-screen onboarding plan in HTML.
## Workflow
1. Read the active DESIGN.md.
2. Identify the role + tenure expectations from the brief. Default to a
30/60/90-day shape if unspecified.
3. Layout:
- Cover banner: name placeholder, role, start date, manager + buddy.
- "Day 1" panel with the literal schedule (kickoff time, lunch, 1:1 slot).
- First-week timeline (Mon → Fri, two activities per day).
- 30 / 60 / 90 day milestone cards with three concrete outcomes each.
- Resource list: handbook, Slack channels, key dashboards, payroll setup.
- "You're set when…" checklist — five outcomes with checkboxes.
4. Single inline `<style>`, semantic HTML.
## Output contract
```
<artifact identifier="onboarding-plan" type="text/html" title="Onboarding Plan">
<!doctype html>...</artifact>
```
Read the full source on GitHub (opens external page)