A pre-launch page has one job: collect email addresses. The usual way it fails is quiet. The design looks fine, the button animates, and a week later you find that the form pointed at a placeholder endpoint and every sign-up went nowhere. Nobody tells you, because the people who hit the error just leave.

We built the agent skill Waitlist Glow around that failure. It produces a one-screen waitlist page, and it will not call the job done until the sign-up has been tried end to end. This tutorial walks through the steps.

What you get

Waitlist Glow makes a single HTML file with no build step to deploy:

  • a soft three-colour gradient glow that slowly breathes behind a large serif headline
  • one email field with a button, a line of proof and a privacy line
  • an optional live countdown to the launch date, which hides itself once the time has passed

The form is real. It posts to the service you choose and works without JavaScript. With JavaScript it shows the result in place: a thank-you line on success, and an error message that keeps the form on screen when the service fails. It has a hidden spam trap and a proper label.

It is one of our 38 free skills, MIT licensed.

Install

Pick whichever route fits your setup:

npx skills add lookbkdev/lookbk-skills --skill waitlist-glow 

Or, in Claude Code, through the plugin marketplace:

/plugin marketplace add lookbkdev/lookbk-skills /plugin install waitlist-glow@lookbk-skills 

You need Node.js 18 or newer and nothing else to install. The checks use Chrome, Chromium or Edge; the scripts look for it, and you can set CHROME_PATH if they can't find it. The page loads its fonts (Fraunces, Manrope and JetBrains Mono by default) from Google Fonts when it is opened, and falls back to system fonts without a connection.

Step 1: decide where sign-ups go

Your agent will ask which service you use, or recommend one. The skill supports four providers:

provider Notes
formspree Create a form there; its ID goes in form. The simplest choice for any host.
netlify Only when the page is deployed on Netlify. Sign-ups appear under the site's Forms tab.
buttondown A Buttondown newsletter. People get its confirmation page and email.
endpoint Anything else that accepts a form post: your own API, or a mailing-list form action such as Mailchimp's.

With ajax (the default for formspree, netlify and endpoint), the page sends the form with JavaScript and shows your success or error text in place. With "ajax": false it is a classic form post and the service's own page takes over, which is the right setting for list services.

If you use your own endpoint with ajax, it must answer with a 2xx status, and if it lives on another domain it must allow the page's origin (CORS). It receives the email field and a website field that real visitors never see. Drop any sign-up where website is filled in. That is the spam trap.

Step 2: write waitlist.json

All content lives in one file. This is the example the skill ships with:

{ "brand": { "name": "soon", "note": "Launching winter 2026" }, "eyebrow": "Private beta", "title": "Something *calm*\nis coming.", "text": "A notes app that breathes with you. Fewer buttons, softer edges.", "form": { "provider": "formspree", "id": "xayzbqwe", "button": "Join the waitlist", "success": "You're on the list. We'll send one email when your invite is ready." }, "proof": "Early invites roll out weekly", "fine": "One email when your invite is ready. No newsletter, no sharing.", "launch": "2026-12-01T17:00:00Z", "links": [{ "label": "Privacy", "href": "/privacy" }], "theme": { "bg": "#0b0b10", "fg": "#f4f5f8", "glow": ["#ffb37a", "#ff7ab6", "#7a9bff"] }, "meta": { "title": "soon: something calm is coming", "description": "A notes app that breathes with you. Join the waitlist for an early invite." } } 

A few things worth knowing about the fields:

  • title takes *word* for an italic word in the accent colour and \n for a line break, up to three lines, 60 characters.
  • launch needs a time with its zone, like 2026-12-01T17:00:00Z. That is what drives the live countdown.
  • proof is a single line beside a row of coloured dots, 48 characters at most. fine is what you will send and how often, 90 characters at most. It is the line people read before typing their address, so keep it honest.
  • theme takes bg, fg and three hex colours for glow, plus optional accent, opacity and font families.
  • meta holds the title and description for search and link previews. It also accepts url, image, icon and lang when you want them.

The copy rules matter as much as the schema. The headline names the feeling or the outcome, not the product category. The proof line and any numbers must be true. If you have no real list size yet, use a fact about the launch, such as invites going out weekly. And if you collect emails, link a privacy policy; your agent will ask you for its URL.

The glow can sit behind any text, so the build works out the brightest the glow gets and derives every text colour from fg and bg so it stays readable. If the glow is too strong for your fg, it is dimmed automatically and the build tells you.

Step 3: build

node <skill>/scripts/build.mjs waitlist.json out 

Here <skill> is the skill's folder. The build lists every problem in waitlist.json at once, then writes out/index.html and prints where the form posts. Read that line. It should be your service, not an example's. This is the cheapest way to catch the placeholder-endpoint mistake from the opening.

Step 4: check it

Three scripts follow the build:

node <skill>/scripts/check.mjs out/index.html node <skill>/scripts/try-form.mjs out/index.html node <skill>/scripts/screenshot.mjs out/index.html 

check.mjs loads the page at 390, 768, 1024 and 1440 px and must say ok at each width. It looks for anything cut off or wider than the screen, readable contrast, a labelled field and exactly one h1.

try-form.mjs is the one that closes the gap from the opening. It fills in test@example.com and submits in headless Chrome, against a stand-in for your service running on your own machine, so nothing reaches the real one. It shows exactly what was sent and what the visitor sees afterwards. For in-place forms it also shows what the visitor sees when the service fails. The run has to end with The form works.

screenshot.mjs saves out/screens/desktop.png and mobile.png. Look at both before you move on.

Step 5: put it live

Upload out/index.html as the site's home page, or at any path, on any static host: Netlify, Vercel, Cloudflare Pages or GitHub Pages. If you chose "provider": "netlify", form detection must be switched on for the site under Forms in the site settings.

Then do the one check a local test cannot do. Sign up once on the live page with your own address and confirm it arrives in the service's dashboard or inbox. Some services send the form owner a confirmation the first time a form is used, so do not be surprised by one.

Troubleshooting

  • build: fix waitlist.json first: each line names the field and what to change.
  • try-form.mjs says nothing was sent: the email field must stay required and the button must stay type="submit". Rebuild instead of editing the HTML by hand.
  • The live form fails but the local test passes: the service rejected the request. For endpoint with ajax, check the CORS settings and that it returns 2xx. For Formspree, check the form's ID and that the form isn't disabled. For Netlify, make sure the site was deployed after the form was added.
  • The page shows system fonts: Google Fonts could not be reached. Install the families locally and set "fonts": "".

Where to go next

The skill folder includes two complete examples, examples/soon/ (dark, Formspree) and examples/loam/ (light, Netlify). The products, IDs and addresses in them are made up, so copy the structure and swap in your own. Source and the rest of the collection are in the repository at https://github.com/lookbkdev/lookbk-skills.

Waitlist Glow is one of 38 free skills from Lookbk, and you can see its previews and details on the Waitlist Glow page at Lookbk.

This post was drafted with AI assistance and checked against the skill's SKILL.md.