Amazon Listing Optimizer

Checks your live listing for suppression triggers first, then rewrites title, bullets and backend terms — using only words Amazon hasn't already indexed.

NewNew8.8 KB snapshotStarter VM
Claude Code logo

What's inside

Harness

Claude Code

Plan

Starter

vCPU

1

Memory

2 GiB

Snapshot

8.8 KB

How it works · ~3 minutes

  1. 01 · Fork

    New isolated microVM on your subdomain — creator state included.

  2. 02 · Your keys

    Log into Claude Code with your own model credentials (BYOK).

  3. 03 · Ask it to work

    Open the terminal and give it a real job. You keep what ships.

30-day money-back on your first purchase · no free trial · keys never leave the VM

About this template

"BEST SELLER — FREE SHIPPING" in the title is a suppression

You paid for a listing rewrite. It came back with promotional language Amazon suppresses for, an eco-friendly claim nobody substantiated, and backend keywords that repeat every word already in your bullets.

A suppressed listing earns nothing. And the backend field — the one genuinely free lever you have — was spent on words Amazon had already indexed.

The compliance pass runs first, on what's already live

Before writing a word, it checks your current listing against the known suppression triggers: promotional language in the title, restricted claims (medical, curative, FDA-adjacent, unsubstantiated "eco-friendly", safety), competitor brand names, contact details or URLs, unsubstantiated superlatives.

A suppression risk already published matters more than a better bullet — and most sellers have never had theirs checked.

Backend keywords: only words that appear nowhere else

Amazon indexes your whole listing, so repeating a word from your title or bullets in the hidden search-terms field buys nothing. Neither does your brand name, your ASIN, commas, or both the plural and singular of one stem.

So terms are generated only from words appearing nowhere else in the listing — and you get the byte count.

Bullets are objection handlers, not feature lists

Five bullets in a fixed order: does it fit / will it last / is it right for me / what's included / what happens if it's wrong. Each led by a capitalised phrase, because buyers scan bullets on mobile.

It won't invent a spec

Missing materials, dimensions, counts or certifications come back as [SPEC NEEDED: what]. On Amazon an invented spec is both a suppression risk and a returns problem.

Every change carries its reason

One line per element on what changed and why. A rewrite you can't evaluate is one you won't ship.

What you supply

Your own Claude Code login, plus your current listing in ~/amzlisting/exports/.

Tell it the category — title limits and restricted claims differ by category, and guessing produces a suppression. Paste your reviews if you have them; the five objections your bullets need to answer are already written there.

No Seller Central connection, which is also why nothing can publish.

Where this stops

It drafts copy to paste. It does not connect to Seller Central, edit a listing, or submit a flat file.

It has no keyword tool, so no search-volume or ranking claims. And the compliance pass flags known triggers — it cannot promise a review outcome.

Verified on build: the skill, the working tree, the NEVER_PUBLISH guard, all five compliance rules, the backend-waste rules and the bullet structure are present on a fresh fork. Running it on your own listing is yours to do.

Inside this fork

Forking copies this template into a brand-new, fully isolated microVM on your own subdomain. Here's exactly what lands in it.

  • Claude Code agent

    The upstream harness, pre-installed — same version the creator ran.

  • Starter VM

    1 vCPU · 2 GiB RAM · 10 GiB disk.

  • Creator's /persist data

    The captured persist volume is copied byte-for-byte into your fork.

  • BYOK — your keys, your VM

    Add your model API keys after forking; they live only inside your microVM.

What this agent can do

1 skill

  • amazon-listing-optimizer

    Rewrite an Amazon title, five bullets and backend search terms from supplied specs — compliance-checked against suppression triggers, with…

What you'll configure after forking

Secrets are scrubbed from shared templates — these are the names you supply in your agent's terminal once it boots.

Environment variables

  • ANTHROPIC_API_KEY

Your turn

Your own Amazon Listing Optimizer, live in about 3 minutes.

Forking copies this Claude Codeagent into a brand-new, fully isolated microVM on your own subdomain — the creator's /persist state and all. Add your own keys after it boots; they never leave the box. Don't love it? Your first jurniti purchase comes with 30 days to get every cent back.

New paid VM · BYOK · 30-day money-back on your first purchase · ~3 min to provision

Starter · fork

$25/ mo

Needs 1 of your own API key