CtrlK
BlogDocsLog inGet started
Tessl Logo

form-cro

When the user wants to optimize any form that is NOT signup/registration — including lead capture forms, contact forms, demo request forms, application forms, survey forms, or checkout forms. Also use when the user mentions "form optimization," "lead form conversions," "form friction," "form fields," "form completion rate," or "contact form." For signup/registration forms, see signup-flow-cro. For popups containing forms, see popup-cro.

63

Quality

75%

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

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/form-cro/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is a thorough, well-organized CRO reference with concrete guidance, but it is verbose for a single-file skill and offers qualitative heuristics rather than executable artifacts. Splitting dense sections into reference files and tightening redundant prose would improve it.

Suggestions

Move the large 'Experiment Ideas' and 'Form Types: Specific Guidance' sections into separate reference files and keep SKILL.md as a lean overview with one-level-deep links.

Tighten or remove statements Claude already knows (e.g., 'Each field reduces completion rate') and consolidate repeated field-type guidance to reduce token load.

Add an explicit assessment checklist with verification checkpoints (e.g., confirm analytics availability, confirm compliance requirements before recommending field removal) to strengthen workflow clarity.

DimensionReasoningScore

Conciseness

The body is mostly efficient but padded with long enumerations and statements Claude already knows (e.g., 'Each field reduces completion rate'); it could be tightened considerably. Not a 3 because not every token earns its place; not a 1 because it avoids explaining basic concepts.

2 / 3

Actionability

Provides concrete heuristics and good/bad copy examples (e.g., '44px+' tap targets, 'Get My Free Quote'), but guidance is largely qualitative rather than copy-paste executable artifacts. Not a 3 because it lacks fully executable/copy-paste-ready material; not a 1 because it is specific and instructive rather than vague.

2 / 3

Workflow Clarity

The Initial Assessment gives a clear sequenced process (context -> form type -> current state -> business context), but checkpoints are implicit and there are no validation/feedback steps. Not a 3 because no explicit validation checkpoints; not a 1 because a real sequence exists.

2 / 3

Progressive Disclosure

No bundle files exist, so it is a single-file skill with well-organized sections, but at ~420 lines it is a monolithic wall where form-type-specific guidance and experiment ideas could be split out. Not a 3 because it is not a lean overview pointing outward; not a 1 because sections are clear with no nested references.

2 / 3

Total

8

/

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 excellent: it is specific, uses natural trigger terms, answers both what and when, and clearly disambiguates from sibling skills. It follows third-person voice and avoids fluff.

DimensionReasoningScore

Specificity

Lists multiple concrete form types (lead capture, contact, demo, application, survey, checkout) and specific optimization triggers, matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

Explicitly answers both 'what' (optimize non-signup forms) and 'when' via 'When the user wants to optimize...' and 'Also use when the user mentions...' trigger clauses.

3 / 3

Trigger Term Quality

Includes natural phrases users would actually say ('form optimization,' 'lead form conversions,' 'form friction,' 'form fields,' 'form completion rate,' 'contact form') with good coverage of variations.

3 / 3

Distinctiveness Conflict Risk

Explicitly excludes signup/registration and popups and routes them to other skills, giving it a clear niche unlikely to trigger the wrong skill.

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
TheCraigHewitt/seomachine
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.