DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to diagnose ACOS problems in an Amazon ad account with Sealeap Amazon Skills

Run the ACOS diagnostics Skill to find whether ACOS comes from clicks, conversion, traffic mix, or profit.

Who it is forAn Amazon advertiser whose ACOS rose and who needs to know which part of the ad funnel to check first.

The problemHigh ACOS has several possible causes, and it is slow to check each one by hand.

The outcomeA diagnosis that separates click cost, conversion, traffic structure, and profit structure, with listed data gaps and optimization options to verify.

What you need first

  • Git installed, to clone the repo
  • An AI agent that can read a SKILL.md file or load a Skill folder from a Skills directory
  • The Amazon account or ad data the chosen Skill lists as required input (see its SKILL.md)
  • Ability to read Chinese, since most Skill content is in Chinese

Steps

  1. Run git clone https://github.com/xjli360/sealeap-amazon-skills.git
  2. Run cd sealeap-amazon-skills
  3. Open amazon-skills/amazon-official/sealeap-amazon-acos-diagnostics/ and read its SKILL.md
  4. Copy that Skill folder into your agent's Skills directory, keeping its references/, agents/, and scripts/ folders
  5. Give the agent the marketplace, the time range, and the goal, then ask it to list the data it needs first

Prompt for your agent

Using the sealeap-amazon-skills repo, run sealeap-amazon-acos-diagnostics for <marketplace> over <time range>, with the goal of finding whether ACOS comes from click cost, conversion, traffic structure, or profit structure. Expect a list of required data, a diagnosis, the evidence gaps, and verifiable optimization options. Check that every conclusion names the data it used and marks missing data as unknown.

Caveat. The README says course examples and past experience must be rechecked against the current account, marketplace, and official Amazon rules before acting on them.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page