MCP HubMCP Hub
Retour aux compétences

onboarding-guide

guia-matthieu
Mis à jour Yesterday
3 vues
111
20
111
Voir sur GitHub
Designdesign

À propos

La compétence onboarding-guide aide les développeurs à concevoir des programmes d'intégration structurés en utilisant une progression par étapes et des ressources organisées. Elle est utile pour créer des plans et des listes de contrôle à l'échelle de l'entreprise ou spécifiques à un rôle, ainsi que pour mesurer leur efficacité. Les principales fonctionnalités incluent des cadres 30-60-90 jours, une focalisation sur l'intégration sociale et des étapes de compétences mesurables basées sur des méthodologies de recherche établies.

Installation rapide

Claude Code

Recommandé
Principal
npx skills add guia-matthieu/clawfu-skills -a claude-code
Commande PluginAlternatif
/plugin add https://github.com/guia-matthieu/clawfu-skills
Git CloneAlternatif
git clone https://github.com/guia-matthieu/clawfu-skills.git ~/.claude/skills/onboarding-guide

Copiez et collez cette commande dans Claude Code pour installer cette compétence

Documentation

Onboarding Guide

Create structured onboarding programs that accelerate new hire productivity through clear milestones, organized resources, and measurable outcomes.

When to Use This Skill

  • Designing company onboarding
  • Creating role-specific plans
  • Building onboarding checklists
  • Measuring onboarding effectiveness
  • Improving time-to-productivity

Methodology Foundation

Based on Gallup Q12 engagement research and BambooHR onboarding studies, combining:

  • 30-60-90 day frameworks
  • Milestone-based progression
  • Social integration focus
  • Measurable competency gates

What Claude Does vs What You Decide

Claude DoesYou Decide
Structures onboarding phasesTimeline flexibility
Creates milestone checklistsResource availability
Suggests activitiesBuddy assignments
Identifies success metricsPerformance standards
Drafts welcome materialsCultural elements

Instructions

Step 1: Define Onboarding Goals

Core Objectives:

ObjectiveMeasureTarget
ProductivityTime to first contribution30 days
EngagementPulse survey score4+/5
Retention90-day retention95%+
CultureManager satisfaction4+/5
ComplianceTraining completion100%

Step 2: Design Phase Structure

30-60-90 Framework:

PhaseDaysFocusOutcome
Absorb1-30Learn, observe, connectUnderstands role
Adapt31-60Apply, contribute, askMaking contributions
Accelerate61-90Own, improve, leadFully productive

Step 3: Create Milestone Checklists

Checklist Categories:

  1. Administrative setup
  2. Tools and systems
  3. People and relationships
  4. Role-specific training
  5. Cultural integration

Step 4: Build Resource Library

Resource Organization:

CategoryContents
CompanyVision, values, org chart
RoleJD, expectations, success criteria
ToolsSystem access, tutorials
PeopleTeam bios, stakeholder map
CultureNorms, rituals, communication

Step 5: Measure Success

Checkpoint Assessments:

DayAssessmentOwner
7First week check-inManager
14Buddy feedbackBuddy
3030-day reviewManager
60Progress assessmentManager
90Performance reviewManager + HR

Examples

Example 1: Complete 30-60-90 Onboarding Plan

Input:

Create onboarding plan for:
- Role: Marketing Manager
- Team: 3 marketers, reports to VP Marketing
- Key tools: HubSpot, Google Analytics, Figma
- First project: Q2 campaign planning

Output:

## 30-60-90 Onboarding Plan: Marketing Manager

### Role Overview

| Element | Detail |
|---------|--------|
| Title | Marketing Manager |
| Reports To | VP Marketing |
| Team | 3 direct reports |
| Start Date | [Date] |
| Buddy | [Senior Marketing Manager] |

---

## Pre-Start Checklist (Before Day 1)

**IT/Admin:**
- [ ] Email account created
- [ ] Laptop ordered and configured
- [ ] Building access/badge
- [ ] HubSpot seat provisioned
- [ ] Google Analytics access
- [ ] Figma seat added
- [ ] Slack workspace invite

