CtrlK
BlogDocsLog inGet started
Tessl Logo

onboarding-wizard-design

Designing first-run product onboarding wizards that get users to the ah-ha moment without overwhelming them. Step architecture, progressive disclosure, escape hatches, completion incentives, drop-off measurement. Honest about tutorial-overload (dump everything upfront), skip-friendly-empty (skipped onboarding leads to abandoned product), and earned-progressive-disclosure (right things at the right moments) patterns. Triggers on onboarding wizard, product onboarding, first-run experience, signup flow, activation flow, FRX, time-to-value, ah-ha moment design. Also triggers when activation rates are low, when users skip onboarding and never return, when onboarding flows are being scoped for the first time, or when audience research shows users not finding key features.

72

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

78%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, opinionated playbook: it keeps the body as a navigable overview, splits detail into clearly signaled one-level-deep reference files, and supplies a concrete 12-consideration framework with named patterns. It is slightly long and repeats its keystone framing across sections, which keeps conciseness at 4 rather than 5.

Suggestions

Trim the closing 'Closing: wizards earn the user's first session' section and the repeated tutorial-overload/skip-friendly-empty framing in the intro, since the keystone distinction is already stated verbatim in its own section.

Add one explicit validate-and-iterate checkpoint to the 12-consideration framework (e.g., 're-run the litmus test after changes') to give the audit workflow a fix-and-retry feedback loop.

Move the 'voice is the senior product marketing director' paragraph out of the load-bearing body or compress it; it describes persona rather than actionable design guidance.

DimensionReasoningScore

Conciseness

Mostly lean and assumes Claude's competence (no beginner definitions of what an onboarding wizard is), but the 'voice' framing, repeated keystone reframing across sections, and closing recap add some padding that could be trimmed.

4 / 5

Actionability

Provides concrete actionable structure (the 12-consideration framework, named step patterns, skip/resume patterns, drop-off remediations tied to specific failure signatures) with minor gaps where guidance stays at the principle level rather than fully specified execution.

4 / 5

Workflow Clarity

The 12-consideration framework gives a clear sequenced audit checklist with a coherence/litmus test validation step, though it is a decision/audit workflow without explicit fix-and-retry feedback loops, leaving minor validation gaps.

4 / 5

Progressive Disclosure

Clear overview body with well-signaled one-level-deep references to nine real reference files (e.g. 'Detail in [`references/wizard-decision-criteria.md`](...)'), content appropriately split, and an explicit Reference files index for easy navigation.

5 / 5

Total

17

/

20

Passed

Description

100%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, comprehensive description: it states concrete capabilities, includes a rich set of natural trigger terms plus situational triggers, and explicitly separates what the skill does from when to use it. Distinctiveness is high because it targets a specific onboarding phase and lists distinguishing anti-patterns.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities ('Step architecture, progressive disclosure, escape hatches, completion incentives, drop-off measurement') and names three named anti-patterns, giving comprehensive coverage of what the skill does.

5 / 5

Completeness

Explicitly answers both what (the capability list) and when via a dedicated 'Triggers on...' clause plus 'Also triggers when...' situational conditions, with concrete trigger phrases.

5 / 5

Trigger Term Quality

Comprehensive natural-keyword coverage including synonyms and abbreviations ('onboarding wizard, product onboarding, first-run experience, signup flow, activation flow, FRX, time-to-value, ah-ha moment design') plus situational triggers users would voice.

5 / 5

Distinctiveness Conflict Risk

Narrow niche (first-run product onboarding wizards) with specific triggers that distinguish it from generic onboarding, tours, and forms, keeping conflict risk minimal.

5 / 5

Total

20

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
rampstackco/claude-skills
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.