CtrlK
BlogDocsLog inGet started
Tessl Logo

form-cro

Optimize any form that is NOT signup or account registration — including lead capture, contact, demo request, application, survey, quote, and checkout forms.

57

Quality

66%

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 ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/form-cro/SKILL.md

The canonical home for this skill is form-cro in administrakt0r/AI-Agents-Safe-Coding-Skills

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 content is a comprehensive, well-structured, and actionable form-CRO framework with concrete examples and a diagnostic-first workflow gate. Its main gaps are a monolithic single-file structure with no progressive disclosure and an index methodology that is not fully operationalized into executable scoring criteria.

Suggestions

Operationalize the Form Health & Friction Index: provide concrete scoring criteria (e.g., points deducted per unjustified required field) so Claude can actually compute the 0-30/0-20 sub-scores rather than assign them subjectively.

Split detailed material into one-level-deep reference files (e.g., references/field-optimization.md, references/health-index.md) with clearly signaled links from SKILL.md to improve progressive disclosure for this 440-line skill.

Remove the filler 'When to Use' boilerplate and the duplicate 'Questions to Ask' section (already covered by Phase 1) to tighten conciseness.

DimensionReasoningScore

Conciseness

The body is dense, terse bullet-point guidance with no padding of concepts Claude already knows, but has minor trim opportunities: the role framing ('You are an expert...'), a 'Questions to Ask' section that duplicates Phase 1, and a filler 'When to Use' boilerplate line.

4 / 5

Actionability

Guidance is concrete and specific — numeric thresholds (≥44px touch targets), good/bad error-message examples, CTA copy examples, and field-cost rules — but the Form Health & Friction Index defines categories and weights without a concrete per-field scoring method, leaving 'calculate the index' not fully executable.

4 / 5

Workflow Clarity

Phases are sequenced with a required Phase 0 diagnostic gate and an explicit stop condition ('If verdict is Broken, stop and recommend structural fixes first'), but later guidance is organized topically rather than as a linear numbered workflow and lacks a re-validation loop after fixes.

4 / 5

Progressive Disclosure

The ~440-line skill is well-organized into clear sections but is entirely monolithic with no bundle files and no one-level-deep references, so content that could be split (e.g., field-level guidance, the full index methodology) is inlined.

3 / 5

Total

15

/

20

Passed

Description

61%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 domain-specific and rich in natural form-type triggers, with a strong negative boundary that aids distinctiveness. Its main weakness is the absence of an explicit 'Use when...' clause and reliance on a single action verb, which cap completeness and specificity.

Suggestions

Add an explicit 'Use when...' clause naming concrete trigger phrases (e.g., 'Use when optimizing lead capture, contact, demo request, survey, quote, or checkout form conversion rates').

Expand beyond the single verb 'Optimize' to list 2-3 concrete actions (audit, diagnose friction, recommend field/form changes) to lift specificity.

Include common synonyms such as 'conversion rate', 'form abandonment', and 'form completion' to broaden trigger coverage.

DimensionReasoningScore

Specificity

The description names the domain (non-signup forms) and a single concrete action ("Optimize") plus an enumerated scope of form types, but offers only one action verb rather than several specific actions, matching the 'domain + 1-2 actions' anchor.

3 / 5

Completeness

It gives a clear 'what' (optimize non-signup forms) but no explicit 'Use when...' trigger clause; the negative scope ("NOT signup") only weakly implies 'when', so per the missing-trigger cap it stays at 3.

3 / 5

Trigger Term Quality

It surfaces many natural phrases users say ("lead capture", "contact", "demo request", "application", "survey", "quote", "checkout forms"), but omits common synonyms like "conversion", "abandonment", or "completion", so a few natural terms are missing.

4 / 5

Distinctiveness Conflict Risk

The explicit exclusion of signup/account registration carves a clear niche against a sibling signup-CRO skill, but 'Optimize any form' still risks minor overlap with related page-cro / popup-cro siblings.

4 / 5

Total

14

/

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
administrakt0r/AI-Agents-Safe-Coding-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.