Agent skill · Design & Presentation

onboarding-buddy-plan

Design the buddy system that makes new-hire onboarding human — the buddy's actual job (context and safety, not training), the 30-day touchpoint plan, the ask-me-anything contract, and the buddy selection that avoids the two classic miscasts. Use when asked set up an onboarding buddy program, I'm buddying the new hire what do I do, our onboarding is docs with no humans, or the new person is drowning quietly. Produces the buddy role definition, the touchpoint schedule, the first-week script, and the escalation line.

mohitagw15856github.com/mohitagw15856GitHub ↗
claude-codecursorMIT
Install
npx skills add mohitagw15856/pm-claude-skills --skill onboarding-buddy-plan --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 6 KB
Bundled scripts: none
Path: skills/onboarding-buddy-plan/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 1,255
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Onboarding Buddy Plan Skill Onboarding docs answer the documented questions; the buddy exists for the *undocumented* ones — "who actually decides this," "is it normal that nobody replied," "can I ask the VP directly or is that weird" — the questions new hires won't ask their manager because every one feels like an admission. The buddy's job is context and psychological safety, explicitly *not* training (that's the manager's and the docs' job — miscasting the buddy as trainer burns them out and confuses accountability). The plan makes the role concrete: selection, the touchpoint arc, the safety contract, and the line where buddy concerns route onward. ## What This Skill Produces - **The role definition** — what the buddy owns (context, norms, safety-net), what they don't (tasks, evaluation, training) - **The touchpoint arc** — day 1, daily-ish week one, weekly to day 30, with each conversation's actual purpose - **The first-week script** — the walkthroughs that matter: the unwritten norms, the who's-who, the [working-agreements](../working-agreements/SKILL.md) tour - **The escalation line** — what the buddy notices and where it goes (struggling ≠ snitching; the line is drawn caref

What's inside
Steps it walks through
  1. What This Skill Produces
  2. Required Inputs
  3. Framework: The Plan Rules
  4. Output Format
  5. The Role Split
  6. The Arc
  7. First-Week Curriculum
  8. The Safety Contract + Escalation Line
  9. Quality Checks
  10. Anti-Patterns
More from pm-claude-skills
All skills →
About this skill
What does the onboarding-buddy-plan skill do?

Design the buddy system that makes new-hire onboarding human — the buddy's actual job (context and safety, not training), the 30-day touchpoint plan, the ask-me-anything contract, and the buddy selection that avoids the two classic miscasts. Use when asked set up an onboarding buddy program, I'm buddying the new hire what do I do, our onboarding is docs with no humans, or the new person is drowning quietly. Produces the buddy role definition, the touchpoint schedule, the first-week script, and the escalation line.

How do I install it?

Run `npx skills add mohitagw15856/pm-claude-skills --skill onboarding-buddy-plan --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going