agentleFS
nisarthnisarth/claude-skills-store/skills/human-resources/onboarding/SKILL.md

onboarding

Skill1 starsChanged 7 months agoMITView on GitHub

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.

100 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use paywalls, popups and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • CesarjoquinSkill

    paywalls

    When the user wants to create or optimize in-app paywalls, upgrade screens, upsell modals, or feature gates. Also use when the user mentions "paywall," "upgrade screen," "upgrade modal," "upsell," "feature gate," "convert free to paid," "freemium conversion," "trial expiration screen," "limit reached screen," "plan upgrade prompt," "in-app pricing," "free users won't upgrade," "trial to paid conversion," or "how do I get users to pay." Use this for any in-product moment where you're asking users to upgrade. Distinct from public pricing pages (see cro) — this focuses on in-product upgrade moments where the user has already experienced value. For pricing decisions, see pricing.

    Also in 19 projects that use this

  • CesarjoquinSkill

    popups

    When the user wants to create or optimize popups, modals, overlays, slide-ins, or banners for conversion purposes. Also use when the user mentions "exit intent," "popup conversions," "modal optimization," "lead capture popup," "email popup," "announcement banner," "overlay," "collect emails with a popup," "exit popup," "scroll trigger," "sticky bar," or "notification bar." Use this for any overlay or interrupt-style conversion element. For forms outside of popups, see cro. For general page conversion optimization, see cro.

    Also in 18 projects that use this

  • coreyhaines31Skill

    marketing-council

    When the user wants multiple expert perspectives on a marketing question — a simulated board of advisors staffed by legendary marketers (Seth Godin, David Ogilvy, Eugene Schwartz, April Dunford, Rory Sutherland, Alex Hormozi, Byron Sharp, and more). Also use when the user mentions 'marketing council,' 'board of advisors,' 'advisory board,' 'what would Seth Godin say,' 'what would Ogilvy think,' 'channel Hormozi,' 'get multiple perspectives,' 'debate this,' 'have the council review,' 'marketing mentors,' or asks how a famous marketer would approach their problem. The council gives each advisor's take through their documented frameworks, surfaces where they disagree, and synthesizes a recommendation. For executing the winning direction, hand off to positioning, offers, copywriting, ads, or the relevant skill.

    Also in 13 projects that use this

  • roerohanSkill

    prospecting

    When the user wants to find, qualify, and build a list of prospects to reach out to — across B2B SaaS, general B2B, or local small businesses. Also use when the user mentions "prospecting," "build a prospect list," "find prospects," "find leads," "lead gen list," "find SaaS companies that," "find B2B companies," "find local businesses," "ICP-fit accounts," "who should we go after," "outbound list," "target account list," "find clients near me," "businesses without websites," "prospect research," "qualified leads," "find my first customers," "early adopters," "design partners," "beta users," or "who has this problem." Use this for the list-building and qualification phase. For writing the outbound copy after the list is built, see cold-email. For deep competitive research on specific accounts, see competitor-profiling.

    Also in 16 projects that use this

  • roerohanSkill

    emails

    When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," "lifecycle emails," "trigger-based emails," "email funnel," "email workflow," "what emails should I send," "welcome series," or "email cadence." Use this for any multi-email automated flow. For cold outreach emails, see cold-email. For in-app onboarding, see onboarding.

    Also in 18 projects that use this

  • +7 more from Cesarjoquin

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 85 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Create email account and calendar

    line 54
  2. Distinctive:

    Add to payroll system

    line 63
  3. Distinctive:

    Create employee profile in HRIS

    line 64
  4. Distinctive:

    Do not schedule more than 4 hours of meetings on Day 1.

    line 190
  5. Distinctive:

    Check in at the end of Week 1, Day 30, Day 60, and Day 90.

    line 192

“Common” is measured: kept by at least 6 in 10 of the 85 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Onboarding Plan Generator

Generate comprehensive onboarding checklists covering pre-start preparation, Day 1 orientation, Week 1 schedule, and 30/60/90-day goals tailored to the role and department.

Workflow

Step 1: Determine Onboarding Scope

Based on the role and employment type, select the appropriate onboarding track:

  • Standard (full-time IC): Full onboarding with all phases
  • Manager/Director: Standard plus leadership introductions, direct report 1:1s, budget access
  • Executive: White-glove onboarding with board introductions, EA assignment, strategic briefings
  • Contractor: Streamlined onboarding focused on access, scope, and deliverables
  • Intern: Structured program with mentor assignment, project scoping, and learning goals

Collect missing details:

  • Manager name and team structure
  • Office location or remote setup
  • Required tools and system access
  • Buddy or onboarding partner assignment

Step 2: Generate Pre-Start Checklist (T-minus 2 weeks to Day 0)

IT and Access (IT/Admin owns):

  • Provision laptop and peripherals
  • Create email account and calendar
  • Set up SSO and password manager
  • Grant access to required systems (list by role)
  • Ship equipment if remote

HR and Admin (HR owns):

  • Send welcome email with Day 1 logistics
  • Complete I-9 and tax documentation
  • Enroll in benefits (or send enrollment link)
  • Add to payroll system
  • Create employee profile in HRIS

