Amazon Blue Ocean Market Detector
Paste the following prompt into your AI chat to install this skill:
Follow https://skillhub.cn/install/skillhub.md to install @user_790bb7bf/amazon-blue-ocean-market-detector.
About this skill
Problem
Amazon product selection often fails not because keywords are missing, but because signals are scattered: category search volume, niche competition, ASIN review counts, sales velocity, new-release momentum, off-site demand, design patents, and trademark risk are usually evaluated in isolation. Manual spreadsheet work can mistake high search volume for opportunity, or treat a zero-result long-tail query as proof that demand does not exist. amazon-blue-ocean-market-detector turns this into a structured go/no-go workflow: validate demand, assess competitive structure, and filter out high-risk directions using IP and review signals.
How It Works
- Fast mode: the default path, targeting roughly 90 seconds.
- Uses
filter_nichesandkeyword_trendsto check category or keyword momentum. - Uses
search_amazonto inspect the first five organic results and identify a Moat Giant (high review count, mature badges) and a Breakout Black Horse (lower review count but strong sales or ranking signals). - Uses
list_new_releasesandget_amazon_productto measure new-entry pressure and single-product detail. - Produces a structured five-part report instead of dumping raw JSON.
- Full mode: triggered only when the user explicitly asks for a deep or complete report.
- Uses
ai_searchto collect off-site demand signals from Reddit, TikTok, and similar sources. - Uses
wipo_searchto scan USPTO design patents and flag active patents held by large companies or law firms. - Uses
ai_searchfor a preliminary text-trademark screening pass. - After budget confirmation, calls
get_amazon_reviewsand clusters the top negative-review pain points. - Data discipline: the report only uses hard data returned by the MCP tools. Key numbers are traceable to calls such as
search_amazon,get_amazon_product, andfilter_niches; missing fields are explicitly marked as not returned by the backend instead of being filled with approximations.
Boundaries
This skill is useful for early product discovery, category entry decisions, competitor prototyping, and pre-launch risk scanning. It is not a substitute for formal legal clearance or investment advice. Fast mode avoids slower, costlier tools such as review scraping. marketplaceId must be an ISO site code such as US, UK, or DE, not an Amazon merchant ID. Terminal errors like AUTH, QUOTA, and BAD_INPUT should not be blindly retried; transient errors such as RATE_LIMIT or 9200 require lowering concurrency and retrying only the failed request.
Use Cases
- Before entering an Amazon niche, use Fast mode to check trends, organic results, and competitor sales signals.
- When shortlisting a candidate niche, separate high-review incumbents from low-review breakout sellers.
- Before tooling, scan USPTO design patents for active filings against the reference brand.
- Before listing optimization, pull one page of negative reviews and cluster the top three pain points.
Best For
- Product managers working on Amazon cross-border selection: need data-backed go/no-go judgment before entering a category.
- Launch operations owners: need to compare incumbents, breakout sellers, and new-release signals to judge entry timing.
- Supply-chain engineers doing early compliance screening: need to flag design-patent and trademark risk before tooling.
- Sellers optimizing listings: need to extract review pain points and turn them into title, bullet, and backend keyword direction.
Related Skills
Analyzes bidding documents, extracts key requirements and risks, and generates a structured WPS report.
Amazon US A9 Listing optimization workflow that uses Fast and Full tiers to combine PDP data, reviews, and trademark checks into copy-ready title, bullets, and backend search terms.
Scans a reimbursement folder, extracts ride, hotel, high-speed rail, and flight details, calculates allowances and discounts, and outputs a deduplicated report.
Stress-test product logic by challenging assumptions, demanding evidence, and pruning the idea to a minimal verifiable core.