PaperclipOrg
Claude Agent Skill · by Anthropics

Onboarding

Install Onboarding skill for Claude Code from anthropics/knowledge-work-plugins.

Install
Terminal · npx
$npx skills add https://github.com/obra/superpowers --skill brainstorming
Works with Paperclip

How Onboarding fits into a Paperclip company.

Onboarding drops into any Paperclip agent that handles this kind of work. Assign it to a specialist inside a pre-configured PaperclipOrg company and the skill becomes available on every heartbeat — no prompt engineering, no tool wiring.

S
SaaS FactoryPaired

Pre-configured AI company — 18 agents, 18 skills, one-time purchase.

$27$59
Explore pack
Source file
SKILL.md104 lines
Expand
---name: onboardingdescription: 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.argument-hint: "<new hire name and role>"--- # /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 Goals1. [Goal aligned to role]2. [Goal aligned to role]3. [Goal aligned to role] ### 60-Day Goals1. [Goal]2. [Goal] ### 90-Day Goals1. [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.