SEO Keyword Clustering
AgriciDaniel/claude-seo
Clusters keywords by how much their search results overlap and designs a hub-and-spoke content plan with an internal link matrix and an interactive cluster map.
Amazon keyword research and market opportunity analysis for sellers.
$ npx skills add nexscope-ai/Amazon-Skills --skill amazon-keyword-research -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install nexscope-ai/Amazon-Skills amazon-keyword-research --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/nexscope-ai/Amazon-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/amazon-keyword-research .claude/skills/amazon-keyword-research && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "amazon-keyword-research" agent skill from https://github.com/nexscope-ai/Amazon-Skills/tree/main/amazon-keyword-research into .claude/skills/amazon-keyword-research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "amazon-keyword-research", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/nexscope-ai/Amazon-Skills/tree/main/amazon-keyword-researchType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add nexscope-ai/Amazon-Skills --skill amazon-keyword-research -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install nexscope-ai/Amazon-Skills amazon-keyword-research --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nexscope-ai/Amazon-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/amazon-keyword-research .agents/skills/amazon-keyword-research && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "amazon-keyword-research" agent skill from https://github.com/nexscope-ai/Amazon-Skills/tree/main/amazon-keyword-research into .agents/skills/amazon-keyword-research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "amazon-keyword-research", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add nexscope-ai/Amazon-Skills --skill amazon-keyword-research -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install nexscope-ai/Amazon-Skills amazon-keyword-research --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nexscope-ai/Amazon-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/amazon-keyword-research .cursor/skills/amazon-keyword-research && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "amazon-keyword-research" agent skill from https://github.com/nexscope-ai/Amazon-Skills/tree/main/amazon-keyword-research into .cursor/skills/amazon-keyword-research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "amazon-keyword-research", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/nexscope-ai/Amazon-Skills.git --path amazon-keyword-research--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add nexscope-ai/Amazon-Skills --skill amazon-keyword-research -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install nexscope-ai/Amazon-Skills amazon-keyword-research --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nexscope-ai/Amazon-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/amazon-keyword-research .gemini/skills/amazon-keyword-research && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "amazon-keyword-research" agent skill from https://github.com/nexscope-ai/Amazon-Skills/tree/main/amazon-keyword-research into .gemini/skills/amazon-keyword-research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "amazon-keyword-research", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install nexscope-ai/Amazon-Skills amazon-keyword-researchInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add nexscope-ai/Amazon-Skills --skill amazon-keyword-research -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/nexscope-ai/Amazon-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/amazon-keyword-research .github/skills/amazon-keyword-research && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "amazon-keyword-research" agent skill from https://github.com/nexscope-ai/Amazon-Skills/tree/main/amazon-keyword-research into .github/skills/amazon-keyword-research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "amazon-keyword-research", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add nexscope-ai/Amazon-Skills --skill amazon-keyword-research -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install nexscope-ai/Amazon-Skills amazon-keyword-research --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nexscope-ai/Amazon-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/amazon-keyword-research .opencode/skills/amazon-keyword-research && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "amazon-keyword-research" agent skill from https://github.com/nexscope-ai/Amazon-Skills/tree/main/amazon-keyword-research into .opencode/skills/amazon-keyword-research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "amazon-keyword-research", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
amazon-keyword-researchAmazon keyword research and market opportunity analysis for sellers.
Amazon Keyword Research is an agent skill from nexscope-ai/Amazon-Skills. 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…
Its SKILL.md is about 2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including scripts (for example `_meta.json` and `scripts/research.sh`).
It sits in Marketing & SEO, covering Keyword research and Startup and business strategy. The repository describes itself as: Free AI agent skills for Amazon sellers— keyword research, competitor analysis, listing audit & more. Works with OpenClaw, Claude Code, Cursor, Windsurf, Codex and any agent that… The licence is MIT.
4 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 0f3b13f. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Ships 1 file in scripts/ (Shell), which the agent can run.
Shell commands in SKILL.md call:
npxFrom the folder's file list and the shell code blocks in SKILL.md.
Hosts in commands or code, which the agent is likely to contact:
trends.google.comAlso links to:
nexscope.aiFrom URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Amazon Keyword Research loads about 2k tokens when it runs. Until then it costs about 247 tokens; SKILL.md has 649 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
The full file from nexscope-ai/Amazon-Skills at commit 0f3b13f, republished under its MIT licence (© nexscope-ai). 649 words, ~2,028 tokens.
.claude/skills/amazon-keyword-research/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.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 -gUsers can ask naturally. Examples:
Research the keyword "portable blender" on Amazon USFind long-tail keywords for "yoga mat" on AmazonI 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 GermanyResearch "water bottle" across Amazon US, UK, and DERun 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 keywordsFor 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=USIf Google Trends returns a 429 error, fall back to web_search for seasonal data:
"<keyword>" seasonal trends demand peak monthsIdentify: 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" usThen 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.
© nexscope-ai, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 2 other files (scripts) in amazon-keyword-research of nexscope-ai/Amazon-Skills.
Open the folder on GitHubat commit 0f3b13f
Amazon Keyword Research next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Amazon Keyword Research this skillnexscope-ai/Amazon-Skills | 744 | — | ~2k | Automated safety check: Pass | MIT | |
| SEO Keyword ClusteringAgriciDaniel/claude-seo | 19k | 2 repos | ~3.3k | Automated safety check: Pass | MIT | |
| Evaluate Skillevery-app/open-seo | 23k | — | ~1.8k | Automated safety check: Notes | MIT | |
| SEO Content Brief GeneratorAgriciDaniel/claude-seo | 19k | 2 repos | ~2.6k | Automated safety check: Pass | MIT | |
| Blog GoogleAgriciDaniel/claude-blog | 2.3k | 1 repos | ~3.3k | Automated safety check: Notes | MIT | |
| FLOW SEO FrameworkAgriciDaniel/claude-seo | 19k | 2 repos | ~1.4k | Automated safety check: Pass | MIT |
AgriciDaniel/claude-seo
Clusters keywords by how much their search results overlap and designs a hub-and-spoke content plan with an internal link matrix and an interactive cluster map.
every-app/open-seo
Test a candidate OpenSEO skill end to end by running fresh, isolated Codex sessions against the local backend and scoring the reports they save.
AgriciDaniel/claude-seo
Builds research-backed SEO content briefs with competitor scoring, per-section word counts and page-type templates, for new pages or improving existing ones.
AgriciDaniel/claude-blog
Google API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity…
AgriciDaniel/claude-seo
Brings the FLOW framework's stage-specific SEO prompts into the agent, from keyword discovery through backlinks, on-page work and conversion to local SEO, loaded on demand.
AgriciDaniel/codex-seo
Live SEO data via DataForSEO MCP server. An agent skill from AgriciDaniel/codex-seo.
nexscope-ai/Amazon-Skills
Amazon listing builder and optimizer for sellers. An agent skill from nexscope-ai/Amazon-Skills.
nexscope-ai/Amazon-Skills
Comprehensive product research and opportunity analysis for Amazon sellers.
nexscope-ai/Amazon-Skills
Amazon backend search term optimization and strategy. An agent skill from nexscope-ai/Amazon-Skills.
nexscope-ai/Amazon-Skills
Amazon Brand Analytics interpretation and strategic insights for Brand Registry owners.
nexscope-ai/Amazon-Skills
Amazon Buy Box strategy and optimization framework. An agent skill from nexscope-ai/Amazon-Skills.
nexscope-ai/Amazon-Skills
Amazon competitor monitoring and competitive intelligence for sellers.
Categories
Amazon keyword research and market opportunity analysis for sellers. Amazon Keyword Research is an agent skill from nexscope-ai/Amazon-Skills. Amazon keyword research and market opportunity analysis for sellers.
Amazon Keyword Research fits situations like: the user mentions Amazon product research; finding products to sell on Amazon; amazon keyword ideas; competition analysis for Amazon.
Run `npx skills add nexscope-ai/Amazon-Skills --skill amazon-keyword-research -a claude-code`. Or copy the skill folder (amazon-keyword-research in nexscope-ai/Amazon-Skills) into .claude/skills/amazon-keyword-research in your project. Claude Code loads it when a task matches its description.
Run `npx skills add nexscope-ai/Amazon-Skills --skill amazon-keyword-research -a codex`. Or copy the skill folder (amazon-keyword-research in nexscope-ai/Amazon-Skills) into .agents/skills/amazon-keyword-research in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add nexscope-ai/Amazon-Skills --skill amazon-keyword-research -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/amazon-keyword-research, .gemini/skills/amazon-keyword-research, .github/skills/amazon-keyword-research and .opencode/skills/amazon-keyword-research in your project.
Going by SKILL.md and its folder, Amazon Keyword Research needs a shell for the scripts in its folder and the command-line tools its instructions call (npx). Our summary lists: Node.js; A Bash shell.
SKILL.md names 2 domains. In commands or code: trends.google.com; the agent is likely to contact it when it follows the instructions. As links in the text: nexscope.ai. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
Amazon Keyword Research is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 2k tokens (SKILL.md is roughly 8.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Amazon Keyword Research: SEO Keyword Clustering (AgriciDaniel/claude-seo, 19k stars), Evaluate Skill (every-app/open-seo, 23k stars), SEO Content Brief Generator (AgriciDaniel/claude-seo, 19k stars) and Blog Google (AgriciDaniel/claude-blog, 2.3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
nexscope-ai (a GitHub organization) maintains it in nexscope-ai/Amazon-Skills, which has 744 GitHub stars. The repository holds 50 skills in this directory. The repository was last updated on August 26, 2026.
Source: nexscope-ai/Amazon-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.