**Manager Prep:**
- [ ] First week calendar blocked
- [ ] Buddy assigned and briefed
- [ ] Welcome message drafted
- [ ] Desk/workspace ready
- [ ] Team notified of start date

---

## Phase 1: ABSORB (Days 1-30)

### Goal
Understand the company, team, and role fundamentals

### Week 1: Orientation

**Day 1 - Welcome**
| Time | Activity | Owner |
|------|----------|-------|
| 9:00 | Welcome from manager | VP Marketing |
| 9:30 | IT setup and security training | IT |
| 10:30 | Office tour | Buddy |
| 11:00 | HR paperwork and benefits | HR |
| 12:00 | Team lunch | Team |
| 1:30 | Company overview presentation | VP Marketing |
| 3:00 | Tool access verification | Self |
| 4:00 | First 1:1 with manager | VP Marketing |

**Day 2-3 - Company Deep Dive**
- [ ] Complete company history module
- [ ] Review brand guidelines
- [ ] Read last 2 quarterly reports
- [ ] Watch CEO all-hands recording
- [ ] Review competitor landscape doc

**Day 4-5 - Marketing Team Orientation**
- [ ] 1:1 with each team member (3 × 30 min)
- [ ] Review team OKRs and metrics
- [ ] Understand current campaigns
- [ ] Access marketing dashboards
- [ ] Review content calendar

### Week 2: Systems and Stakeholders

**Tools Training:**
- [ ] HubSpot certification (8 hours)
- [ ] Google Analytics walkthrough
- [ ] Figma basics tutorial
- [ ] Internal wiki navigation

**Stakeholder Meetings:**
| Person | Role | Purpose |
|--------|------|---------|
| Head of Sales | Revenue partner | Understand MQL handoff |
| Product Manager | Product launches | Align on roadmap |
| Customer Success | Customer voice | Understand retention |
| Finance | Budget partner | Understand process |

### Week 3-4: Role Immersion

**Activities:**
- [ ] Shadow team members on key tasks
- [ ] Review past 6 months of campaigns
- [ ] Analyze top-performing content
- [ ] Understand lead scoring model
- [ ] Map customer journey documentation

**Deliverable:** Present "30-Day Observations" to VP Marketing
- What I've learned
- Questions I have
- Initial opportunities I see

---

### Phase 1 Milestones

| Milestone | Due | Status |
|-----------|-----|--------|
| All system access working | Day 3 | [ ] |
| Completed company training | Day 5 | [ ] |
| Met all key stakeholders | Day 14 | [ ] |
| HubSpot certification | Day 21 | [ ] |
| 30-day presentation | Day 30 | [ ] |

### Phase 1 Success Criteria

| Criterion | Measure | Target |
|-----------|---------|--------|
| System proficiency | Can navigate independently | Yes/No |
| Team relationships | Buddy rating | 4+/5 |
| Company knowledge | Quiz score | 80%+ |
| Engagement | Pulse check | Positive |

---

## Phase 2: ADAPT (Days 31-60)

### Goal
Start contributing and take ownership of initial responsibilities

### Responsibilities Ramp

**Week 5-6: Supporting Role**
- [ ] Co-lead weekly marketing meeting
- [ ] Review and approve team content
- [ ] Begin 1:1s with direct reports
- [ ] Contribute to campaign ideation

**Week 7-8: Primary Ownership**
- [ ] Lead weekly marketing meeting
- [ ] Own content calendar decisions
- [ ] First budget planning input
- [ ] Draft Q2 campaign strategy

### Key Activities

**Campaign Planning:**
- [ ] Analyze Q1 campaign performance
- [ ] Interview Sales on lead quality
- [ ] Research competitor Q2 activities
- [ ] Draft Q2 campaign brief

**Team Management:**
- [ ] Establish 1:1 cadence with reports
- [ ] Complete first performance check-ins
- [ ] Identify team training needs

**Deliverable:** Q2 Campaign Proposal Presentation

---

### Phase 2 Milestones

