shipped@di-atomic/cro-actions · v0.1.0 · beta

An audit tells you what is broken. It does not tell you what to do.

Cutting a signup form from 11 fields to 4 lifted conversions 120%. Cutting a different one from 9 to 6 dropped them 14%. Both are real, which is why “shorten the form” is not a plan. cro-actions is the middle link of my CRO chain — it turns a ranked finding list into actions concrete enough to start on Monday, and it refuses to emit anything vaguer than that.

For teams sitting on an audit nobody has started — where the list is agreed, the order is not, and the page has looked the same for three weeks.

Chalk diagram headed FROM FINDING TO FIX: a page sketch with two circled findings, a gold arrow leading to three fix cards tagged week one, two and three
Built by Di-Atomic Marketing & compliance agency REACH / CLP vocabulary-aware 7-language team Clients incl. ONYX Radiance, Pamit Group
32action blueprints, each with its own source and measured lift
4scripts that gate every plan before it reaches you
20%hard cap on unverified actions in any one plan
0backends added to your stack
Installopvs-skills install @di-atomic/cro-actions

Then say: “what should I fix first?” or “turn this audit into a plan”.

Why the audit never turns into work

What comes out of the meeting
findings: hero weak, form long,
          pricing confusing

→ "add social proof"
→ "shorten the form"
→ "make the CTA stronger"

(no element named, no target value,
 no evidence, no effort, no order
 — and nothing to start on)

Every line is true of pages in general and unfalsifiable about yours. Nobody can pick one up, and nobody can tell afterwards whether it worked.

What cro-actions will actually emit
element   hero H1
change    match the inbound ad phrase
evidence  +115% form submissions
          (source cited, live URL)
effort    copy / hours
metric    form submissions
owner     copy-engine → SpiderPublish
window    week 1

Seven fields, or it does not ship. An action without evidence and without a named target is not an action — it is a vibe with a ticket number.

A finding is a diagnosis. Somebody still has to write the prescription.

What you actually get

🎯

Every action names a real target

Each fix resolves to one of two shapes: a named component that already exists and can be installed, or a specific content edit handed to the skill that writes it. There is no third category where the plan says “improve” and leaves the rest to you.

📎

Evidence, or an honest flag

Every action carries a source-cited measured lift, or it is explicitly marked unverified best practice. A whole plan is capped at 20% unverified. The same tactic is documented lifting and lowering conversion, so when the evidence does not transfer the recommendation becomes “test it”, not “do it”.

Effort estimates that survive contact

Copy edits live in hours, component installs in days, page rebuilds in weeks, checkout reworks in months. An estimate two bands away from its change type is rejected. Rank by impact over effort and get the effort wrong, and the whole order is wrong.

The two rules that do the most work

Chalk comparison: three crossed-out boxes headed NOT AN ACTION beside a gold-outlined card headed AN ACTION listing element, change, evidence and metric
The lint script rejects empty verbs outright. “Improve the CTA” fails every time — it names no element, no change, and no way to measure whether it worked.
Chalk arithmetic: 12 plus 9 plus 6 equals 27 struck through, with a smaller gold 14 and a tick beneath
Three fixes worth 12%, 9% and 6% do not make 27%. The effects overlap, so projections stay per-action. Under-promising is the difference between a client who trusts the next plan and one who does not.

One finding, start to plan

> "the audit says my hero is weak and the form is too long. what first?"

  recall prior outcomes for this brand + page ...... 1 hit
    → form-shortening lost 14% here in March. do not re-propose blind.

  finding 1  weak hero
    class ....... content edit
    action ...... match hero H1 to the inbound ad phrase
    evidence .... +115% form submissions (cited, live source)
    effort ...... copy / hours
    owner ....... copy-engine → SpiderPublish

  finding 2  long form
    class ....... component install
    action ...... multistep funnel, 11 fields → 4
    evidence .... +120% conversions (cited)   CAVEAT: -14% at 9→6 elsewhere
    effort ...... component / days
    verdict ..... A/B test it, do not ship blind

  gates       evidence 2/2 PASS · effort 2/2 PASS · lint 2/2 PASS
  sequence    week 1: hero copy   week 2: form test   week 3: re-audit
  projected   per-action, not summed

The recall line at the top is the part that pays for itself. A plan that re-proposes a fix which already lost a test on this exact page is worse than no plan.

Where it stops

Chalk ruler with four ticks labelled hours, days, weeks and months, four task cards hanging above, and a gold crossed-out checkout card over the hours tick
It plans, it never builds. The plan is a handoff payload: install here, write the copy there, rebuild that layout, render those assets.
It is guidance-only, with no backend of its own. It will not stack more than a handful of new components on one page, because uplift plateaus and components start competing for the same screen. On a regulated page — REACH, CLP, biocides — it refuses manufactured urgency, invented scarcity, and any social proof not backed by real data. That is not a style preference. It is exposure.
Why this exists

I built this by dogfooding the same stack I run for clients.

cro-actions is one skill in the system behind Di-Atomic — the marketing & compliance agency that runs cognitoAI, SpiderIQ and OPVS. If you want a conversion program that hands your team a prioritized plan instead of a list of adjectives — in any of our seven languages, including regulated categories like REACH and CLP — that’s the day job. Let’s talk.

Book a 30-min call with Di-Atomic

Just want the skill? Get @di-atomic/cro-actions free.