form-strategy

Design forms that convert, validate well, resist spam, and integrate cleanly with downstream systems. Use this skill when designing or auditing any form (contact, signup, checkout, multi-step, embedded), planning validation logic, fighting spam, choosing form tooling, or improving form conversion. Triggers on form design, form validation, form conversion, multi-step form, form spam, captcha, honeypot, form abandonment, signup form, contact form. Also triggers when form completion rates are low or spam is overwhelming.

Quality

87%

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

75%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-organized instruction-only skill with concrete, actionable form guidance, a sequenced workflow with verification, and clean one-level-deep reference splitting. Minor tightening of redundancy and adding executable snippets would push it higher.

Suggestions

De-duplicate the validation-while-typing guidance between Dimension 3 and the Failure patterns section, and trim obvious explanations like 'Placeholder labels disappear when typing' to improve conciseness.

Add a short executable snippet for the layered spam defense (e.g., a honeypot + time-check + Turnstile wiring example) and a validation example to lift actionability.

Make the tune-and-retry feedback loop explicit in the workflow (e.g., after Step 8 monitor, loop back to Step 4 to re-tune spam layers based on observed throughput).

Dimension	Reasoning	Score
Conciseness	Mostly efficient skill-specific decision guidance, but minor redundancy (validation-while-typing appears in both Dimension 3 and Failure patterns) and light over-explanation ('Placeholder labels disappear when typing') keep it just below a 5.	4 / 5
Actionability	Concrete specifics throughout (`autocomplete="email"`, `aria-describedby`, ordered spam-defense layers, per-form-type success metrics), but lacks executable implementation code for the layered defense or validation regexes.	4 / 5
Workflow Clarity	Clear 8-step sequence with explicit verification checkpoints (Step 7 'Test downstream', Step 8 'Monitor'); audit/design focus so the destructive-cap does not apply, though a couple of validation feedback loops are only implicit.	4 / 5
Progressive Disclosure	Good section structure with the detailed field-by-field checklist appropriately split into a real references/form-anatomy-checklist.md, clearly signaled with a one-line description; framework guidance kept inline as overview.	4 / 5
	Total	16 / 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 description: third-person voice, explicit what-and-when structure, and comprehensive natural trigger terms covering synonyms and form types. No over-claims or padding.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions — 'Design forms that convert, validate well, resist spam, and integrate cleanly' — covering the form domain comprehensively, matching the score-5 anchor.	5 / 5
Completeness	Explicitly answers both what ('Design forms that convert, validate well, resist spam, and integrate cleanly') and when ('Use this skill when...', 'Triggers on...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Comprehensive natural-term coverage including synonyms: 'form design, form validation, form conversion, multi-step form, form spam, captcha, honeypot, form abandonment, signup form, contact form' — phrases users would actually say.	5 / 5
Distinctiveness Conflict Risk	Clear form-design niche with distinct triggers (captcha, honeypot, multi-step form) and minimal overlap risk with adjacent web skills.	5 / 5
	Total	20 / 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: rampstackco/claude-skills
Path: skills/form-strategy/SKILL.md
Commit: 3d4510a

Reviewed: 2 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.