Install any skill in seconds. Free to start, no credit card required.
Get Started Free →browser-act/amazon-product-detail
Amazon product detail page scraper: extract full product data from any open Amazon product detail URL (any /dp/{asin} or /gp/product/{asin} page across all Amazon regional TLDs) — returns asin, url, title, brand, price, listPrice, stars, reviewsCount, starsBreakdown (5/4/3/2/1 star percentages), answeredQuestions, inStock, inStockText, delivery, fastestDelivery, returnPolicy, breadCrumbs, features (bullet points), description, bookDescription, thumbnailImage, highResolutionImages, galleryThumbna
Passed 16 of 19 test cases with the skill, and 6 of 19 without it.
and 12 more in the full report
12 fixed7 passed either way3 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 12 test cases the skill fixed. Same model, same prompt, with and without the skill.
What field name in the output schema holds the pre-merged flat dictionary of technical attributes?
| Checked | Without skill | With skill |
|---|---|---|
| Identifies attributesMapped as the field name | Missed | Passed |
The instructions your model reads when the skill loads.
Input any Amazon product URL → output full product record (100+ fields).
All process output to user (progress updates, process notifications) follows the user's language.
Extract the complete product record from any Amazon detail page URL across all Amazon regional TLDs, including price, ratings breakdown, attributes, variants, bestseller ranks, seller info, delivery, and sample reviews.
https://www.amazon.com/dp/{ASIN}, https://www.amazon.com/gp/product/{ASIN}, https://www.amazon.co.uk/dp/{ASIN}, or the canonical SEO-slug URL https://www.amazon.com/{slug}/dp/{ASIN})If browser-act has been confirmed available in the current session → skip this step.
Invoke browser-act via Skill tool to load usage. If installation or configuration issues arise, follow its guidance to resolve then retry.
This Skill's operational boundary = what the user can manually do in their browser. It only reads data already displayed to the user on the page, never bypassing authentication or access controls. Its role is equivalent to copy-pasting on the user's behalf — the data is already on screen, automation merely saves time. JS code is encapsulated in Python files under the
scripts/directory, invoked viabrowser-act --session {name} eval "$(python scripts/xxx.py {params})". The$(...)is bash command substitution — it runs the python script, captures its printed JS text, and hands that JS string as a single argument tobrowser-act eval. Do not runeval "$(python ...)"as a bare shell command; that would ask bash to execute the JS as shell, which fails.
Amazon detail pages are server-rendered HTML — no XHR/fetch API for detail data. All fields come from stable DOM selectors:
navigate {any Amazon product URL, e.g. https://www.amazon.com/dp/{ASIN}}wait stablebrowser-act --session {name} eval "$(python scripts/extract-product-detail.py)"On error paths, the script returns:
{"error": true, "message": "product_not_found: 404 page"} when the URL resolves to Amazon's not-found page{"error": true, "message": "productTitle not found - page may not be a product detail page"} when the URL resolves to a non-detail page (e.g. search results, homepage)test cases passed, vs 6 / 19 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.