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

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

100%

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: lean body, concrete role-specific guidance, an explicit sequenced workflow with checkpoints and a feedback loop, and clean one-level-deep reference offloading. No significant weaknesses.

Dimension	Reasoning	Score
Conciseness	The body is lean for a process framework: it assumes Claude's competence, never explains basic concepts, and every section adds specific guidance, with only a few short editorial lines that still carry judgment rather than filler.	3 / 3
Actionability	Guidance is concrete and specific throughout, from day-level role overlays ('Day 1: dev environment running, first commit') to a defined set of seven output deliverables, giving copy-ready actionable instruction without needing code.	3 / 3
Workflow Clarity	A numbered 9-step Workflow is clearly sequenced with explicit checkpoints (formal 30/60/90 check-ins) and a feedback loop (90-day retrospective feeding back into playbook updates), plus corrective guidance for laggards.	3 / 3
Progressive Disclosure	SKILL.md is a well-sectioned overview and offloads the detailed day-by-day checklist to a single, clearly signaled, one-level-deep reference (references/onboarding-checklist.md) that exists and is appropriately split from the main body.	3 / 3
	Total	12 / 12 Passed

Description

90%

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, third-person description with explicit and varied triggers plus a clear what/when structure. Its only weakness is specificity: it states one overarching action rather than enumerating several concrete deliverable-level actions.

Suggestions

List the concrete artifacts the skill produces (e.g. 'builds pre-day-1 checklists, day-1 schedules, and 30/60/90 milestone plans') to lift specificity from a single conceptual action to multiple specific actions.

Tighten the trigger list slightly to avoid near-duplicate scenarios ('new project has many fresh members joining at once' overlaps with 'team is growing fast') which adds length without adding distinct triggers.

Dimension	Reasoning	Score
Specificity	It names the domain and a main action ('Design a structured onboarding experience that gets new team members productive in 30, 60, and 90 days') but offers a single conceptual action rather than a list of multiple distinct concrete actions as required for a 3.	2 / 3
Completeness	It explicitly answers both what ('Design a structured onboarding experience...') and when with explicit 'Use when...' and 'Also triggers when...' clauses, satisfying both halves.	3 / 3
Trigger Term Quality	It covers many natural trigger phrases a manager would actually say ('new hire is joining', 'contractors or agency partners need to ramp up', 'current onboarding feels chaotic and slow', 'keep losing people in their first 90 days').	3 / 3
Distinctiveness Conflict Risk	Onboarding is a clear niche with distinct triggers (new-hire ramp, tribal-knowledge capture, first-90-day attrition) that are unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 12 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
Commit: f1bc195

Reviewed: 12 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.