onboarding-checklist
Skill1 starsChanged 5 months agoMITView on GitHub
Generate a complete new-client or new-hire onboarding sequence, phased and ready to run. Use when the user says "onboarding checklist", "onboard a client", "new hire onboarding", "client onboarding sequence", "ramp a new person", or "onboarding plan".
1 other project uses a version of this.
Adopted by
Most recently taken up by
- OneWave-AI/claude-skillstheir own version, first seen Sep 21, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- OneWave-AI/claude-skills★ 378same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository4 other files it gives its agents.
- calendar-cleanupSkill
- meeting-scheduler-replySkill
- reminder-and-no-show-reducerSkill
- sop-writerSkill
The file
Files
Onboarding Checklist
Generate a new-client or new-hire onboarding sequence.
When to use
You're bringing on a new client or new hire and want a phased, owner-assigned checklist that gets them set up to succeed.
What you'll need
Who you're onboarding (new client or new hire), what they're onboarding into, what success looks like, the tools/accounts involved, and the onboarding window if you know them.
Instructions
Collect any missing inputs from the user, then run this prompt:
You are an operations lead who designs onboarding processes. Build a complete onboarding sequence for the person below.
Onboarding: [new client / new hire]
Role or engagement: [e.g. monthly bookkeeping client / junior account manager]
What success looks like by the end: [e.g. first deliverable shipped / fully productive on their own]
Tools/accounts they need access to: [list, or "you suggest"]
Steps I already know I want: [list, or "you suggest"]
Total onboarding window: [e.g. first 2 weeks]
Produce a checklist grouped by phase (Before day 1, Day 1, Week 1, Week 2+). For each item give:
- The task, written as a clear action
- Who owns it (me, them, or a teammate)
- When it's due
- Why it matters in one short line
Flag anything that's a blocker (must happen before later steps can start). End with a 3-question check-in I should ask at the end of the window to confirm they're set up to succeed. Keep tasks concrete and skippable-if-not-relevant — no vague "get familiar with the team" filler.Tip: Tell Claude your actual tools (the CRM, the payment system, the shared drive) — generic onboarding lists are useless, and the specific access steps are exactly where people get stuck.
Built by Ootto — the AI autopilot that connects your tools once and runs invoicing, follow-up, and reports for you, automatically. Book a demo →
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
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.