Claude builds the landing page, and Codex checks every claim before you publish it.
I build ElasticFunnels too, so Overvibe ships with its skill switched on. Ask Claude for a landing page and it builds one with the ef CLI, as files in your folder. A Codex session then reads the page against your product facts and lists every claim it can't find a source for. Once the copy holds up, one ef command publishes it.
Free and open sourceRuns on Mac and LinuxYour own Claude and Codex logins
The ElasticFunnels skill ships with Overvibe, switched on. One switch turns it off.
The page looks finished. Is every claim on it true?
A model writing sales copy reaches for the strongest line it can find, and sometimes that line promises something your product never did. On a live page that turns into refunds, chargebacks or a rejected ad, and the model that wrote the line is the least likely to question it.
One agent writes and publishes
Claims nobody checked against the product
Copy pasted from a chat into a page builder
The writer proofreads its own page
Publishing left as a job for later
A writer and a checker in Overvibe
Codex checks each claim against your facts file
The page is files in your folder, built with ef
A second model reads the copy cold
A draft first, published when you say so
From the brief to a live page
You type
❯Build a landing page for the offer in brief.md on ElasticFunnels, have Codex check every claim against facts.md, and show me before you publish.
1Claude links the folder
ef init connects it to your ElasticFunnels brand. You sign in once, in the browser.
2It builds the page
Headline, sections, the offer and the button, as .ef files. ef lint checks the markup.
3Codex checks the claims
Each promise on the page against facts.md. The ones without a source come back as a list.
4You say publish
Claude fixes or drops the flagged lines, saves a draft, and publishes it once you've looked.
Behind it, ef and one checker. Claude knows the ef commands from the ElasticFunnels skill. The checker is a normal overvibe new. Read the CLI reference
$ ef init# links the folder to your ElasticFunnels brand (you sign in once, in the browser)$ overvibe new --attach --tool codex --cwd . --name "offer: claims check" \
--prompt "Check every claim in elasticfunnels/pages/offer.ef against facts.md. List the ones with no source. Do not edit. When done, run: overvibe send \"$OVERVIBE_SESSION\" \"<claims>\""
$ ef push elasticfunnels/pages/offer.ef --draft
One agent can do it alone when
the page is a plain opt-in or a thank-you page with nothing to prove. Bring in the checker for sales pages, advertorials and anything that promises a result. For long copy, the copywriting page shows Claude and Codex arguing a draft into shape.
Questions
Do I need an ElasticFunnels account?
To publish there, yes. You sign up at elasticfunnels.io and sign in once with ef init. If you'd rather build on another stack, the agents follow you.
Can I switch the skill off?
Yes. Settings > Skills has one switch for it, and the setup asks on its Shared skills step. Off removes its links from Claude Code, Codex and agy.
Will Claude publish without asking?
Ask it to show you first, like the prompt above. ef push --draft saves a draft you can look at before anything goes live.