| Milestone | Due | Status |
|-----------|-----|--------|
| First campaign contribution | Day 35 | [ ] |
| Leading weekly meeting | Day 42 | [ ] |
| Team 1:1 rhythm established | Day 45 | [ ] |
| Q2 campaign proposal | Day 60 | [ ] |

### Phase 2 Success Criteria

| Criterion | Measure | Target |
|-----------|---------|--------|
| Campaign contribution | VP approval | Yes |
| Team feedback | Skip-level pulse | 4+/5 |
| Independence | Manager assessment | 4+/5 |

---

## Phase 3: ACCELERATE (Days 61-90)

### Goal
Operate independently and drive impact

### Full Ownership

**Responsibilities:**
- [ ] Full ownership of Q2 campaign execution
- [ ] Team performance management
- [ ] Budget management ($X/quarter)
- [ ] Cross-functional project leadership
- [ ] Process improvement initiatives

### Key Activities

**Campaign Execution:**
- [ ] Launch Q2 campaign
- [ ] Establish reporting cadence
- [ ] First optimization cycle

**Strategic Contribution:**
- [ ] Participate in H2 planning
- [ ] Identify one process improvement
- [ ] Present results to leadership

**Deliverable:** 90-Day Impact Report
- Campaigns launched/contributed
- Metrics influenced
- Team development actions
- Recommendations for next 90 days

---

### Phase 3 Milestones

| Milestone | Due | Status |
|-----------|-----|--------|
| Q2 campaign launched | Day 70 | [ ] |
| First optimization cycle | Day 80 | [ ] |
| 90-day review completed | Day 90 | [ ] |

### Phase 3 Success Criteria

| Criterion | Measure | Target |
|-----------|---------|--------|
| Campaign performance | KPIs met | 80%+ |
| Team satisfaction | Survey | 4+/5 |
| Manager confidence | Assessment | Ready for full autonomy |

---

## Resources

### Company
- [ ] Employee handbook
- [ ] Org chart
- [ ] Company values document
- [ ] Strategic plan summary

### Marketing
- [ ] Brand guidelines
- [ ] Content style guide
- [ ] Campaign playbooks
- [ ] Competitor analysis

### Tools
- [ ] HubSpot training library
- [ ] GA4 course link
- [ ] Figma tutorials
- [ ] Internal wiki

### People
- [ ] Team bios and backgrounds
- [ ] Stakeholder map
- [ ] Slack channel guide
- [ ] Meeting cadence overview

Example 2: Quick First Week Schedule

Input:

Create a first week schedule for a new software engineer.

Output:

## First Week Schedule: Software Engineer

### Day 1 (Monday) - Welcome & Setup

| Time | Activity | Owner |
|------|----------|-------|
| 9:00 | Welcome, team intro | Manager |
| 9:30 | IT setup, equipment | IT |
| 10:30 | Security training | IT |
| 11:30 | Office tour | Buddy |
| 12:00 | Team lunch | Team |
| 1:00 | HR onboarding | HR |
| 2:30 | Dev environment setup | Buddy |
| 4:00 | End-of-day check-in | Manager |

### Day 2 (Tuesday) - Technical Orientation

| Time | Activity | Notes |
|------|----------|-------|
| 9:00 | Architecture overview | Senior Engineer |
| 10:30 | Codebase walkthrough | Buddy |
| 12:00 | Lunch | Self |
| 1:00 | CI/CD pipeline training | DevOps |
| 3:00 | First PR: Update README | Self + Buddy |
| 4:30 | Questions & wrap-up | Buddy |

### Day 3 (Wednesday) - Deep Dives

| Time | Activity | Notes |
|------|----------|-------|
| 9:00 | Product overview | Product Manager |
| 10:30 | Database schema review | DBA/Senior |
| 12:00 | Lunch with another team | Networking |
| 1:00 | Testing practices | QA Lead |
| 3:00 | Pair programming session | Buddy |
| 4:30 | Check-in | Manager |

### Day 4 (Thursday) - Stakeholders

