Onboarding New Hires logo

Onboarding New Hires

Community
cnfeat
onboarding-new-hires

Help users onboard new team members effectively. Use when someone is planning onboarding for a new hire, starting a new job themselves, designing a first-90-days plan, or trying to ramp up new employees faster.

Overview

Publishercnfeat
Repositorytop-pm-skills
Skill nameonboarding-new-hires
Stars
55
Forks
6
Bundled files
1
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 1 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by cnfeat on GitHub. Read the source before you install it.

Installation

Install the Onboarding New Hires AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/cnfeat/top-pm-skills/tree/main/参考skill/lenny-skills-main%20(2)/lenny-skills-main/skills/onboarding-new-hires
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Use it in TypingMind

Enable Onboarding New Hires in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Onboarding New Hires on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Onboarding New Hires is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Onboarding New Hires

Help the user onboard new team members effectively using approaches from 14 product leaders.

How to Help

When the user asks for help with onboarding:

  1. Understand the context - Ask if they're onboarding someone or being onboarded, the seniority level, and whether it's a new role or backfill
  2. Design the structure - Help them create a 30-60-90 day plan with clear milestones and success criteria
  3. Prioritize belonging and learning - Ensure the plan includes social integration, not just tasks
  4. Engineer early wins - Identify opportunities for the new hire to demonstrate value quickly

Core Principles

Listen first, act later - diagnose before you treat

Deb Liu: "The first 90 days are focused on listening and learning first, then doing. Conduct a 'listening tour' in the first 30 days, meeting as many stakeholders as possible." Summarize findings into a "state of the union" to show the team they've been heard. Align on vision in days 30-60, move to full execution by day 90.

Define success at 90 days, 1 year, and 2 years

Lauren Ipsen: "The 90-day plan is overused but necessary, and that's just the tip of the iceberg. What should this person be doing a year from now? Two years from now?" Define what "crushing it" looks like at each milestone before starting the search.

Create immediate belonging through pairing

Heidi Helfand: "Help them feel a sense of belonging by not having their first day be them sitting alone. Have someone be a 'first pair.'" Ensure new hires are not working alone on day one. Assign a buddy to work with them immediately. Encourage sharing personal stories to build connection.

Teach golden rituals by the first Friday

Shishir Mehrotra: "Great companies have a very small list of golden rituals. Every employee knows them by their first Friday." Include core company rituals in the onboarding curriculum. These rituals should be named, known, and templated.

Engineer early wins for visibility

Melissa Tan: "How do I help them secure early wins? I'll suggest 'You should do this presentation - it's a great way to get visibility early.'" Identify low-hanging fruit projects for new hires. Create opportunities for them to present to leadership in their first weeks.

Document your philosophy publicly

Brandon Chu: "People joining my team already knew how I thought because they'd Google me. It passively onboarded a lot of the PMs." Write about your management and product philosophy. New hires can ramp up before their first day.

Have a "relationship design" conversation

Kenneth Berger: "For maybe your first 10-20 employees, have a relationship design conversation when they're hired." Collaboratively figure out the best way to work together given specific roles and personalities. This prevents friction and "out of integrity" behavior later.

Don't overpromise during hiring

Molly Graham: "Do not promise things you can't control. Be honest about the ambiguity and chaos of a scaling environment." Avoid promising stability, specific titles, or career paths you can't guarantee. Overpromises become "letter bombs" that demoralize high performers when they explode.

Accelerate ownership with clear cadences

Timothy Davis: "I want to try and make onboarding 30-45 days by giving them responsibility early. Here's everything we did, here's your responsibilities, go." Use an ops cadence spreadsheet to define task frequency. Assign campaign or project ownership within the first few weeks.

Use AI for low-friction knowledge access

Scott Wu: "New engineers can ask Devin questions about the codebase. It's nice to be able to ask without social pressure." AI tools can help new hires explore internal systems and ask "dumb questions" without feeling judged.

Questions to Help Users

  • "What does success look like at 30, 60, and 90 days for this person?"
  • "Who is their 'first pair' or buddy on day one?"
  • "What are the company's golden rituals they need to know by their first Friday?"
  • "What early win can we engineer to give them visibility and credibility?"
  • "Have you documented your philosophy anywhere they can read before starting?"
  • "What did you promise them during hiring that you need to deliver on?"

Common Mistakes to Flag

  • No structured 90-day plan - New hires need clear milestones. "Figure it out" is not onboarding
  • Leaving them alone on day one - Isolation kills belonging. Assign a pair from the start
  • All tasks, no relationships - Onboarding is social, not just functional. Prioritize introductions and connection
  • Delayed ownership - Don't wait months to give responsibility. Find ways to assign ownership in weeks
  • Over-promising during hiring - Be honest about chaos and ambiguity. Broken promises demoralize

Deep Dive

For all 14 insights from 14 guests, see references/guest-insights.md

Related Skills

  • Writing Job Descriptions
  • Conducting Interviews
  • Building Team Culture
  • Running Effective 1:1s

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Onboarding New Hires AI skill do?

Help users onboard new team members effectively. Use when someone is planning onboarding for a new hire, starting a new job themselves, designing a first-90-days plan, or trying to ramp up new employees faster.

Why use Onboarding New Hires on TypingMind?

Because you install it once and use it with any model. Onboarding New Hires is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Onboarding New Hires in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/cnfeat/top-pm-skills/tree/main/参考skill/lenny-skills-main%20(2)/lenny-skills-main/skills/onboarding-new-hires. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Onboarding New Hires?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Onboarding New Hires?

As many as you like. As long as a model supports skills, you can use Onboarding New Hires with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Onboarding New Hires AI skill free?

Yes. It is published on GitHub by cnfeat under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