Structured 30-60-90 day onboarding framework drawing from 14 product leaders' approaches.
Works with
Covers listening tours, milestone planning, early wins, and belonging through pairing rather than isolation on day one
Emphasizes defining success at 90 days, 1 year, and 2 years before onboarding begins, plus identifying golden rituals to teach by first Friday
Includes relationship design conversations, documented management philosophy, and early ownership assignment to accelerate ramp-up to 30
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versiononboarding-new-hiresExecute the skills CLI command in your project's root directory to begin installation:
Fetches onboarding-new-hires from refoundai/lenny-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate onboarding-new-hires. Access via /onboarding-new-hires in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
616
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
616
stars
Help the user onboard new team members effectively using approaches from 14 product leaders.
When the user asks for help with onboarding:
Deb Liu: "The first 90 days are focused on listening and learning first, then doing. Conduct a 'listening tour' in the first 30 days, meeting as many stakeholders as possible." Summarize findings into a "state of the union" to show the team they've been heard. Align on vision in days 30-60, move to full execution by day 90.
Lauren Ipsen: "The 90-day plan is overused but necessary, and that's just the tip of the iceberg. What should this person be doing a year from now? Two years from now?" Define what "crushing it" looks like at each milestone before starting the search.
Heidi Helfand: "Help them feel a sense of belonging by not having their first day be them sitting alone. Have someone be a 'first pair.'" Ensure new hires are not working alone on day one. Assign a buddy to work with them immediately. Encourage sharing personal stories to build connection.
Shishir Mehrotra: "Great companies have a very small list of golden rituals. Every employee knows them by their first Friday." Include core company rituals in the onboarding curriculum. These rituals should be named, known, and templated.
Melissa Tan: "How do I help them secure early wins? I'll suggest 'You should do this presentation - it's a great way to get visibility early.'" Identify low-hanging fruit projects for new hires. Create opportunities for them to present to leadership in their first weeks.
Brandon Chu: "People joining my team already knew how I thought because they'd Google me. It passively onboarded a lot of the PMs." Write about your management and product philosophy. New hires can ramp up before their first day.
Kenneth Berger: "For maybe your first 10-20 employees, have a relationship design conversation when they're hired." Collaboratively figure out the best way to work together given specific roles and personalities. This prevents friction and "out of integrity" behavior later.
Molly Graham: "Do not promise things you can't control. Be honest about the ambiguity and chaos of a scaling environment." Avoid promising stability, specific titles, or career paths you can't guarantee. Overpromises become "letter bombs" that demoralize high performers when they explode.
Timothy Davis: "I want to try and make onboarding 30-45 days by giving them responsibility early. Here's everything we did, here's your responsibilities, go." Use an ops cadence spreadsheet to define task frequency. Assign campaign or project ownership within the first few weeks.
Scott Wu: "New engineers can ask Devin questions about the codebase. It's nice to be able to ask without social pressure." AI tools can help new hires explore internal systems and ask "dumb questions" without feeling judged.
For all 14 insights from 14 guests, see references/guest-insights.md
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
mattpocock/skills
We added onboarding-new-hires from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Registry listing for onboarding-new-hires matched our evaluation — installs cleanly and behaves as described in the markdown.
Keeps context tight: onboarding-new-hires is the kind of skill you can hand to a new teammate without a long onboarding doc.
Keeps context tight: onboarding-new-hires is the kind of skill you can hand to a new teammate without a long onboarding doc.
Registry listing for onboarding-new-hires matched our evaluation — installs cleanly and behaves as described in the markdown.
onboarding-new-hires reduced setup friction for our internal harness; good balance of opinion and flexibility.
onboarding-new-hires is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Solid pick for teams standardizing on skills: onboarding-new-hires is focused, and the summary matches what you get after install.
I recommend onboarding-new-hires for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Useful defaults in onboarding-new-hires — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
showing 1-10 of 42