review-collect

Aggregate Amazon and Noon product reviews into versioned JSON files.

40|8|Updated May 14, 2026
One-click install
npx skills add https://github.com/zpoint/vibe-seller --skill review-collect
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-collect
Source: https://github.com/zpoint/vibe-seller/tree/main/app/skills_v2/review-collect
Command: npx skills add https://github.com/zpoint/vibe-seller --skill review-collect

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Cross-border sellers managing stores on Amazon and Noon need to aggregate full customer review and rating data across their entire product catalog to analyze sentiment, track performance, and inform listing updates. Manually checking each product page is extremely time-consuming, error-prone, and impossible to scale for stores with hundreds of products, especially when needing to capture low-star reviews and full historical data.

Core Features & Use Cases

  • Full Review History Collection: Gathers every customer review (sorted newest-first) for every product in a store's Amazon and Noon catalog, including low-star reviews filtered via platform-specific query parameters, with idempotent deduplication across runs.
  • Standardized Versioned Output: Exports data as per-product JSON files conforming to the reviews/v1 contract, plus a manifest index for completeness tracking, ready for downstream analysis or integration with other tools.
  • Read-Only Safe Operation: Never posts, edits, or deletes any content on Amazon or Noon, eliminating risk of accidental changes to live store listings or customer interactions.
  • Use Case: A seller running 3 Amazon country stores and 2 Noon country stores can use this skill to collect all reviews for 200+ products in a single automated run, instead of spending days manually navigating each product page.

Quick Start

Use the review-collect skill to gather all customer reviews and ratings for every product in your Amazon and Noon store catalogs and save them as structured JSON files for analysis.

Frequently Asked Questions about review-collect

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I collect Amazon and Noon reviews into a structured JSON format?

To collect Amazon and Noon reviews into structured JSON, aggregate scattered product review and rating data into a standardized, machine-readable dataset. This process exports full historical review data as per-product JSON files conforming to the reviews/v1 contract.

Can I gather low-star reviews and full historical data for multiple Amazon stores?

Yes, you can gather low-star reviews and full historical data for multiple Amazon stores. The collection applies platform-specific query parameters to filter low-star reviews and ensures idempotent deduplication across all runs for every product in your catalog.

What is the best way to automate cross-border e-commerce review collection?

The best way to automate cross-border e-commerce review collection is to run an automated aggregation process across multiple marketplace country combinations. This captures every customer review sorted newest-first and exports a manifest index for downstream analysis.

Does collecting product ratings from Amazon storefronts risk modifying my live listings?

No, collecting product ratings from Amazon storefronts does not risk modifying your live listings. The collection operates strictly in read-only mode to prevent accidental platform modifications, ensuring it never posts, edits, or deletes any content.

How do I export cross-border sales product ratings for downstream consumer ingestion?

You export cross-border sales product ratings for downstream consumer ingestion by generating versioned JSON output. This output conforms to the reviews/v1 data contract and includes a manifest index for completeness tracking, ready for integration with other tools.

Why does my full review history collection need idempotent deduplication?

Your full review history collection needs idempotent deduplication to prevent duplicate data entries across multiple automated runs. This ensures that gathering every customer review across hundreds of products remains accurate and avoids re-processing existing records.