CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

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.

The content is highly actionable, clearly sequenced with verification checkpoints and a feedback loop, and well-structured with a properly signaled one-level-deep reference. The main weakness is conciseness: guidance is repeated across the framework, workflow, and failure-patterns sections, and some editorial prose could be trimmed.

Suggestions

Reduce cross-section redundancy: validation appears in Dimension 3, Step 5, and Failure patterns, and spam defense in Dimension 4, Step 4, and Failure patterns — consolidate each topic to one canonical treatment and cross-reference rather than restate.

Trim non-actionable editorial prose such as the opener 'Forms are where intent becomes action. Design them well or lose conversions, frustrate users, and drown in spam.' which adds tokens without executable guidance.

Move the detailed per-field-type examples (password, email, phone, date, address) and the full spam-defense layer list into the existing reference checklist to slim the main body while preserving the guidance.

DimensionReasoningScore

Conciseness

The body is mostly efficient and does not explain concepts Claude already knows (no 'what is a form' padding), but content is repeated across the 5-dimension framework, the 8-step workflow, and the failure-patterns section (e.g., validation appears in Dimension 3, Step 5, and Failure patterns), and editorial prose like 'Forms are where intent becomes action' earns little. Not a 1 because it never explains basics; not a 3 because not every token earns its place given the redundancy.

2 / 3

Actionability

Highly concrete, actionable guidance for an instruction-only skill: specific attribute values (autocomplete='email', type='tel'), explicit timing rules ('Validate on blur, not on every keystroke', 'Reject submissions completed in under 2-3 seconds'), and named tools (hCaptcha, reCAPTCHA v3, Turnstile) — copy-paste-ready specifics rather than vague direction.

3 / 3

Workflow Clarity

A clearly sequenced 8-step workflow with explicit verification checkpoints (Step 6 'Verify accessibility', Step 7 'Test downstream' with verify bullets, Step 8 'Monitor') and a feedback loop ('After launch, monitor. Tune layers based on what's actually getting through'), plus a supporting checklist in the reference file. Form auditing is not a destructive/batch operation, so the validation-cap rule does not apply.

3 / 3

Progressive Disclosure

SKILL.md is a well-organized overview (When to use / NOT to use, Required inputs, framework, workflow, failure patterns, output format) that points via a clearly signaled, one-level-deep link — '[references/form-anatomy-checklist.md]: A field-by-field... checklist' — to the verified existing reference file, keeping the detailed checklist out of the main body.

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.

The description is strong across all four dimensions: it uses third-person voice, lists concrete actions, provides explicit 'Use when' and 'Triggers on' guidance, and carves out a distinct forms niche with natural keyword coverage.

DimensionReasoningScore

Specificity

Lists multiple concrete actions such as 'Design forms that convert, validate well, resist spam, and integrate cleanly' plus 'designing or auditing any form..., planning validation logic, fighting spam, choosing form tooling, or improving form conversion' — a comprehensive, specific action set, not just a named domain.

3 / 3

Completeness

Explicitly answers both what ('Design forms that convert, validate well, resist spam, and integrate cleanly...') and when ('Use this skill when designing or auditing any form...' plus the explicit 'Triggers on...' clause), satisfying the maximum-completeness anchor.

3 / 3

Trigger Term Quality

Strong natural-term coverage via 'Triggers on form design, form validation, form conversion, multi-step form, form spam, captcha, honeypot, form abandonment, signup form, contact form' — these are exactly the phrases a user would say, including common variations like 'signup form' and 'captcha'.

3 / 3

Distinctiveness Conflict Risk

A clear, narrow forms niche with form-specific triggers (captcha, honeypot, form abandonment, multi-step form); the body further disambiguates against sibling skills (cro-optimization, landing-page-copy, accessibility-audit), 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.