amazon-listing-optimizer
Skill1 starsChanged 39 days agoMITView on GitHub
Writes an Amazon product title, five bullets, and backend search terms that obey Amazon's character, byte, and keyword rules while staying click-worthy in the search grid. Use when drafting or fixing a Seller Central listing, rewriting an Amazon title or bullet points, packing backend search terms, or recovering a listing flagged or suppressed for content. Do NOT use when writing on-site product-detail-page copy for your own storefront or marketing site - use product-description-writer instead.
In this repository8 other files it gives its agents.
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 6 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 16
Run the compliance pass before delivering: scan every field against the Do NOT list and the category's restricted-word rules (supplements, …
- Distinctive: line 29
Every word in the title is search-relevant.
- Distinctive: line 32
No claim survives that you cannot substantiate.
- Distinctive: line 35
Use ALL CAPS, emojis, or decorative symbols anywhere.
- Distinctive: line 36
Use promotional phrasing in the title or bullets ("best", "sale", "free shipping", "#1").
- Distinctive: line 39
Put competitor brand names, ASINs, quotes, pricing, or time-sensitive info in any field.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Amazon Listing Optimizer
Optimize an Amazon listing for both the A9 search algorithm and a shopper scanning a crowded grid, within Amazon's exact structural rules.
Workflow
- Gather inputs: the product, top 5-10 target keywords, brand name, key specs, and the category. If keywords are missing, ask for them or for the category to infer intent - do not guess. If a requested claim violates Amazon policy or lacks substantiation, refuse and propose compliant phrasing before writing.
- Write the title. Cap under 200 characters, but many categories cap at 80 - target roughly 80-150 and verify the category limit. Order: brand, primary keyword, then most search-relevant attributes (type, size, quantity, color). Capitalize the first letter of each major word. Make the first ~50 characters say what it is and why it differs, since that is what shows on mobile.
- Write exactly 5 bullets. Begin each with a 2-4 word capitalized benefit label, then one supporting sentence. Keep each bullet under ~200 characters for mobile readability. Cover in priority order: main benefit, key feature, fit/compatibility, what is in the box or dimensions, trust/guarantee point. Reserve one bullet for the top objection that reviews reveal.
- Write backend search terms. The field caps at 250 bytes total (not per line); spaces separate terms, so no commas. Do not repeat any word already in the title or bullets - Amazon indexes those separately and repeats waste bytes. Add synonyms, common and alternate spellings, and use-case terms. Lowercase throughout.
- Run the compliance pass before delivering: scan every field against the Do NOT list and the category's restricted-word rules (supplements, beauty, baby are strictest).
Deliverable
Produce a paste-ready listing package containing:
- The title - with its character count and the verified category cap noted beside it.
- The five bullets - each with its benefit label, character count, and the priority slot it fills (main benefit, key feature, fit, contents, trust/objection).
- The backend search-term string - a single lowercase, space-separated line with its byte count out of 250 and confirmation of zero overlap with title/bullet words.
- A compliance sign-off - one line per field confirming it passed the Do NOT list and the category's restricted-word rules, plus any claim that was rewritten for substantiation and why.
Quality bar
- Title and each bullet are within their character limits and the verified category cap.
- Every word in the title is search-relevant; none is filler, because every word is indexed.
- Backend terms add only new tokens (zero overlap with title/bullets) and fit in 250 bytes.
- Secondary keywords read naturally inside sentences, never stacked into nonsense.
- No claim survives that you cannot substantiate.
Do NOT
- Use ALL CAPS, emojis, or decorative symbols anywhere.
- Use promotional phrasing in the title or bullets ("best", "sale", "free shipping", "#1").
- Make restricted claims ("cures", "FDA approved", or unsubstantiated guarantees).
- Repeat words across the title, bullets, and backend terms.
- Put competitor brand names, ASINs, quotes, pricing, or time-sensitive info in any field.
- Keyword-stuff a bullet until it stops reading like a sentence.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

