Amazon keyword research and market opportunity analysis for sellers. Retrieve autocomplete suggestions (long-tail keywords), analyze competitor landscape, and assess market opportunity for any keyword on 12 Amazon marketplaces (US/UK/DE/FR/IT/ES/JP/CA/AU/IN/MX/BR). No API key required. Make sure to use this skill whenever the user mentions Amazon product research, finding products to sell on Amazon, Amazon keyword ideas, niche analysis, competition analysis for Amazon, market opportunity on Amazon, comparing Amazon keywords, evaluating whether a product is worth selling, Amazon autocomplete data, seasonal demand for Amazon products, or anything related to researching what to sell on Amazon — even if they don't explicitly say 'keyword research'. Also trigger when the user asks vague questions like 'is this a good product to sell?', 'what's the competition like for X on Amazon?', 'should I sell X or Y?', or 'what are people searching for on Amazon?'.
npx skills add https://github.com/nexscope-ai/Amazon-Skills --skill amazon-keyword-research
Free keyword research for Amazon sellers. No API key — works out of the box.
npx skills add nexscope-ai/Amazon-Skills --skill amazon-keyword-research -g
Users can ask naturally. Examples:
Research the keyword "portable blender" on Amazon US
Find long-tail keywords for "yoga mat" on Amazon
I want to sell resistance bands. What does the Amazon keyword landscape look like?
Compare "laptop stand" vs "monitor stand" on Amazon US — which has more opportunity?
Analyze "Küchenmesser" on Amazon Germany
Research "water bottle" across Amazon US, UK, and DE
Run the bundled script to collect Amazon autocomplete suggestions:
<skill>/scripts/research.sh "<keyword>" [marketplace]
Parameters:
keyword (required): The seed keyword to researchmarketplace (optional): us (default), uk, de, fr, it, es, jp, ca, au, in, mx, brWhat the script does:
Why this matters: Amazon autocomplete reflects what real shoppers are actually typing. These aren't guesses — they're demand signals directly from Amazon's search engine. The prefix and alphabet expansion catches long-tail terms that basic autocomplete misses, which are often lower competition and higher intent.
Example:
<skill>/scripts/research.sh "portable blender" us
# Returns 100-200 long-tail keywords
For multi-marketplace research, run the script once per marketplace.
Use web_search to gather competitor intelligence:
"<keyword>" site:amazon.com — note approximate result count for competition density"<keyword>" amazon best sellers price review — extract price patterns, rating averages, dominant brandsWhy this matters: Raw keyword volume means nothing without competition context. A keyword with 10,000 searches but dominated by 3 entrenched brands with 10,000+ reviews each is a very different opportunity than one with the same volume but fragmented sellers. The price range reveals margin potential — if everything is under $10, margins will be razor-thin after FBA fees.
Use web_fetch on Google Trends:
https://trends.google.com/trends/explore?q=<keyword>&geo=US
If Google Trends returns a 429 error, fall back to web_search for seasonal data:
"<keyword>" seasonal trends demand peak months
Identify: trend direction (rising/declining/stable), seasonal peaks (which months), year-over-year change.
Why this matters: Seasonality determines cash flow risk. A product that sells 80% of its volume in Q4 means you need capital for inventory months in advance and may sit on dead stock the rest of the year. Rising trends mean growing demand and more room for new entrants; declining trends mean you're fighting over a shrinking pie. This context turns a keyword from a number into a business decision.
Combine all data into the output format below.
Why structure matters: Grouping keywords by intent (commercial vs informational vs niche) helps the seller understand not just what people search, but why they search it. The opportunity score condenses multiple signals into a single actionable number, but the breakdown behind it is what actually informs the decision — so always show the reasoning.
Present the final report in this structure:
## Keyword Research Report: [keyword]
**Marketplace:** Amazon [US/UK/DE/...]
**Date:** [current date]
### 1. Long-tail Keywords ([count] found)
**High Commercial Intent:**
- [keyword with "buy", "best", "vs", "for" etc.]
- ...
**Informational / Research:**
- [keyword with "how to", "what is", "review" etc.]
- ...
**Niche / Specific:**
- [long, specific keywords indicating clear purchase intent]
- ...
### 2. Competition Landscape
| Metric | Value |
|--------|-------|
| Estimated competitors | [number] |
| Price range | $[min] - $[max] |
| Average price | $[avg] |
| Average rating | [stars] |
| Top brands | [brand1, brand2, brand3...] |
### 3. Seasonal Trends
[Describe 12-month trend: peaks, valleys, stable periods]
[Note any upcoming peak seasons relevant to the keyword]
### 4. Market Opportunity Score: [X/10]
**Score breakdown:**
- Competition density: [low/medium/high] — [why]
- Price room: [low/medium/high] — [why]
- Demand trend: [growing/stable/declining] — [why]
- Niche potential: [low/medium/high] — [why]
**Recommendation:** [1-2 sentence actionable recommendation]
When the user asks to compare two or more keywords, run the full workflow (Steps 1-4) for each keyword separately, then present results in a side-by-side comparison table.
Example user input:
Compare "laptop stand" vs "monitor stand" vs "tablet stand" on Amazon US — which one should I sell?
How to execute: Run the script 3 times:
<skill>/scripts/research.sh "laptop stand" us
<skill>/scripts/research.sh "monitor stand" us
<skill>/scripts/research.sh "tablet stand" us
Then complete Steps 2-3 for each keyword, and output a comparison table:
| Metric | laptop stand | monitor stand | tablet stand |
|--------|-------------|---------------|-------------|
| Long-tail count | — | — | — |
| Avg price | — | — | — |
| Top brand dominance | — | — | — |
| Trend direction | — | — | — |
| Opportunity score | — | — | — |
End with a Recommendation stating which keyword has the best opportunity and why.
This skill uses publicly available data (Amazon autocomplete + web search). It does not provide exact monthly search volumes or sales estimates. For precise data, check out Nexscope — Your AI Assistant for smarter E-commerce decisions.
Built by Nexscope — research, validate, and act on e-commerce opportunities with AI.
Identifies high-quality leads for your product or service by analyzing your business, searching for target companies, and providing actionable contact strategies. Perfect for sales, business development, and marketing professionals.
Research your competitors and build an interactive battlecard. Outputs an HTML artifact with clickable competitor cards and a comparison matrix. Trigger with "competitive intel", "research competitors", "how do we compare to [competitor]", "battlecard for [competitor]", or "what's new with [competitor]".
Master the consultative sales methodology trusted by enterprise sales teams worldwide. Use Neil Rackham's research-backed question sequence to uncover needs and close complex deals. Use when: **Complex B2B sales** with long sales cycles; **High-value deals** requiring multiple stakeholders; **Solution selling** where discovery is critical; **Enterprise sales** with sophisticated buyers; **Consultative positioning** to differentiate from competitors
Complete product launch workflow coordinating 15+ specialist agents across research, development, marketing, sales, and operations. Uses sequential and parallel orchestration for 10-week launch timeline.
Content research and SEO writing methodology. Guides the agent through topic research, keyword identification, competitive analysis, and writing SEO-optimized content that ranks well and provides genuine value to readers.
Generate sandbox security policies from plain-language requirements and optional REST API documentation. Produces L4 or fine-grained L7 network policies and ordered network middleware configuration. Use for API access rules, middleware host selection, failure behavior, or built-in and operator-run middleware attachment. Trigger keywords - generate policy, create policy, update policy, change policy, sandbox policy, network policy, API policy, security policy, allow API, restrict API, network middleware, supervisor middleware.
Research a company, industry, or competitor set using web search and seven analytical lenses. Use when you need structured intel that feeds downstream PM skills.
Generative Engine Optimization (GEO) specialist — the technical, on-page publishing work that makes a given page or site discoverable, understandable, trustworthy, quotable, and fresh for AI answer engines (Google AI Overviews, ChatGPT Search, Bing Copilot, Perplexity). Use when asked to 'optimize this page/site for GEO', 'optimize for AI search / answer engines', 'get my page cited by ChatGPT/Perplexity', 'improve AI visibility/citability', 'write an llms.txt', 'add citation-ready structure or schema for AI answers', 'otimizar para busca com IA', or to audit/create/improve a codebase for generative search. Do NOT use for AI-driven SEO content strategy or programmatic pages at scale (use ai-seo), classic keyword/SERP ranking (use seo), accessibility (use web-accessibility), or multi-area site audits (use web-quality-audit).
Take nexscope-ai/amazon-keyword-research from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.
The instructions reference npx.
Without those the skill loads but fails at the first command.