keyword-research
Skill17 starsChanged 4 months agoMITView on GitHub
Amazon keyword research via the Helium 10 MCP — reverse-search competitors (Cerebro), expand seed terms, find coverage gaps, and prioritize by CPR into a keyword map for listings, backend terms, and ad campaigns. Use when the user asks "what keywords should I target", "research keywords for this product", "what do competitors rank for", or before writing/rewriting listing copy.
54 other projects use a version of this.
Adopted by
Most recently taken up by
- oivanfelipe/claude-skillstheir own version, first seen Nov 8, 2026
- kostja94/marketing-skillstheir own version, first seen Nov 8, 2026
- kristian-presso/claude-marketing-skillstheir own version, first seen Nov 8, 2026
- foverse/seoversetheir own version, first seen Nov 8, 2026
- AppKittie/aso-mcp-skillstheir own version, first seen Nov 8, 2026
- MoizIbnYousaf/marketing-clitheir own version, first seen Nov 1, 2026
Used with
Projects with it also use link-prospecting, seo-project-setup and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
JwuthriSkilllink-prospecting
Find link prospects, discover contact paths, and draft outreach from SERPs and backlink signals.
Also in 11 projects that use this
JwuthriSkillseo-project-setup
Set up a durable local SEO workspace with project context, notes, goals, positioning, preferences, MCP checks, and Search Console data intake.
Also in 11 projects that use this
appeekySkillapp-marketing-context
When the user wants to create or update their app marketing context document. Also use when the user mentions "app context", "marketing brief", "app positioning", or when starting any ASO or app marketing project. This is the foundation skill — all other skills check for this context first.
Also in 6 projects that use this
appeekySkillmetadata-optimization
When the user wants to optimize App Store metadata — title, subtitle, keyword field, or description. Also use when the user mentions "optimize my title", "ASO metadata", "keyword field", "character limits", "app description", or "write my subtitle". For keyword discovery, see keyword-research. For full ASO audits, see aso-audit.
Also in 6 projects that use this
liangdabiaoSkillreview-analysis
对亚马逊商品评论进行深度分析,自动识别产品痛点、分析退货原因,生成改进建议和客服回复模板。Invoke when user uses /review-analysis command with a product ASIN.
Also in 5 projects that use this
akii-technologies-ltdSkillkeyword-clustering
Cluster and organize keywords into topical groups for SEO. Use when the user asks to "cluster keywords", "group keywords", "organize keywords", "keyword mapping", "topic clusters", "keyword grouping", "build a content plan", "pillar pages", "topical authority", "semantic clustering", or pastes a list of keywords.
Also in 12 projects that use this
- +5 more from Jwuthri
Other versions54 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 54
- every-app/open-seo★ 27ksame name
- Ryze-AI-Adgent/open-seo-mcp-skills★ 8.4ksame name
- nowork-studio/toprank★ 4.1ksame name
- nowork-studio/notfair-plugin★ 4.1ksame name
- appeeky/aso-skills★ 2.2ksame name
- Eronred/aso-skills★ 2.2ksame name
- Jwuthri/Tracely-ai★ 1.3ksame name
- VladSez/easy-invoice-pdf★ 1.1ksame name
- kostja94/marketing-skills★ 1.1ksame name
- liangdabiao/amazon-sorftime-research-MCP-skill★ 1.1ksame name
44 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository4 other files it gives its agents.
- impact-trackerSkill
- listing-guardSkill
- review-automationSkill
- store-auditSkill
The file
Files
Keyword research → prioritized keyword map
Discovery is cheap; focus is the product. This skill ends with a per-ASIN keyword map routed into the other skills — not a 1,500-row dump.
Inputs
Your ASIN(s), 2–5 competitor ASINs (from get_listing_details of your top
keywords' ranking pages, or user-provided), and optionally seed phrases.
Phase 1 — Discover (pick per goal; watch the quota)
- Reverse-search a competitor:
get_keywords_by_asin(Cerebro) — every phrase the ASIN is visible for, with volume, rank, CPC, CPR, title density. ⚠ HUGE output (can be 1,000+ rows). Use for 1–2 ASINs max per session and summarize immediately; never paste raw output back to the user. - Gap vs competitors:
get_top_keywords(main_asin=yours, competitor_asins=[theirs])— multi mode returns shared keywords + which ones competitors rank top-40 for that you don't. This is the highest-signal call per token; prefer it over multiple Cerebro pulls. - Seed expansion:
get_keywords_by_keyword("stun gun")— related phrases from a seed when there's no good competitor ASIN yet (new product research). - Fresh angles:
get_keywords_new_suggestionfor terms recently gaining volume around an ASIN. - Score a finalized list:
analyze_keywords([...])— batch metrics for candidate lists from any source (brainstorm, PPC search terms, etc.).
Phase 2 — Filter & prioritize
Score each candidate on:
- Volume — floor of ~300/mo for copy targets; no floor for backend terms.
- CPR — units needed in 8 days for page-1 top half. CPR ≤ 15 = cheap ranking push; flag these separately, they're the actionable list.
- Relevance — does the phrase describe THIS product? (Ranking for a near-miss term brings clicks that don't convert and hurts CVR.)
- Trend — 30-day search-volume trend; a +30%/mo term at 500 volume beats a flat 800.
- Competition texture — exact title-match count (low = title opportunity), CPC (proxy for commercial intensity).
Phase 3 — Output: the keyword map (per ASIN)
- Primary (2–4): highest volume × relevance → title + first bullets.
- Secondary (5–10): remaining bullets, description/A+.
- Backend (~250 bytes): everything indexable that doesn't fit copy — no brand names, no commas needed, no repeats of title words.
- Push list: CPR ≤ 15 terms with current rank 5–20 → hand to ads/promo.
- Tracker list: primaries + push list → for the user to add to Helium 10 Keyword Tracker (UI-only; no API write) so rank history starts accruing.
Route: copy targets → listing-guard (draft → approval → PATCH), measurement → impact-tracker baseline, coverage re-check → next store-audit.
Gotchas (learned in production)
- Variation siblings share keyword data — research the family head, not each child.
time_period=YYYY-MMon Cerebro gives one historical month per call (24-month lookback) — useful for seasonality checks before Q4 bets.- A keyword you rank #6–9 on is worth more than a new one at #80: check current rank before chasing volume (get_top_keywords single mode shows your ranks).
- Quota: a focused research session ≈ 5–10 calls of the 1,000/period. The trap is Cerebro-ing every competitor "to be thorough" — the gap call usually answers the question in one.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

