Amazon Daily Competitor Radar

Problem

• Tracking one Amazon ASIN in isolation can miss competitor moves: price cuts, rank shifts, Buy Box changes, review spikes, coupon changes, and new entrants.
• This skill turns daily monitoring into a repeatable SOP: check the target ASIN and SERP, then check category momentum, and optionally inspect reviews, Rufus visibility, seller catalog, and external sentiment.

How it works

• The default Fast mode targets one ASIN and aims for a sub-60-second report using search_amazon, get_amazon_product, and list_bestsellers, with alerts for price, rank, Buy Box, rating count, and coupons.
• If no keyword is provided, it infers 2-3 traffic words from the PDP leaf category and title terms, then filters out the seller's own brand to preserve hijacker signal.
• Full mode adds list_new_releases, get_amazon_reviews, search_amazon_alexa, list_seller_products, and ai_search overview for new entrants, review comparisons, AI recommendation pool visibility, seller breadth, and off-site sentiment.
• A JSON baseline snapshot is stored under ~/.pangolinfo/baselines/; on first run it reports absolute values only and avoids trend arrows without prior data.
• It enforces a conservative concurrency limit of 2 scrapeApi calls per turn because 3-way concurrency can trigger 9200.

Boundaries

• Best for sellers or growth advisors who already own a primary ASIN and need daily alerts on price, rank, Buy Box, reviews, new entrants, and AI visibility.
• Not a substitute for product discovery, keyword mining, listing optimization, or inventory and supply-chain analysis.
• All metrics must come from MCP responses; missing fields are stated explicitly rather than estimated.
• search_amazon_alexa is a slow endpoint, typically 60-90 seconds and up to about 200 seconds, so it should be reserved for Full mode when rank loss or competitor pressure is detected.