# 12 Claude Skills That Carry a New Hire From Yes to Day 90 12 free Claude skills for employee onboarding: the pre-boarding plan, onboarding checklist, welcome pack, team intro, first goals and the first 90 days. - Page: https://lantern.meet-polar-bear.com/skills/onboarding-pack - Download: https://lantern.meet-polar-bear.com/skills/onboarding-pack.zip - Source: https://github.com/polar-bear-org/claude-skills/tree/main/packs/onboarding-pack - Price: free ## Install in Claude Code ``` /plugin marketplace add polar-bear-org/claude-skills /plugin install onboarding-pack@polar-bear-skills ``` ## The 12 skills you get The set is grouped by who installs it. Everyone starts with the same skill: - **Onboarding Setup** — use when: You've installed the skills and nothing is configured yet. Output: Your Onboarding HQ project created, company-onboarding-context.md filled in from one fifteen-minute interview, and a test run of your first skill. ### If you run onboarding (founder, HR lead, or HRBP) - **Preboarding Planner** — use when: Someone just accepted your offer and day one has to go right. Output: The plan from yes to day one: the handoff written down so nobody assumes someone else is doing it, the internal track with an owner and a date per item, the keep-warm touchpoints, and the open risks. - **Onboarding Comms Drafter** — use when: IT, finance and the workspace need to hear about the joiner, and nothing is written. Output: One short email per owner, under 100 words, one deadline in the first line and a checklist they can tick, plus the keep-warm notes to the joiner and the nudge for when nobody confirms. - **Welcome Brief Writer** — use when: The start is approaching and the joiner hasn't heard what it's actually like to work here. Output: The congratulations choreography for right after the yes, and the one-page cultural brief for three days before: hours, dress code, lunch, rituals and first-day logistics, in the company's real voice. - **Welcome Pack Designer** — use when: You want joiners to receive something on day one that isn't a mug they'll abandon. Output: The pack as a company standard: every item marked necessity or emotional with why it earned its place, the per-role variants, the sourcing and shipping realities, and budget math as ranges rather than invented prices. - **Onboarding Checklist Builder** — use when: A pre-boarding plan exists and needs to become something people can tick. Output: The per-joiner checklist by phase, every line a task with one named owner and one date, plus a self-contained HTML dashboard with tick boxes, progress per phase, and flags for anything past its deadline. - **Joiner Companion Builder** — use when: New joiners keep asking the same thirty questions and they all land on you. Output: The companion's instruction block, a coverage report against the questions joiners actually ask — its “not answered” list is your handbook's holes — and the deployment kit for a shared project or individual accounts. ### If you're the hiring manager - **Team Deck Builder** — use when: Someone starts next week and nothing explains where they landed. Output: A real pptx in four layers — company, function, team, person — 12 to 18 slides: the first run builds your master, every run after derives the per-joiner edition in minutes. - **Team Intro Writer** — use when: The team needs to hear who's joining before the person walks in. Output: One message under 150 words in your voice, with the joiner's own photo, their own background lines and only the personal details they offered, adapted per channel and never sent without their approval. - **First Goals Writer** — use when: A joiner has started and nobody has written down what success looks like. Output: Three to five 90-day goals on a 30/60/90 rhythm, each traced to a business goal and each naming the support it assumes, ending in the evaluation paragraph, plus the agenda for the one-hour ways-of-working session. - **Week One Designer** — use when: The start date is close and the joiner's calendar is still empty. Output: Day one hour by hour, the meeting map with who, when and why this person at two to three a day, the breathing room blocked on purpose, and the booking list handed to whoever owns calendars. ### If you're the one joining - **My First 90** — use when: You start Monday, and it's fifty names, a dozen systems and a hose. Output: Your own pinned chat as the dashboard: the 90-day map, the daily two-minute brief, your wins logged with their dates, and your half of the 30, 60 and 90-day conversations built from the chat's own history. ## Workflows - **Set up once** (You have installed the skills and nothing is configured yet.) Onboarding Setup → Joiner Companion Builder - **From yes to day one** (Someone just accepted the offer.) Preboarding Planner → Onboarding Comms Drafter → Welcome Brief Writer → Welcome Pack Designer → Onboarding Checklist Builder - **The manager's first weeks** (You are the hiring manager and the start date is close.) Team Deck Builder → Team Intro Writer → Week One Designer → First Goals Writer - **The joiner's own start** (You are the one starting on Monday.) Onboarding Setup → My First 90 ## The quality bar - Claude prepares and keeps track, humans welcome: no skill replaces the manager's first conversation, the team's hello, or the lunch on day one - The congratulations notes are prompted, never ghost-written: five real sentences from five real people beat five polished paragraphs from one skill - The joiner approves their own introduction before it is sent: they are being introduced, not announced - Every task carries one named owner and one date, and a task without an owner is written as a flagged gap rather than a wish - Flags are about the process, never the person: “IT not confirmed” is a flag; the joiner's enthusiasm is not a field anywhere - The brief describes the culture you have, not the culture you want, because the joiner re-reads it with new eyes after their first week - Nothing invented: systems come from the systems list, names from the roles section, prices from real research, and a gap gets surfaced instead of filled in - Sensitive data stays out of drafts and dashboards, and the serious matters — contracts, visas, conduct, health — get an owner and a deadline, not a paragraph ## Questions people ask ### What is in the Onboarding pack? 12 Claude skills that carry a new hire from yes to day 90: the pre-boarding plan, the setup emails, the welcome brief and pack, the checklist, the team deck, the intro, the first goals, the first week, and the joiner's own companion. ### How do I install these Claude skills? In Claude Code, two lines install all 12 at once. In Claude.ai or Claude Desktop, download the zip, open Settings, Skills, Add, and upload the skills you want. Either way it takes about five minutes. ### Do I need Claude Code to use them? No. The skills work in Claude.ai, Claude Desktop and Claude Code. In the app you upload them yourself; in Claude Code one command installs the whole pack. ### Do the skills work with ChatGPT or other assistants? They are built as Claude Skills, and installing them is a Claude feature. Each one is a plain Markdown file, so you can read it and reuse the method elsewhere, but it will not load and trigger by itself outside Claude. ### Will Claude welcome the new hire for us? No. Claude prepares and keeps track, humans welcome. No skill replaces the manager's first conversation, the team's hello, or the lunch on day one. The congratulations notes are prompted, never ghost-written, and the joiner approves their own introduction before it is sent. ### Is the pack free? Yes. It is free to use inside your company and in client work, and not for resale. There is no signup: the download and the install command are on this page. ## About Written by Polar Bear (https://meet-polar-bear.com/). Published on Lantern (https://lantern.meet-polar-bear.com/), which turns your notes, documents and call transcripts into social post drafts you review and publish.