amazon-asin-search-auditor
Skill8 starsChanged 45 days agoMITView on GitHub
Audit an Amazon seller's organic and sponsored search visibility by combining DataDoe search-term data, live Amazon search results, owned-ASIN matching, screenshots, and a reusable dashboard report. Use when asked to run an Amazon ASIN/search visibility audit for a specific DataDoe seller.
In this repository26 other files it gives its agents.
- amazon-listing-optimizerSkill
- buy-box-loss-root-causeSkill
- create-amazon-reconciliation-dashboardSkill
- create-orders-managerSkill
- daily-account-health-checkSkill
- daily-performance-health-checkSkill
- fba-inventory-ledger-reportSkill
- fba-stock-restock-plannerSkill
- keyword-rank-sqp-trackerSkill
- net-profit-pl-analyzerSkill
- ppc-asin-acos-alertSkill
- ppc-bid-optimizer-applySkill
- ppc-campaign-acos-alertSkill
- ppc-negative-keyword-applierSkill
- ppc-profit-bid-applySkill
- ppc-wasted-spend-watchdogSkill
- promotions-managerSkill
- restock-priority-alertSkill
- return-refund-analyzerSkill
- sales-movers-scannerSkill
- suppressed-inactive-listings-checkSkill
- vendor-inventory-reportSkill
- vendor-performance-dashboardSkill
- vendor-pnl-dashboardSkill
- weekly-business-reviewSkill
- weekly-sales-briefingSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
18 rules. About 0 are common, 11 are distinctive, and 7 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈11
Distinctive · estimate
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 18
Use the built-in browser directly for any ASIN analysis work.
- Distinctive: line 19
Do not finish until all steps are done.
- Distinctive: line 20
If you need a script to perform an action, use NodeJS.
- Very specific: line 21
Create a new directory in the project root at runs/RUN_DIR, with RUN_DIR being run_YY_MM_DD_HH_mm.
- Very specific: line 22
Read references/asin-visibility-auditor.md when the user asks for analysis, optimization, or audit work on a specific ASIN.
- Distinctive: line 23
When the Action Plan tells you to do so, you MUST spawn a sub-agent.
- Distinctive: line 25
Do not repeat the steps that were sent to the sub-agent.
- Distinctive: line 28
If the DataDoe Seller or Vendor is not provided: Ask the user to input the Seller or Vendor to use.
- Distinctive: line 30
Use the 'sellers_and_vendors_list' tool.
- Distinctive: line 40
5 unique: search terms after dedup.
- Very specific: line 41
Add all other available metrics to the data, using child_asin_search_query_score for Amazon Search Query Score.
- Very specific: line 45
Write coreSearchSummaries.json with normalized fields matching references/dashboard.md.
- Distinctive: line 49
Always use web browser cards that are visible to the user, so the user can follow your actions.
- Distinctive: line 50
If prompted: Accept cookies usage.
- Distinctive: line 53
Search for each unique search term and collect all ASINs with their organic/paid search ranks:
- Very specific: line 55
Use this command to URL encode: node -e "console.log(encodeURIComponent('SEARCH_TERM'))".
- Very specific: line 56
Before collecting the data, make sure that Deliver to, language, and currency are properly set.
- Very specific: line 107
If the user asks for analysis / optimization / audit / etc.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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 ASIN Search Auditor
General Rules
- Execute exactly all actions from the "Action Plan".
- Use the built-in browser directly for any ASIN analysis work.
- Do not finish until all steps are done.
- If you need a script to perform an action, use NodeJS.
- Create a new directory in the project root at
runs/RUN_DIR, withRUN_DIRbeingrun_YY_MM_DD_HH_mm. Store all run files in that directory and only in that directory. - Read
references/asin-visibility-auditor.mdwhen the user asks for analysis, optimization, or audit work on a specific ASIN. - When the Action Plan tells you to do so, you MUST spawn a sub-agent. Spawn sub-agents for those steps and only for those steps.
- Pause your work until the sub-agent is done. It is OK if you need to wait for the sub-agent for a few minutes.
- Do not repeat the steps that were sent to the sub-agent.
Action Plan
- If the DataDoe Seller or Vendor is not provided: Ask the user to input the Seller or Vendor to use.
- (Spawn a sub-agent for this step) DataDoe resolver:
- Use the 'sellers_and_vendors_list' tool.
- Return only
{sellerId, marketplace, displayName}.
- (Spawn a sub-agent for these steps) Core term export normalizer:
- Fetch the following top search terms data:
- Source:
amazon_child_product_organic_search_ranks_per_week. - Total top 5 search terms by
child_asin_purchase_countfrom the last 60 days. - This source is weekly-grain (one row per ASIN/term/week), so a row is NOT a
unique term -
ORDER BY child_asin_purchase_count DESC LIMIT 5returns 5 rows that can dedupe to fewer terms. Pull a larger limit (15-20 rows) ordered bychild_asin_purchase_count DESCfrom the last 60 days, then take the first 5 unique search terms after dedup. - Add all other available metrics to the data, using
child_asin_search_query_scorefor Amazon Search Query Score. child_asin_organic_search_rankis a deprecated compatibility name and should not be used; neither name measures organic search position. Keep scores per ASIN and period, never use them as browser-observed ranks.- Download the report to file using
exports_raw_url_getmethod. - It is OK if there are fewer than 60 days of data.
- Source:
- Write
coreSearchSummaries.jsonwith normalized fields matchingreferences/dashboard.md. - Return only the top terms + totals.
- Fetch the following top search terms data:
- Prepare a list of unique search terms that appeared in the data.
- Open the Amazon website for the seller's marketplace in the built-in browser if available, otherwise fall back to Chrome MCP:
- Always use web browser cards that are visible to the user, so the user can follow your actions.
- If prompted: Accept cookies usage.
- Change the
Deliver toto a valid postal code from the capital of the marketplace country. - Change the language of the page and currency to the ones local to the marketplace.
- Search for each unique search term and collect all ASINs with their organic/paid search ranks:
- To search, enter a URL matching this pattern:
https://AMAZON_DOMAIN/s?k=SEARCH_TERM_URL_ENCODED. - Use this command to URL encode:
node -e "console.log(encodeURIComponent('SEARCH_TERM'))". - Before collecting the data, make sure that
Deliver to, language, and currency are properly set. - Take a screenshot of the top of each results page in the built-in browser and save it in
search_results/screenshots/st-SEARCH_TERM.png. - Sponsored results are marked as sponsored. If a result is sponsored, it is not organic (a single ASIN cannot be both).
- For each search term, prepare a JSON file named
search_results/st-SEARCH_TERM.jsonwith the following content:
{ "searchTerm": "SEARCH_TERM", "amazonMarketplace": "AMAZON_DOMAIN", "checkedAt": "CURRENT_DATE", "screenshotLocation": "run-root-relative path to the screenshot", "organicRanks": [ { "asin": "ASIN", "organicRank": rank as int, "price_value": price as float 00.00, "price_currency": "CURRENCY_CODE", "asin_name": "NAME_OF_THE_ASIN (exact as displayed in search results)", "asin_rating" review rating as float 0.0 or null if not given in the result tile, "asin_image_url": "LINK_TO_THE_ITEM_IMAGE", "asin_url": "LINK_TO_THE_ITEM (exact URL as the user would click it)", "my_listing": null } ], "ppcRanks": [ { "asin": "ASIN", "ppcRank": rank as int, "price_value": price as float 00.00, "price_currency": "CURRENCY_CODE", "asin_image_url": "LINK_TO_THE_ITEM_IMAGE", "asin_url": "LINK_TO_THE_ITEM", "my_listing": null } ] } - To search, enter a URL matching this pattern:
- (Spawn a sub-agent for this step) Extract unique ASINs from all results for each search term using
scripts/list-asins.js. - (Spawn a sub-agent for this step) Fetch the seller's active listings for the candidate ASINs only (the unique ASINs from step 11 /
asins.json) using DataDoe, and save to CSV:- Source:
amazon_listings_with_cogs. - Filter:
child_asin IN [the step-11 candidate ASINs]ANDlisting_status = Active. - This targets the few dozen ASINs from the search results, so it never hits the export row cap (1,000 rows JSON / 5,000 CSV) and needs no pagination - correct regardless of catalog size. Do NOT dump the whole catalog: an unordered
listing_status = Activepull on a large catalog can drop an actively-selling owned ASIN off page 1, which then reads as "not mine" and shows a competitor beating a rank that is actually yours. - Request
child_asinin the columns. DataDoe prepends 8 utility columns beforechild_asin, so downstream parsing must be header-based, not column-position (seescripts/mark-my-listings.js). - (Fallback, only if a full-catalog snapshot is ever required: add a deterministic
orderByColumnand loop - "while returned rowCount == limit, repeat with skip += limit" - so the cap never silently drops rows.)
- Source:
- (Spawn a sub-agent for these steps) Run the file-based post-processor for the step 11 ASIN list, step 12 listings export, and the dashboard build:
- Mark my listings in JSONs using
scripts/mark-my-listings.js. - Generate
report-data.json. - Render
report.html. - Run contract checks.
- Return only summary stats + paths.
- Mark my listings in JSONs using
- That's all. Open the report page for the user.
If the user asks for analysis / optimization / audit / etc. of a specific ASIN, then follow references/asin-visibility-auditor.md directly with the ASIN, the marketplace domain to use, and the location of your run data. Never run this task in a sub-agent.
Glossary
- ASIN:
- An ASIN (Amazon Standard Identification Number) is a unique 10-character code Amazon uses to identify and manage products in its marketplace.
- ASIN matches the regex:
\b[a-zA-Z0-9]{10}\b.
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.

