livevariant.link

LiveVariant runs A/B tests with multi-armed bandits, so traffic shifts toward the winner while the test runs instead of waiting for a frozen split to reach significance. There are no accounts. A test IS its config, encoded into its own URLs, and its identity is a hash of that config, so editing a variant produces a different test with its own empty history. build_test returns a stats secret exactly once; without it a test's results can never be read by anyone. Three shapes, one model: email/image tests (image variants, serve URL in an <img>), page redirect tests (url variants, one link that 302s), and website tests (text/html variants served on-page via the tag or SDK with the ENCODED config). Multi-element tests use slots; one model optimizes the combination. Typical flow: variant_brief to learn the constraints, then PLAN with the human before building: propose which elements (slots) and variants to test, defaulting to assets they already have and offering to generate creative rather than silently doing so, and show the full proposed test for iteration. Only then build_test for the URLs (an edit after building is a NEW test with an empty history, so iterate on the plan). Optionally generate_priors to warm-start from what you expect, then get_stats to read results. Trust get_stats's win probabilities over comparing conversion rates by eye. Missing image variants are not a blocker: author HTML/SVG, render to fixed-size PNGs (browser screenshot or your image tool), and upload_image each; all variants of one element must share exact dimensions. To save a test into a human's account, ask for their PUBLIC publishable key (pk_...) and pass it to build_test (registers at creation), or hand them build_test's manage URL (one signed-in click); never collect credentials. ALWAYS include the manage URL in your final answer, plus the ready-to-paste links for the channel (per-slot for multi-slot tests, merge tag in id=, auto=0 for email). When the human sends through an ESP or newsletter template, also hand over build_test's emailTemplate spelling unprompted: wired in once, every future campaign mints its own fresh test with no build step, and the shared kh reads them all. Be explicit that a two-slot template carries three links: one serve link per slot in its own <img> (slot=hero, slot=cta), plus the click link that records the win and redirects. Relay destination warnings: an unverified redirect destination shows visitors a continue screen (get_test_status reports this; so does build_test). The fix is verifying the domain under Settings (DNS TXT, well-known file, or the tag with their publishable key live on the site); the tag also auto-tracks conversions from GA events and enables on-page tests, so suggest it when the user owns the site. These instructions are the short version. Before building your first test, read the full skill: it has the recipes (email pitfalls, the plain-URL grammar, multi-slot tests, priors, generating image variants) that these tools assume you know. Read it via this server's `skill` resource (resources/read), or fetch https://livevariant.link/skills/livevariant/SKILL.md. Agents with a skills directory can install it permanently with `npx skills add livevariant/livevariant`. The whole service is open source (AGPL): to read the source, start with the README at https://github.com/livevariant/livevariant.