| Time | Activity | Notes |
|------|----------|-------|
| 9:00 | Design team intro | UX Lead |
| 10:00 | Support team overview | Support Lead |
| 11:00 | Self-study: Documentation | Self |
| 12:00 | Skip-level lunch | Director |
| 1:30 | Pick first bug/ticket | Manager assigns |
| 4:00 | Work on first ticket | Self + Buddy available |

### Day 5 (Friday) - First Contribution

| Time | Activity | Notes |
|------|----------|-------|
| 9:00 | Continue first ticket | Self |
| 11:00 | Team standup | Observe |
| 12:00 | Team lunch (TGIF) | Team tradition |
| 1:30 | Complete first PR | Self |
| 3:00 | Code review feedback | Buddy |
| 4:00 | Week 1 retrospective | Manager |
| 4:30 | Plan for Week 2 | Manager |

### Week 1 Success Checklist

- [ ] All accounts and access working
- [ ] Can build and run locally
- [ ] Completed security training
- [ ] Met all immediate team members
- [ ] First PR merged
- [ ] Understands team processes
- [ ] Calendar has Week 2 blocked

Skill Boundaries

What This Skill Does Well

  • Structuring onboarding phases
  • Creating comprehensive checklists
  • Organizing resources
  • Setting success criteria

What This Skill Cannot Do

  • Know company-specific systems
  • Access internal resources
  • Assess individual readiness
  • Replace manager judgment

Iteration Guide

Follow-up Prompts:

  • "Create the 30-day presentation template"
  • "What questions should managers ask at check-ins?"
  • "Design an onboarding feedback survey"
  • "How should we handle remote onboarding?"

References

  • BambooHR Onboarding Statistics
  • Gallup Q12 Engagement Framework
  • SHRM Onboarding Best Practices
  • Google's Noogler Experience

Related Skills

  • resume-screener - Pre-hire assessment
  • interview-scheduler - Hiring process
  • employee-support - Ongoing support

Skill Metadata

  • Domain: HR Operations
  • Complexity: Intermediate
  • Mode: cyborg
  • Time to Value: 2-4 hours per role
  • Prerequisites: Role requirements, company context

Dépôt GitHub

guia-matthieu/clawfu-skills
Chemin: skills/hr-ops/onboarding-guide
0
ai-skillsanthropicclaude-codeclaude-skillsmarketingmcp-server

Compétences associées

executing-plans

Design

Utilisez la compétence executing-plans lorsque vous disposez d'un plan de mise en œuvre complet à exécuter par lots contrôlés avec des points de contrôle de revue. Elle charge et examine le plan de manière critique, puis exécute les tâches par petits lots (3 tâches par défaut) tout en rapportant la progression entre chaque lot pour une revue par l'architecte. Cela garantit une mise en œuvre systématique avec des points de contrôle de qualité intégrés.

Voir la compétence

requesting-code-review

Design

Cette compétence délègue un sous-agent réviseur de code pour analyser les modifications apportées au code par rapport aux exigences avant de poursuivre. Elle doit être utilisée après avoir terminé des tâches, implémenté des fonctionnalités majeures, ou avant une fusion vers la branche principale. La revue aide à détecter précocement les problèmes en comparant l'implémentation actuelle avec le plan initial.

Voir la compétence

connect-mcp-server

Design

Cette compétence fournit un guide complet permettant aux développeurs de connecter des serveurs MCP à Claude Code via les transports HTTP, stdio ou SSE. Elle couvre l'installation, la configuration, l'authentification et la sécurité pour intégrer des services externes tels que GitHub, Notion et des API personnalisées. Utilisez-la lors de la configuration d'intégrations MCP, de la configuration d'outils externes ou du travail avec le Protocole de Contexte de Modèle de Claude.

Voir la compétence

web-cli-teleport

Design

Cette compétence aide les développeurs à choisir entre les interfaces Web et CLI de Claude Code en fonction de l'analyse des tâches, puis permet une téléportation transparente des sessions entre ces environnements. Elle optimise le flux de travail en gérant l'état et le contexte de la session lors du passage entre le web, la CLI ou le mobile. Utilisez-la pour des projets complexes nécessitant différents outils à diverses étapes.

Voir la compétence