trackiq-amazon-listing-optimizerlisted

# Listing Optimizer The catalogue is full of skills that measure. **This one writes the fix.** One ASIN in, a rewritten title, five bullets, a description and backend terms out — each change traced to a search term that earns it or a question it answers. Output is a branded HTML document: current beside proposed, with reasons. ## Requires - **The Oxylabs scraper**, for `get_product` and `get_reviews` — the live page and what buyers say about it. - The TrackIQ MCP, for `list_marketplaces`, `get_search_query_performance` and `get_search_terms` — the terms worth ranking for and the ones that already convert. - Nothing else. No filesystem, no shell. - **Without the MCP:** works from the live page plus a keyword list the user supplies. Without Oxylabs it cannot see the page and should not guess — ask the user to paste the current title, bullets and description. ## First run Fill in a copy of `assets/account.example.md` saved as account.md beside the skill. Every TrackIQ skill reads the same file, so an account already set up for another TrackIQ report needs nothing added here. If the runtime has no filesystem, print the same block and ask the user to paste it into their project instructions once. ## Read first - `assets/fields.md` — what the scrape actually returns, and the two fields that are not what they look like - `assets/method.md` — where the terms come from and how the copy is built - `assets/checks.md` — what to verify before anything is published C