Manager (Hiring Manager owns):

  • Assign onboarding buddy
  • Schedule Week 1 meetings and introductions
  • Prepare role-specific reading list or documentation
  • Set up recurring 1:1 meetings
  • Notify the team of the new hire and start date

Step 3: Create Day 1 Plan

Morning:

  • Welcome and office/remote setup walkthrough
  • Meet hiring manager (30 min): Team overview, expectations, first priorities
  • IT setup verification: Confirm all accounts and tools are working
  • HR orientation (60 min): Benefits overview, handbook, policies, emergency contacts

Afternoon:

  • Team lunch or virtual coffee
  • Meet onboarding buddy (30 min): Informal culture introduction
  • Self-paced: Complete required compliance training
  • Self-paced: Review team documentation, wikis, and project boards
  • End-of-day check-in with manager (15 min)

Step 4: Create Week 1 Schedule

Map out a day-by-day schedule:

  • Day 2: 1:1s with immediate team members, dev environment or tool setup
  • Day 3: Cross-functional introductions, shadow a team meeting or workflow
  • Day 4: Deep-dive into current projects, begin first small task or onboarding project
  • Day 5: Week 1 retrospective with manager, adjust Week 2 priorities

Step 5: Define 30/60/90-Day Goals

30 Days (Learn):

  • Complete all onboarding training and compliance requirements
  • Understand team processes, tools, and communication norms
  • Build relationships with immediate team and key stakeholders
  • Complete first deliverable or onboarding project
  • Identify 3 areas of ambiguity and discuss with manager

60 Days (Contribute):

  • Own a workstream or project independently
  • Participate in team planning and retrospectives
  • Provide feedback on onboarding experience
  • Begin building cross-functional relationships
  • Set personal development goals with manager

90 Days (Own):

  • Deliver measurable impact on a team objective
  • Operate independently with minimal guidance
  • Contribute to process improvements based on fresh-eyes observations
  • Complete performance check-in with manager
  • Establish long-term goals and development plan

Output Format

## Onboarding Plan: [Name] — [Role]

**Start Date**: [date]
**Manager**: [name]
**Buddy**: [name/TBD]
**Location**: [office/remote]

---

### Pre-Start Checklist (2 weeks before Day 1)

#### IT and Access
- [ ] Laptop provisioned and shipped
- [ ] Email and calendar created
- [ ] SSO and password manager configured
- [ ] System access granted: [list tools]
- [ ] VPN access configured (if remote)

#### HR and Admin
- [ ] Welcome email sent
- [ ] I-9 and tax documents completed
- [ ] Benefits enrollment initiated
- [ ] Payroll setup confirmed
- [ ] HRIS profile created

#### Manager Prep
- [ ] Buddy assigned: [name]
- [ ] Week 1 meetings scheduled
- [ ] Reading list prepared
- [ ] Team notified of new hire
- [ ] 1:1 recurring meeting created

### Day 1 Schedule
| Time       | Activity                        | Owner    |
|-----------|--------------------------------|----------|
| 9:00 AM    | Welcome and setup               | Manager  |
| 9:30 AM    | Manager 1:1                     | Manager  |
| 10:30 AM   | HR orientation                  | HR       |
| 12:00 PM   | Team lunch                      | Buddy    |
| 1:00 PM    | Buddy intro and culture chat    | Buddy    |
| 2:00 PM    | Compliance training (self-paced)| New Hire |
| 3:30 PM    | Documentation review            | New Hire |
| 4:30 PM    | End-of-day check-in             | Manager  |

### Week 1 Overview
[Day-by-day breakdown]

### 30/60/90-Day Goals
[Structured goals by phase]

Examples

User: "Create an onboarding plan for a new Senior Data Engineer starting March 15." Action: Generate full onboarding plan with data-engineering-specific tool access (Snowflake, Airflow, dbt), data team introductions, and technical ramp-up goals.

User: "Onboarding checklist for a contractor joining the design team." Action: Generate streamlined contractor checklist focused on access provisioning, scope definition, and project kickoff. Skip benefits enrollment and long-term goal setting.

User: "30/60/90 plan for a new VP of Marketing." Action: Generate executive-track 30/60/90 with strategic assessment, stakeholder mapping, team evaluation, and first-quarter priorities.

Best Practices

  • Send the welcome email at least one week before Day 1 so the new hire arrives feeling expected and prepared.
  • Front-load people introductions over process training. Relationships drive successful onboarding more than documentation.
  • Assign the onboarding buddy from a different sub-team than the manager to give broader perspective.
  • Do not schedule more than 4 hours of meetings on Day 1. New hires need unstructured time to set up and absorb.
  • Make the 30-day goal achievable and specific. A quick win builds confidence.
  • Check in at the end of Week 1, Day 30, Day 60, and Day 90. Do not wait for the first formal review.
  • Customize system access lists by role. Engineering needs GitHub and CI/CD; marketing needs CMS and analytics.
  • For remote hires, ship equipment to arrive 2-3 business days before start date to allow for setup issues.
  • Include a "fresh eyes feedback" prompt at Day 30. New hires see inefficiencies that tenured employees miss.
  • Track onboarding task completion in a shared document so both the new hire and manager can see progress.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.