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

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.

The content is a well-structured, actionable CRO playbook with a phased workflow and a validation gate, though it runs long with some redundancy and reference-style sections that are not strictly sequenced. Tightening duplicate sections would improve token efficiency.

Suggestions

Merge or trim the 'Questions to Ask' section, which duplicates Phase 1 context items, to reduce redundancy and length.

Replace the generic 'When to Use' placeholder line with concrete applicability guidance or remove it.

Consider splitting the detailed Friction Index scoring rubric or field-level reference into a references file so SKILL.md reads as a lean overview with one-level-deep pointers.

DimensionReasoningScore

Conciseness

The body is mostly lean bullets with little concept over-explanation, but at ~440 lines it carries redundancy ('Questions to Ask' duplicates Phase 1 context), truisms, and a generic placeholder 'When to Use' line that could be tightened.

3 / 5

Actionability

Concrete, executable specifics throughout (≥44px touch targets, field-count completion heuristics, named CTA examples, a fully worked error-message example), with only minor gaps keeping it just below fully copy-paste-ready.

4 / 5

Workflow Clarity

A clear phased sequence (Phase 0 index → Broken stop-checkpoint → Phase 1 context → output) with an explicit validation gate; not a destructive/batch operation so no cap applies, but downstream sections read more as reference than a sequenced workflow.

4 / 5

Progressive Disclosure

Single self-contained file with no bundle files present, organized under clear section headers and free of nested-reference anti-patterns; good structure with minor organization gaps rather than a clean overview-plus-references split.

4 / 5

Total

15

/

20

Passed

Description

65%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 distinctive and uses natural trigger terms, but it lacks an explicit 'Use when...' clause and relies on a single action verb, leaving completeness and specificity at mid-level. Adding an explicit trigger clause would lift the capped completeness score.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when optimizing lead capture, contact, demo request, application, survey, quote, or checkout forms' to satisfy the completeness 'when' requirement.

Expand the single 'Optimize' verb into two or three concrete actions (e.g. 'audit, score, and restructure') to raise specificity.

Include common synonyms such as 'contact form' and 'survey form' to round out trigger-term coverage.

DimensionReasoningScore

Specificity

Names the domain ('form optimization') and a single concrete action ('Optimize') alongside an enumerated list of seven specific form types, matching the anchor for naming a domain with 1-2 concrete actions rather than several distinct actions.

3 / 5

Completeness

Has a clear 'what' (optimize non-signup forms) but no explicit 'Use when...' trigger clause; the 'when' is only weakly implied via the enumeration, so per the judging guideline completeness is capped at 3.

3 / 5

Trigger Term Quality

Includes natural terms users would say ('lead capture', 'contact', 'demo request', 'checkout forms') with good coverage, but is missing common synonyms like 'contact form' or 'survey form' that would push it to a 5.

4 / 5

Distinctiveness Conflict Risk

The explicit exclusion ('NOT signup or account registration') carves a clear niche with distinct triggers and minimal conflict risk against adjacent CRO skills, matching the top anchor.

5 / 5

Total

15

/

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.