team-onboarding-playbook

Design a structured onboarding experience that gets new team members productive in 30, 60, and 90 days. Use when a new hire is joining, when contractors or agency partners need to ramp up, when an existing team is restructuring and members are switching focus, or when current onboarding feels chaotic and slow. Also triggers when one person owns all the tribal knowledge and you need to capture it, when you keep losing people in their first 90 days, or when a new project has many fresh members joining at once. Useful for engineering, design, product, marketing, and operations roles.

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

88%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, actionable process skill with clear sequencing, milestone checkpoints, and a useful one-level reference. The main weakness is mild redundancy between SKILL.md and the reference file, which also slightly inflates length.

Suggestions

Deduplicate the 30/60/90 milestones and role-specific tasks: keep the framework and one-line summaries in SKILL.md and point to references/onboarding-checklist.md for the full operational detail.

Trim justifying framing sentences (e.g., "Get this right and everything else accelerates") that restate the value of an action rather than instructing it.

Dimension	Reasoning	Score
Conciseness	Efficient and assumes Claude's competence throughout, with a few justifying framing sentences ("contribution is how ramping happens") and some redundancy between the framework layers, the 30/60/90 section, and the role overlay that could be tightened.	4 / 5
Actionability	Highly actionable for an instruction skill: concrete day/week tasks per role, an explicit 7-item Output format, a 9-step Workflow, and a detailed reference checklist with copy-ready review templates.	5 / 5
Workflow Clarity	Clear 9-step sequence with explicit 30/60/90 milestone checkpoints, a feedback loop ("if significantly behind... the plan is wrong, the support is wrong, or the role fit is wrong"), and a retrospective-to-update loop.	5 / 5
Progressive Disclosure	A well-signaled one-level-deep reference link, but the 30/60/90 milestones and role-specific guidance are duplicated between SKILL.md and references/onboarding-checklist.md, so the split is good rather than optimal.	4 / 5
	Total	18 / 20 Passed

Description

86%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description that clearly states what the skill does and provides unusually rich, natural trigger scenarios with good synonym coverage. The main gap is modest overlap with documentation-strategy via the tribal-knowledge capture trigger.

Suggestions

Reword the tribal-knowledge trigger to scope it to onboarding (e.g., "capture a departing teammate's knowledge as part of their onboarding handoff") to reduce overlap with documentation-strategy.

Add one or two more concrete actions (e.g., "build a pre-day-1 checklist, a 30/60/90 milestone plan, and a buddy guide") to lift specificity beyond the current single design action.

Dimension	Reasoning	Score
Specificity	Names the domain and one to two concrete actions ("Design a structured onboarding experience that gets new team members productive in 30, 60, and 90 days"), but does not enumerate a comprehensive set of distinct actions.	3 / 5
Completeness	Explicitly answers both what ("Design a structured onboarding experience...") and when ("Use when a new hire is joining... Also triggers when...") with concrete trigger phrases.	5 / 5
Trigger Term Quality	Comprehensive natural trigger phrases a manager would actually say — "new hire is joining", "contractors or agency partners need to ramp up", "onboarding feels chaotic and slow", "one person owns all the tribal knowledge", "keep losing people in their first 90 days" — with role synonyms (engineering, design, product, marketing, operations).	5 / 5
Distinctiveness Conflict Risk	A clear onboarding niche with distinct triggers, but the "capture tribal knowledge" trigger overlaps with the sibling documentation-strategy skill, creating minor conflict risk.	4 / 5
	Total	17 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: rampstackco/claude-skills
Path: skills/team-onboarding-playbook/SKILL.md
Commit: a67dd34

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.