CtrlK
BlogDocsLog inGet started
Tessl Logo

multi-step-form-design

Designing forms with multiple steps, progress indicators, conditional logic, and save-and-resume mechanics. The discipline of breaking complex data collection into stages that respect cognitive load while maintaining completion intent. Honest about kitchen-sink-single-page (overwhelms before the user starts), progress-theater (steps without genuine staging), and genuinely-staged (each step earns its own page) patterns. Triggers on multi-step form, multi-page form, form wizard, signup wizard, lead form, application form, intake form, configurator, onboarding form. Also triggers when a long form is converting poorly, when an audience is dropping off mid-form, or when a multi-step form is being scoped for the first time.

68

Quality

83%

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

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

The body is a well-structured, actionable design playbook with excellent progressive disclosure via real one-level-deep reference files and a clear 12-step framework. Its main weakness is conciseness: the keystone framing is repeated across several sections and some prose could be trimmed.

Suggestions

Consolidate the kitchen-sink/progress-theater/genuinely-staged framing to a single canonical section and reference it from the anti-patterns and closing sections rather than restating it.

Tighten the intro and section-openening prose ('The principle.', 'The structure that makes steps coherent.') which currently restate the heading intent.

Add a brief explicit verification/checkpoint note in the 12-considerations framework (e.g., 'confirm each step passes the coherence test before proceeding') to push workflow clarity toward the top anchor.

DimensionReasoningScore

Conciseness

The body is mostly efficient structured guidance, but the kitchen-sink/progress-theater/genuinely-staged framing is restated across the intro, keystone section, anti-patterns, and closing, and some explanatory prose could be tightened, fitting the 'mostly efficient but some unnecessary explanation' anchor rather than the lean 4.

3 / 5

Actionability

Concrete, specific guidance throughout — 'more than 8-10 fields', named step patterns (identity/context/need/detail/confirmation), litmus tests, and per-drop-off-point remediation — giving mostly executable design direction with only minor gaps, appropriate for an instruction-only skill.

4 / 5

Workflow Clarity

The '12 considerations' framework provides a clear ordered sequence for designing/auditing a form, and decision criteria are well-sequenced; no explicit validation checkpoints, but this is a non-destructive design skill so the destructive-operation cap does not apply, landing just below the explicit-validation 5.

4 / 5

Progressive Disclosure

The body is a concise overview with each section closing in a well-signaled one-level-deep reference link, all 9 referenced files exist in references/, and a dedicated Reference files section indexes them, matching the clear-overview-with-one-level-deep-references anchor.

5 / 5

Total

16

/

20

Passed

Description

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

The description is strong: third-person voice, concrete capabilities, comprehensive natural trigger terms, and explicit what/when guidance. It carves a clear, low-conflict niche with concrete trigger phrases for both intent and symptom-based activation.

DimensionReasoningScore

Specificity

Names the domain and lists several concrete sub-capabilities — 'multiple steps, progress indicators, conditional logic, and save-and-resume mechanics' — with only minor coverage gaps, fitting the 'several specific actions' anchor rather than the fully comprehensive 5.

4 / 5

Completeness

Explicitly answers both what ('Designing forms with multiple steps...') and when ('Triggers on... Also triggers when a long form is converting poorly...') with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

'Triggers on multi-step form, multi-page form, form wizard, signup wizard, lead form, application form, intake form, configurator, onboarding form' gives comprehensive coverage of natural terms and synonyms users would actually say.

5 / 5

Distinctiveness Conflict Risk

The multi-step form design niche is clearly carved out with distinct trigger terms and explicit pattern distinctions (kitchen-sink vs progress-theater vs genuinely-staged), minimizing conflict with adjacent skills.

5 / 5

Total

19

/

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.