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.

74

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

85%

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 design playbook with excellent progressive disclosure (real, one-level-deep references) and a clear sequenced framework. The main drag is conciseness: the keystone framing and persona commentary are restated across the intro and closing.

Suggestions

Cut the Closing section's restatement of tutorial-overload / skip-friendly-empty / earned-progressive-disclosure and the design-choice list — they duplicate the intro and keystone section; replace with the single diagnostic question that already closes it.

Remove or compress the meta persona paragraph ("The voice is the senior product marketing director who has watched activation rates double...") — the opinionated tone is already evident in the content and the paragraph carries no actionable guidance.

Condense the four opening paragraphs, which overlap heavily with the frontmatter description, so the body opens directly at the keystone framing instead of re-introducing the skill.

DimensionReasoningScore

Conciseness

It does not explain concepts Claude already knows, but it restates the tutorial-overload / skip-friendly-empty / earned-progressive-disclosure framing three times (intro, keystone section, and closing) and includes a meta persona paragraph ("The voice is the senior product marketing director...") that adds tokens without actionable guidance; this fits mostly-efficient-but-could-be-tightened, not the lean level 3.

2 / 3

Actionability

Concrete and specific throughout — named step patterns (welcome/orientation, critical setup, first-action), skip/resume patterns, drop-off diagnoses with cures, and a 12-consideration framework checklist — which is actionable guidance for an instruction-only skill (absence of code is not penalized here).

3 / 3

Workflow Clarity

The 12-consideration framework is a clearly sequenced design process with embedded checkpoints (the litmus test, the step coherence test) and diagnostic feedback loops in the failure-modes section, matching the clear-sequence-with-validation anchor.

3 / 3

Progressive Disclosure

An overview body pointing to 9 well-signaled one-level-deep reference files — each section ends with "Detail in [references/...]" and a Reference files index lists all — and every referenced file exists with no nested chaining, matching the clear-overview-with-one-level-deep-references anchor.

3 / 3

Total

11

/

12

Passed

Description

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.

A strong description: concrete capabilities, rich natural-language triggers, explicit what-and-when, and a distinct niche. Its only weakness is verbosity — the inline parenthetical pattern definitions pad an already complete description.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities — "Step architecture, progressive disclosure, escape hatches, completion incentives, drop-off measurement" — in third person ("Designing first-run product onboarding wizards..."), matching the multiple-specific-actions anchor rather than the domain-only level 2.

3 / 3

Completeness

Explicitly answers both what ("Designing first-run product onboarding wizards that get users to the ah-ha moment...") and when ("Triggers on..." / "Also triggers when..."), with explicit trigger guidance rather than only implied.

3 / 3

Trigger Term Quality

Natural terms a user would say are well covered — "onboarding wizard, product onboarding, first-run experience, signup flow, activation flow, FRX, time-to-value, ah-ha moment design" — plus situational triggers ("activation rates are low", "users skip onboarding and never return"), beyond the some-keywords level 2.

3 / 3

Distinctiveness Conflict Risk

The post-signup onboarding niche is clear and distinguished from adjacent skills via named patterns (tutorial-overload / skip-friendly-empty / earned-progressive-disclosure), making wrong-skill triggering unlikely.

3 / 3

Total

12

/

12

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.