hr-onboarding

A new-hire onboarding plan as a single page — first week schedule, buddy + manager intro, learning track, equipment checklist, and "you're set when…" outcomes. Use when the brief mentions "onboarding", "new hire", "first week plan", or "入职".

Quality

96%

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

100%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.

An exemplary lean, single-purpose skill: concrete panel specs with exact counts, a default rule for ambiguous input, and a copy-paste output contract, with zero token waste and no bundle files to disclose. The only nit is that description-level elements (equipment checklist, learning track) are not restated in the layout spec, which does not diminish the body's actionability.

Dimension	Reasoning	Score
Conciseness	The body (~25 lines) contains zero padding and no explanations of concepts Claude already knows — every line ("Produce a single-screen onboarding plan in HTML.", the panel spec, the output contract) is instructional, matching the score-5 'lean and efficient' anchor.	5 / 5
Actionability	Guidance is fully concrete: an exact panel-by-panel layout spec with counts ("two activities per day", "three concrete outcomes each", "five outcomes with checkboxes"), a default rule ("Default to a 30/60/90-day shape if unspecified"), and a copy-paste artifact output contract — the instruction-only equivalent of the score-5 'fully executable' anchor.	5 / 5
Workflow Clarity	The numbered 1–4 workflow is clearly sequenced with an explicit default for underspecified input; the task (generating an HTML artifact) is neither destructive nor batch, so no validation checkpoint is required, and the single-purpose sequence is unambiguous — score 5 under the simple-skill exception.	5 / 5
Progressive Disclosure	The body is under 50 lines with no bundle files; it is cleanly sectioned (Workflow, Output contract) and its single external reference ("Read the active DESIGN.md") is one level deep and clearly signaled, satisfying the score-5 condition for simple skills with well-organized sections.	5 / 5
	Total	20 / 20 Passed

Description

92%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: it names the concrete deliverable and its components, gives an explicit 'Use when' clause with natural trigger phrases in two languages, and occupies a distinct niche. The only weakness is trigger coverage that misses a few common variations (e.g., "first week", "employee onboarding").

Suggestions

Add common trigger variations such as 'first week', 'employee onboarding', 'new employee', or '30/60/90 plan' to the 'Use when' clause to broaden natural-term coverage.

Mirror the 'equipment checklist' and 'learning track' wording from the description inside the body's layout spec so the promised deliverable and the workflow stay in sync.

Dimension	Reasoning	Score
Specificity	"first week schedule, buddy + manager intro, learning track, equipment checklist, and 'you're set when…' outcomes" enumerates multiple concrete components that comprehensively cover the deliverable, matching the score-5 anchor; no meaningful coverage gap within the skill's scope, so it is not a 4.	5 / 5
Completeness	The description answers 'what' concretely ("A new-hire onboarding plan as a single page — first week schedule…") and 'when' explicitly with concrete trigger phrases ("Use when the brief mentions…"), exactly matching the score-5 anchor; the 'when' clause is explicit, so it is not a 4.	5 / 5
Trigger Term Quality	"Use when the brief mentions 'onboarding', 'new hire', 'first week plan', or '入职'" offers good natural-language coverage including a second-language synonym, but misses common variations such as "first week", "employee onboarding", or "new employee" — the score-4 anchor (a few natural terms missing) rather than 5's comprehensive coverage.	4 / 5
Distinctiveness Conflict Risk	"new-hire onboarding plan" with triggers like "onboarding", "new hire", and "入职" carves out a clear HR niche with distinct triggers and minimal overlap risk with other skills, matching the score-5 anchor.	5 / 5
	Total	19 / 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: nexu-io/open-design
Path: design-templates/hr-onboarding/SKILL.md
Commit: 53231d4

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.