Amazon PPC Analyst

Finds the Sponsored Products spend that never converted, then drafts harvest, negate and bid-down changes with the arithmetic shown. Never changes bids.

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

The first line is one number: what you spent on terms that never converted

Four thousand rows in a search-term report, and somewhere in there is the spend going nowhere. Finding it means a pivot table and an afternoon — so instead most sellers change a few bids by feel.

Most PPC advice is noise fitted to four clicks. This one refuses to give you any.

The 10-click floor

A keyword needs at least 10 clicks before its ACOS means anything, and a bid change needs 14 days in the window. Below either, the verdict is WAIT with the reason stated — not a bid.

That single rule is the difference between analysis and confident nonsense.

Four verdicts, one per search term

  • HARVEST — converting at or under target ACOS in an auto/broad campaign. Move it to exact match at its current CPC.
  • NEGATE — spend with zero orders past the click floor. Negative-exact it in the campaign that actually spent the money.
  • BID DOWN — converting but above target. Gets a computed bid, not a flat 10% haircut.
  • WAIT — under the floor or the window. Which one is named.

The arithmetic is shown

proposed = current_bid × (target_acos ÷ actual_acos), rounded to the cent, with the inputs printed. A proposed bid you can't check is a guess, so every one comes with its multiplication. If a column it needs is missing from your export, it says so rather than estimating.

What you supply

Your own Claude Code login — and a report export. No Amazon API key.

Seller Central → Advertising → Reports → Search Term Report, drop the CSV into ~/ppc/exports/, and fill in your target ACOS in the rules file. Leave it blank and every verdict is WAIT, deliberately: without a target there's nothing to compare against.

The guard is a file, not a promise

~/ppc/policy/PPC-RULES.md carries NEVER_AUTOBID, the click floor, the four verdicts and the bid math. The skill reads it before every run. It's also where you override the floor if your volume justifies it — edit the file, not the prompt.

The export-as-input design is itself the guarantee: there's no Seller Central connection to misuse.

Where this stops

It reads exports and drafts change lists. It does not connect to Seller Central, change bids, or pause campaigns.

It won't claim organic rank impact — you can't see that in an ad export — and it won't call ACOS profit, because it doesn't know your unit economics.

Verified on build: the skill, the working tree, the NEVER_AUTOBID guard, the click floor and the bid arithmetic are present on a fresh fork. Running it on your own report 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-ppc-analyst

    Analyze an Amazon Ads search-term or campaign report, find wasted spend, and draft harvest / negate / bid-down changes with the arithmetic…

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 PPC Analyst, 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