算法艺术创作
algorithmic-art
通过代码和可调参数创作生成艺术与交互式视觉效果。
ecommerce-product-detail【设计与创意】Extract complete product information from any e-commerce product page. Returns name, price, currency, brand, images, description, SKU/ASIN/EAN/UPC/GTIN/MPN identifiers, stock availability, rating, review count, variants, and seller. Works on Shopify, Amazon, WooCommerce, eBay, Walmart, Etsy, AliExpress, Alibaba, Target, Best Buy, Rakuten, Magento, Bi…
独立 GitHub 快照 · 自动分类 · 以原作者文档为准
Product URL / keyword / SKU → complete product data (name, price, brand, images, identifiers, availability, rating, variants)
All process output to user (progress updates, process notifications) follows the user's language.
Extract complete product information from any publicly accessible e-commerce product page using a universal multi-layer extraction strategy (JSON-LD → platform-specific DOM → OG meta → microdata).
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. JS code is encapsulated in Python files under the
scripts/directory, invoked viaeval "$(python scripts/xxx.py {params})". Use the bash tool for execution.
Navigate to the product URL first, then extract:
eval "$(python scripts/extract-product.py)"
Output example:
{
"url": "https://www.amazon.com/dp/B09WNK39JN",
"name": "Amazon Echo Pop",
"price": 39.99,
"price_currency": "USD",
"brand": "Amazon",
"image": "https://m.media-amazon.com/images/I/61bTwy0ooPL.jpg",
"images": ["https://...jpg", "https://...jpg"],
"description": "Compact smart speaker with Alexa...",
"category": ["Electronics", "Smart Speakers"],
"sku": "B09WNK39JN",
"gtin": null,
"mpn": null,
"availability": "InStock",
"rating": 4.7,
"review_count": 103789,
"variants": [{"name": "Charcoal", "sku": "B09WNK39JN", "price": 39.99}],
"seller": "Amazon",
"identifiers": {"ASIN": "B09WNK39JN", "Best Sellers Rank": "#1 in Smart Speakers"},
"_platform": "amazon",
"_source": "json-ld"
}
When input is a keyword, ASIN/SKU, or EAN/UPC rather than a direct product URL:
Step 1 — Navigate to search URL based on input type:
| Input type | Target site | URL pattern |
|---|---|---|
| ASIN (10-char alphanumeric) | Amazon | https://www.amazon.com/dp/{ASIN} |
| Keyword | Amazon | https://www.amazon.com/s?k={keyword_urlencoded} |
| Keyword | eBay | https://www.ebay.com/sch/i.html?_nkw={keyword_urlencoded} |
| Keyword | Walmart | https://www.walmart.com/search?q={keyword_urlencoded} |
Keyword + --site specified | Any site | https://{site}/search?q={keyword_urlencoded} |
| Keyword (no site) | Cross-site | https://www.google.com/search?tbm=shop&q={keyword_urlencoded} |
| EAN / UPC / GTIN | Cross-site | https://www.google.com/search?tbm=shop&q={identifier} |
Step 2 — If landed on a search/listing page (multiple results):
wait stableeval "$(python scripts/extract-listing.py --max-results 3)" — get top 3 resultsitems[0].urlnavigate {product_url} → wait stableStep 3 — Extract product data:
eval "$(python scripts/extract-product.py)"
Note: scripts/extract-listing.py is located in ../ecommerce-listing/scripts/extract-listing.py if used as a standalone Skill install; otherwise reference the listing Skill.
result.name != null AND (result.price != null OR result.availability != null)
https://www.amazon.com first to establish session cookies, then navigate to the product pagehttps://www.ebay.com first; use solve-captcha if a challenge appearswait stable before extractingPath: {working-directory}/browser-act-skill-forge-memories/ecommerce-scraper-ecommerce-product-detail.memory.md
Before execution: If the file exists, read it first — it records unexpected situations encountered during past executions (e.g., a strategy has become ineffective); adjust strategy order accordingly.
After execution: If an unexpected situation is encountered (strategy became ineffective, page redesigned, anti-scraping upgraded, better path discovered), append a line:
{YYYY-MM-DD}: {what happened} → {conclusion}