onboarding-checklist
Create comprehensive onboarding plans that set new hires up for success. Use this skill when preparing for new employee arrivals, improving onboarding processes, or building role-specific onboarding. Activate when: onboarding, new hire, first day, new employee, orientation, employee onboarding, 30-60-90.
What this skill does
# Onboarding Checklist **Set new hires up for success with structured onboarding.** ## When to Use - Preparing for a new hire's arrival - Building role-specific onboarding programs - Improving existing onboarding processes - Creating 30-60-90 day plans - Ensuring consistent onboarding across teams ## Pre-Start Checklist (Before Day 1) ### 1 Week Before ```markdown ## IT & Access - [ ] Laptop/equipment ordered and configured - [ ] Email account created - [ ] Slack/Teams account set up - [ ] Required software licenses provisioned - [ ] Building/office access arranged - [ ] VPN access configured (if remote) ## HR & Admin - [ ] Offer letter signed and filed - [ ] Background check completed - [ ] I-9/work authorization ready - [ ] Benefits enrollment information prepared - [ ] Payroll set up - [ ] Emergency contact form ready ## Team Preparation - [ ] Onboarding buddy assigned - [ ] First week meetings scheduled - [ ] Welcome announcement drafted - [ ] Desk/workspace prepared (if on-site) - [ ] Team lunch scheduled ``` ### Day Before ```markdown - [ ] Welcome email sent with Day 1 logistics - [ ] Calendar invites confirmed - [ ] Manager 1:1 scheduled for Day 1 - [ ] Equipment delivery confirmed (if remote) - [ ] Team notified of new hire start ``` ## Day 1 Checklist ### Morning ```markdown ## Welcome & Setup (First 2 hours) - [ ] Warm welcome from manager - [ ] Office tour / virtual workspace orientation - [ ] Equipment setup and login - [ ] Introductions to immediate team - [ ] Review Day 1 agenda ## Admin & HR - [ ] Complete I-9 verification - [ ] Review and sign policies - [ ] Benefits enrollment walkthrough - [ ] Security and compliance training - [ ] Set up direct deposit ``` ### Afternoon ```markdown ## Orientation - [ ] Company overview presentation - [ ] Mission, values, and culture - [ ] Organization structure - [ ] Key tools and systems training - [ ] Communication norms and channels ## Role Introduction - [ ] Manager 1:1: expectations and goals - [ ] Team structure and responsibilities - [ ] Current projects overview - [ ] Access to documentation and resources - [ ] End-of-day check-in ``` ## Week 1 Checklist ```markdown ## Learning & Context - [ ] Complete required compliance training - [ ] Review team documentation and wikis - [ ] Shadow key meetings - [ ] Meet with onboarding buddy daily - [ ] Understand current priorities and projects ## Connections - [ ] 1:1s with each team member - [ ] Meet key cross-functional partners - [ ] Join relevant Slack channels - [ ] Attend team standup/meetings ## Quick Wins - [ ] Complete small starter task - [ ] Set up development environment (if applicable) - [ ] Make first contribution (code, doc, etc.) ## End of Week 1 - [ ] Manager check-in: questions, feedback, blockers - [ ] Onboarding feedback survey - [ ] Review Week 2 plan ``` ## 30-60-90 Day Plan ### Days 1-30: Learn ```markdown ## Goals - Understand the company, team, and role - Build relationships with key stakeholders - Complete all required training - Start contributing to team projects ## Milestones - [ ] Complete all compliance and security training - [ ] Meet with all direct team members - [ ] Understand team goals and priorities - [ ] Complete first small project or task - [ ] Document questions and learnings - [ ] Receive first round of feedback ## Success Metrics - Training completion: 100% - Stakeholder meetings: [X] completed - First contribution delivered ``` ### Days 31-60: Contribute ```markdown ## Goals - Take ownership of specific responsibilities - Contribute meaningfully to team projects - Identify process improvements - Build broader organizational relationships ## Milestones - [ ] Own [specific area or project] - [ ] Complete [medium-sized project] - [ ] Present work to broader team - [ ] Propose one process improvement - [ ] Expand network beyond immediate team ## Success Metrics - Projects completed: [X] - Independent ownership demonstrated - Cross-functional relationships established ``` ### Days 61-90: Own ```markdown ## Goals - Operate independently in role - Drive projects from start to finish - Mentor newer team members - Contribute to team strategy ## Milestones - [ ] Lead [significant project or initiative] - [ ] Deliver measurable impact - [ ] Contribute to team planning - [ ] Support onboarding of newer hires - [ ] Complete 90-day review ## Success Metrics - Key deliverables completed - Positive 90-day review - Team contribution recognized ``` ## Role-Specific Additions ### Engineering Onboarding ```markdown Week 1: - [ ] Development environment setup - [ ] Codebase walkthrough - [ ] Architecture overview - [ ] First PR merged Week 2-4: - [ ] Complete starter bugs/tasks - [ ] Participate in code reviews - [ ] On-call shadowing - [ ] Understand deployment process ``` ### Sales Onboarding ```markdown Week 1-2: - [ ] Product training and certification - [ ] CRM and tools training - [ ] Shadow discovery calls - [ ] Review sales playbook Week 3-4: - [ ] First prospecting activities - [ ] Practice pitch with feedback - [ ] Shadow closing calls - [ ] Begin building pipeline ``` ### Manager Onboarding ```markdown Week 1-2: - [ ] 1:1s with all direct reports - [ ] Understand each person's goals and challenges - [ ] Review team performance history - [ ] Meet with peer managers Week 3-4: - [ ] Stakeholder mapping - [ ] Understand team dynamics - [ ] Review processes and rituals - [ ] Identify quick wins ``` ## Onboarding Feedback Template ```markdown ## 30/60/90 Day Check-in 1. What's going well so far? 2. What's been challenging or confusing? 3. Do you have everything you need to do your job? 4. How is your relationship with your manager? 5. How is your relationship with the team? 6. What could we improve about onboarding? 7. On a scale of 1-10, how supported do you feel? 8. Any other feedback or concerns? ``` ## Best Practices 1. **Assign an onboarding buddy** - Peer support accelerates integration 2. **Don't overwhelm Day 1** - Spread information across weeks 3. **Schedule manager 1:1s early and often** - Weekly minimum for first 90 days 4. **Provide quick wins** - Early success builds confidence 5. **Gather feedback** - Continuously improve the process 6. **Customize by role** - One size doesn't fit all 7. **Document everything** - Reduce tribal knowledge dependency
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.