Amazon Competitor Review Gap Analysis

The Problem

Amazon sellers often see demand signals in competitor reviews, but raw comments are scattered and negative themes get buried. Manual review work makes it hard to answer: which weaknesses hurt conversion most, and whether competitors are solving the same issues? This skill turns collected review samples into traceable gap analysis instead of generic praise-and-complaint summaries.

How It Works

• Entry command: voc --site <site> returns the total collection + VOC cost first; only after user confirmation does --confirm run collection, waiting, analysis, and archiving.
• Report interpretation: use reports / report --id; if deltaMd is returned, explain changes versus the previous report first: which issues improved, which emerged, and which are still worsening.
• Competitor comparison: use analyze --type compare for product-to-competitor comparison; when review counts are sufficient, use radar to compare trends. For top negative feedback, use reviews --stars negative --sort helpful.
• Operational alerts: alerts surfaces unread negative-review alerts, workbench sorts issues by severity, and advise --review-id generates reply suggestions.

Boundaries and Notes

• Paid operations must be quoted first and explicitly confirmed; never assume user consent to spend credits.
• After an interruption, do not rerun immediately; check reports first to confirm whether a report already exists and avoid duplicate charges.
• Data comes from ARI-collected samples; small samples or narrow windows need corroboration from additional sources. Strategy recommendations must be separated from direct data reads.