Amazon Keyword Research logo

Amazon Keyword Research

Organization
nexscope-ai
amazon-keyword-research

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?'.

Overview

Publishernexscope-ai
RepositoryAmazon-Skills
Skill nameamazon-keyword-research
Stars
726
Forks
125
Bundled files
2
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 2 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by nexscope-ai on GitHub. Read the source before you install it.

Installation

Install the Amazon Keyword Research AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/nexscope-ai/Amazon-Skills/tree/main/amazon-keyword-research
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/nexscope-ai/Amazon-Skills.git /tmp/Amazon-Skills
mkdir -p .claude/skills
cp -r /tmp/Amazon-Skills/amazon-keyword-research .claude/skills/amazon-keyword-research
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Amazon Keyword Research in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Amazon Keyword Research on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Amazon Keyword Research is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Amazon Keyword Research 🔍

Free keyword research for Amazon sellers. No API key — works out of the box.

Installation

bash
npx skills add nexscope-ai/Amazon-Skills --skill amazon-keyword-research -g

Capabilities

  • Long-tail keyword mining: Extract 100-200 real search terms from Amazon's autocomplete engine
  • Competitor landscape analysis: Product count, price range, average rating, review distribution, top brands
  • Seasonal trend detection: 12-month Google Trends data to identify peak seasons and demand shifts
  • Market opportunity scoring: 1-10 score combining competition density, price room, and demand signals
  • Multi-marketplace support: US, UK, DE, FR, IT, ES, JP, CA, AU, IN, MX, BR
  • Keyword comparison: Side-by-side analysis of multiple keywords

Usage Examples

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

Workflow

Step 1: Gather Autocomplete Data

Run the bundled script to collect Amazon autocomplete suggestions:

bash
<skill>/scripts/research.sh "<keyword>" [marketplace]

Parameters:

  • keyword (required): The seed keyword to research
  • marketplace (optional): us (default), uk, de, fr, it, es, jp, ca, au, in, mx, br

What the script does:

  • Queries Amazon's autocomplete API with the seed keyword
  • Expands with prefixes: "best [keyword]", "cheap [keyword]", "top [keyword]"
  • Expands with a-z suffixes: "[keyword] a", "[keyword] b", ... "[keyword] z"
  • Returns deduplicated, sorted list of real search suggestions — one per line

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:

bash
<skill>/scripts/research.sh "portable blender" us
# Returns 100-200 long-tail keywords

For multi-marketplace research, run the script once per marketplace.

Step 2: Analyze Competition

Use web_search to gather competitor intelligence:

  1. Search "<keyword>" site:amazon.com — note approximate result count for competition density
  2. Search "<keyword>" amazon best sellers price review — extract price patterns, rating averages, dominant brands
  3. Summarize: total competitors, price range (min/avg/max), average star rating, top 5 brands by visibility

Why 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.

Step 3: Check Seasonality

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.

Step 4: Synthesize Report

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.

Output Format

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]

Multi-Keyword Comparison

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:

bash
<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:

Metriclaptop standmonitor standtablet 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.

Limitations

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.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Amazon Keyword Research AI skill do?

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...

Why use Amazon Keyword Research on TypingMind?

Because you install it once and use it with any model. Amazon Keyword Research is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Amazon Keyword Research in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/nexscope-ai/Amazon-Skills/tree/main/amazon-keyword-research. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Amazon Keyword Research?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Amazon Keyword Research?

As many as you like. As long as a model supports skills, you can use Amazon Keyword Research with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Amazon Keyword Research AI skill free?

Yes. It is published on GitHub by nexscope-ai under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