onboard
Designs and improves onboarding flows, empty states, and first-run experiences to help users reach value quickly. Use when the user mentions onboarding, first-time users, empty states, activation, getting started, or new user flows.
73
67%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.claude/skills/onboard/SKILL.mdQuality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-crafted skill description that follows best practices closely. It uses third person voice, lists specific concrete capabilities, includes a comprehensive 'Use when...' clause with natural trigger terms, and occupies a clearly distinct niche. It closely mirrors the good examples provided in the rubric.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Designs and improves onboarding flows, empty states, and first-run experiences' with a clear outcome 'help users reach value quickly'. These are concrete, domain-specific capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (designs and improves onboarding flows, empty states, first-run experiences) and 'when' with an explicit 'Use when...' clause listing specific trigger scenarios. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'onboarding', 'first-time users', 'empty states', 'activation', 'getting started', 'new user flows'. These are all terms a user would naturally use when seeking help with this topic. | 3 / 3 |
Distinctiveness Conflict Risk | Occupies a clear niche around onboarding and first-run UX design. The trigger terms like 'empty states', 'activation', 'first-time users', and 'new user flows' are distinct and unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
35%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill reads more like a comprehensive UX design guide than a focused, actionable skill for Claude. It's heavily padded with design principles and philosophy that Claude already understands, while lacking concrete, executable implementation patterns. The content would benefit significantly from aggressive trimming of general UX advice and splitting detailed subsections into referenced files.
Suggestions
Cut the 'Onboarding Principles' section to 3-4 bullet points max — Claude already knows UX fundamentals like 'show don't tell' and 'respect user intelligence'.
Move detailed subsections (Empty State Design, Guided Tours, Interactive Tutorials, Documentation & Help) into separate referenced files to reduce the main skill to an actionable overview.
Replace descriptive guidance with concrete, executable examples — e.g., provide actual React/HTML component templates for empty states, tooltip implementations, and welcome screens instead of describing what they should contain.
Add explicit decision-tree workflow: 'If building initial onboarding → follow steps A-D; if designing empty states → follow steps E-G' with validation checkpoints between steps.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~200+ lines, with significant content Claude already knows (UX design principles, what empty states are, general advice like 'be concise and clear'). Sections like 'Respect User Intelligence' and 'Show, Don't Tell' are standard UX knowledge that doesn't need explanation. The 'Onboarding Principles' section largely restates common design wisdom. | 1 / 3 |
Actionability | The skill provides some concrete patterns (empty state example markup, localStorage code snippet, library recommendations) but is mostly descriptive guidance rather than executable instructions. Most content reads as design philosophy and checklists rather than specific, copy-paste-ready implementations or concrete design specifications. | 2 / 3 |
Workflow Clarity | There is a general sequence (assess needs → design → implement → verify) but the steps are loosely connected. The 'Verify Onboarding Quality' section lists metrics but lacks explicit validation checkpoints or feedback loops for iterating on the design. The mandatory preparation step references external skills but the overall workflow lacks clear decision points. | 2 / 3 |
Progressive Disclosure | The skill references external skills (/frontend-design, /teach-impeccable) which is good, but the main body is a monolithic wall of content that could benefit from splitting detailed sections (empty state design, implementation patterns, guided tours) into separate reference files. The structure has headers but everything is inline. | 2 / 3 |
Total | 7 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- pbakaus/impeccable
- Commit
3a4fc70
- Reviewed
Table of Contents
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.