CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

84%

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

67%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, highly actionable strategy skill with a clear 5-dimension framework, an 8-step workflow with verification and monitoring, and a properly signaled one-level-deep reference. The main weaknesses are redundancy between the framework, workflow, and failure-pattern sections, and a few spam-defense items that stay directional rather than concrete.

Suggestions

Consolidate redundancy: the Failure patterns section restates guidance from the 5 dimensions and Workflow Steps 3-5 (e.g., keystroke validation, captcha-as-only-defense, state-on-refresh); merge these into a single statement per point or cut the duplicated list.

Add concrete specifics to the directional spam-defense items: give example thresholds for rate limiting (e.g., N submissions per IP per hour) and name implementable behavioral-signal options, matching the concreteness of the honeypot and time-based items.

Move some inline detail — particularly the failure-pattern catalog and per-field design detail — into the existing references/ file (or a second reference) to shrink the body and strengthen the overview role of SKILL.md.

DimensionReasoningScore

Conciseness

The prose is punchy and free of conceptual padding, but there is noticeable redundancy across sections: the Failure patterns repeat guidance already given in the 5 dimensions ("Validation that fires while typing" restates Dimension 3; "Captcha as the only spam defense" restates Dimension 4; "Forms that lose state on refresh" restates Dimension 5), and the Workflow's Steps 3-5 restate the framework. Mostly efficient but could be tightened to fit anchor 3 rather than 4; not verbose enough for 2.

3 / 5

Actionability

Concrete and specific throughout: "Validate on blur, not on every keystroke", "Reject submissions completed in under 2-3 seconds", `autocomplete="email"`, `tel`, `date`, ordered spam layers with a default recipe ("honeypot + time check + Turnstile"). As an instruction-only skill this is mostly executable guidance, but some items remain directional ("Behavioral signals. Did the cursor move?" and "Rate limiting" give no thresholds or implementation specifics), leaving minor gaps that keep it below a 5.

4 / 5

Workflow Clarity

The 8-step workflow is clearly sequenced (audit → define success → cut fields → defenses → validation → accessibility → test → monitor) with explicit verification in Step 7 ("Submit the form. Verify: Data lands where it should... Spam defenses are working") and a monitor/tune loop in Step 8. Not a 5 because the validation steps lack feedback-loop detail — there is no explicit fix-and-re-test cycle, only "Test after any integration update".

4 / 5

Progressive Disclosure

The single reference (`references/form-anatomy-checklist.md`) is well signaled at the end of the body with a clear description, is one level deep, and exists in the bundle. However, the ~250-line body still inlines a substantial amount of detail (full dimension guidance plus a 15-item failure-pattern catalog) that could partly live in references, which is a minor organization gap consistent with anchor 4 rather than 5.

4 / 5

Total

15

/

20

Passed

Description

96%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 that explicitly answers both what and when, with dense, concrete capability statements and a comprehensive set of natural trigger terms. The only weakness is minor overlap risk with adjacent CRO/frontend skills on conversion-related triggers.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions: "Design forms that convert, validate well, resist spam, and integrate cleanly with downstream systems", plus "designing or auditing any form (contact, signup, checkout, multi-step, embedded), planning validation logic, fighting spam, choosing form tooling, or improving form conversion" — comprehensive coverage of the skill's capabilities.

5 / 5

Completeness

Both questions are explicitly answered: the opening sentence states what the skill does ("Design forms that convert, validate well, resist spam, and integrate cleanly") and "Use this skill when designing or auditing any form..." explicitly states when, with concrete trigger phrases.

5 / 5

Trigger Term Quality

Ten natural trigger terms including synonyms and variations ("form design", "form validation", "multi-step form", "captcha", "honeypot", "form abandonment", "signup form", "contact form") plus situational triggers ("form completion rates are low or spam is overwhelming") that users would naturally say.

5 / 5

Distinctiveness Conflict Risk

Form design/validation/spam is a clear niche with distinct triggers (honeypot, captcha, form abandonment), but "improving form conversion" and "choosing form tooling" carry minor overlap risk with closely related CRO and frontend-build skills. Not a 5 because the description alone doesn't fully disambiguate from those adjacent skills.

4 / 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.

Validation — 15 / 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

Path

skills/form-strategy/SKILL.md

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.