SKILLEMALL.ai

AB popup-cro

When the user wants to create or optimize popups, modals, overlays, slide-ins, or banners for conversion purposes. Also use when the user mentions "exit intent," "popup conversions," "modal optimization," "lead capture popup," "email popup," "announcement banner," or "overlay." For forms outside of popups, see form-cro. For general page conversion optimization, see page-cro.

alirezarezvani/claude-skills Agent Skills author: alirezarezvani MIT 2 files body ≈ 1 812 tokens Open the sourcegithub.com analyzed 2 d ago

When the user wants to create or optimize popups, modals, overlays, slide-ins, or banners for conversion purposes.

As a process B 66/100 · Nearly there — weak spots: inputs and preconditions, failures and branches, running it twice

GeneratorSales and CRMSecurityWriting and documentstype and topics are labelled automatically from the skill text
JSON
Technical rating
A
97/100
safety, quality, tests
Safety 60%
100
Quality 40%
93
Run on models
none yet
Process rating
B
66/100
Nearly there
Inputs and preconditions w 11
0
Failures and branches w 10
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten

How to improve

    For the model run — optional
    • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
    • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

    Guard findings · 0

    ✓ No critical or high findings

    Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    ✓ No remarks against the Agent Skills spec

    Process rating: all ten parameters 66/100

    • 0Inputs and preconditions. Does not say what the process needs to start
    • 0Failures and branches. Linear process with no failure handling
    • 0Progress reporting. Says nothing while it works
    • 30Running it twice. 2 mutating operations with no state check
    • 60Result and completion. Output format stated, no completion criterion
    • 85Steps. 100 steps, 2 vague phrases
    • 100Tools and files. No external tools needed
    • 100When it triggers. States when to use and when not to
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 1812 tokens
    • low 10 top-level sections: this looks like several domains in one skill

    Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

    Quality signals

    • +4Description does not say when NOT to use the skill (false activations)
    • +4No input/output examples
    • +2Single-language instructions
    • +5Description quotes 7 example trigger phrases
    • +3Description length 377: enough signal without eating the budget
    • +4Structure: 23 headings
    • +3Step-by-step instructions: 100 items
    • +3Output format is stated explicitly
    • +4Reference files are cited in the instructions (1 of 1)
    • +1License stated

    Quality base 70; lint remarks subtract, signals add up to 100. Result: 93.