onboarding
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.
Best use case
onboarding is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
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.
Teams using onboarding should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/onboarding/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How onboarding Compares
| Feature / Agent | onboarding | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
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.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
Top AI Agents for Productivity
See the top AI agent skills for productivity, workflow automation, operational systems, documentation, and everyday task execution.
AI Agents for Marketing
Discover AI agents for marketing workflows, from SEO and content production to campaign research, outreach, and analytics.
AI Agents for Startups
Explore AI agent skills for startup validation, product research, growth experiments, documentation, and fast execution with small teams.
SKILL.md Source
# /onboarding > If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../../CONNECTORS.md). Generate a comprehensive onboarding plan for a new team member. ## Usage ``` /onboarding $ARGUMENTS ``` ## What I Need From You - **New hire name**: Who's starting? - **Role**: What position? - **Team**: Which team are they joining? - **Start date**: When do they start? - **Manager**: Who's their manager? ## Output ```markdown ## Onboarding Plan: [Name] — [Role] **Start Date:** [Date] | **Team:** [Team] | **Manager:** [Manager] ### Pre-Start (Before Day 1) - [ ] Send welcome email with start date, time, and logistics - [ ] Set up accounts: email, Slack, [tools for role] - [ ] Order equipment (laptop, monitor, peripherals) - [ ] Add to team calendar and recurring meetings - [ ] Assign onboarding buddy: [Suggested person] - [ ] Prepare desk / remote setup instructions ### Day 1 | Time | Activity | With | |------|----------|------| | 9:00 | Welcome and orientation | Manager | | 10:00 | IT setup and tool walkthrough | IT / Buddy | | 11:00 | Team introductions | Team | | 12:00 | Welcome lunch | Manager + Team | | 1:30 | Company overview and values | Manager | | 3:00 | Role expectations and 30/60/90 plan | Manager | | 4:00 | Free time to explore tools and docs | Self | ### Week 1 - [ ] Complete required compliance training - [ ] Read key documentation: [list for role] - [ ] 1:1 with each team member - [ ] Shadow key meetings - [ ] First small task or project assigned - [ ] End-of-week check-in with manager ### 30-Day Goals 1. [Goal aligned to role] 2. [Goal aligned to role] 3. [Goal aligned to role] ### 60-Day Goals 1. [Goal] 2. [Goal] ### 90-Day Goals 1. [Goal] 2. [Goal] ### Key Contacts | Person | Role | For What | |--------|------|----------| | [Manager] | Manager | Day-to-day guidance | | [Buddy] | Onboarding Buddy | Questions, culture, navigation | | [IT Contact] | IT | Tool access, equipment | | [HR Contact] | HR | Benefits, policies | ### Tools Access Needed | Tool | Access Level | Requested | |------|-------------|-----------| | [Tool] | [Level] | [ ] | ``` ## If Connectors Available If **~~HRIS** is connected: - Pull new hire details and team org chart - Auto-populate tools access list based on role If **~~knowledge base** is connected: - Link to relevant onboarding docs, team wikis, and runbooks - Pull the team's existing onboarding checklist to customize If **~~calendar** is connected: - Create Day 1 calendar events and Week 1 meeting invites automatically ## Tips 1. **Customize for the role** — An engineer's onboarding looks different from a designer's. 2. **Don't overload Day 1** — Focus on setup and relationships. Deep work starts Week 2. 3. **Assign a buddy** — Having a go-to person who isn't their manager makes a huge difference.
Related Skills
pipeline-review
Analyze pipeline health — prioritize deals, flag risks, get a weekly action plan. Use when running a weekly pipeline review, deciding which deals to focus on this week, spotting stale or stuck opportunities, auditing for hygiene issues like bad close dates, or identifying single-threaded deals.
forecast
Generate a weighted sales forecast with best/likely/worst scenarios, commit vs. upside breakdown, and gap analysis. Use when preparing a quarterly forecast call, assessing gap-to-quota from a pipeline CSV, deciding which deals to commit vs. call upside, or checking pipeline coverage against your number.
draft-outreach
Research a prospect then draft personalized outreach. Uses web research by default, supercharged with enrichment and CRM. Trigger with "draft outreach to [person/company]", "write cold email to [prospect]", "reach out to [name]".
daily-briefing
Start your day with a prioritized sales briefing. Works standalone when you tell me your meetings and priorities, supercharged when you connect your calendar, CRM, and email. Trigger with "morning briefing", "daily brief", "what's on my plate today", "prep my day", or "start my day".
create-an-asset
Generate tailored sales assets (landing pages, decks, one-pagers, workflow demos) from your deal context. Describe your prospect, audience, and goal — get a polished, branded asset ready to share with customers.
competitive-intelligence
Research your competitors and build an interactive battlecard. Outputs an HTML artifact with clickable competitor cards and a comparison matrix. Trigger with "competitive intel", "research competitors", "how do we compare to [competitor]", "battlecard for [competitor]", or "what's new with [competitor]".
call-summary
Process call notes or a transcript — extract action items, draft follow-up email, generate internal summary. Use when pasting rough notes or a transcript after a discovery, demo, or negotiation call, drafting a customer follow-up, logging the activity for your CRM, or capturing objections and next steps for your team.
update
Sync tasks and refresh memory from your current activity. Use when pulling new assignments from your project tracker into TASKS.md, triaging stale or overdue tasks, filling memory gaps for unknown people or projects, or running a comprehensive scan to catch todos buried in chat and email.
task-management
Simple task management using a shared TASKS.md file. Reference this when the user asks about their tasks, wants to add/complete tasks, or needs help tracking commitments.
memory-management
Two-tier memory system that makes Claude a true workplace collaborator. Decodes shorthand, acronyms, nicknames, and internal language so Claude understands requests like a colleague would. CLAUDE.md for working memory, memory/ directory for the full knowledge base.
write-spec
Write a feature spec or PRD from a problem statement or feature idea. Use when turning a vague idea or user request into a structured document, scoping a feature with goals and non-goals, defining success metrics and acceptance criteria, or breaking a big ask into a phased spec.
synthesize-research
Synthesize user research from interviews, surveys, and feedback into structured insights. Use when you have a pile of interview notes, survey responses, or support tickets to make sense of, need to extract themes and rank findings by frequency and impact, or want to turn raw feedback into roadmap recommendations.