hr-onboarding
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", or "first week plan".
Source facts
- Repository
- sanghyunna/readable-studio
- Last source activity
- October 6, 2026 at 07:59
- Detected SKILL.md language
- English
- Stars
- 0
- Forks
- 0
Install options
The review-first prompt is selected by default. You can switch to a direct command or download a local copy.
Review the source files
Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.
File Explorer
3 filesShowing SKILL.md
SKILL.md
Source instructions · Read-only preview- 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", or "first week plan".
- triggers
- ["onboarding","new hire","first week"]
- readable
- {"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
With file tools, save or edit `index.html`; the saved file is the deliverable. Finish with a brief reference to that file and a summary of the change. Keep the user's topic in the document title.
<readable-delivery channel="no-file-tools">
Only without file tools, use this chat delivery channel with the stable identifier `index` and the user's topic in `title`:
```
<artifact identifier="index" type="text/html" title="Onboarding Plan">
<!doctype html>...</artifact>
```
</readable-delivery>
View on GitHub