product-research
Skill2 starsChanged 4 months agoMITView on GitHub
Amazon product opportunity research using SellerSprite MCP and LLM reasoning. Use when the user runs `/product-research "{PRODUCT_KEYWORD}" {SITE}` to research a product direction, evaluate market opportunity, competitors, VOC, barriers, and launch decision.
14 other projects use a version of this.
Adopted by
Most recently taken up by
- darkweb19/skillstheir own version, first seen Nov 8, 2026
- ethanratnofsky/skillstheir own version, first seen Nov 8, 2026
- newkirkjosh/skillstheir own version, first seen Oct 25, 2026
- liangdabiao/amazon-sorftime-research-MCP-skilltheir own version, first seen Oct 13, 2026
- alexander-zuev/agent-skillstheir own version, first seen Oct 13, 2026
- rolandtolnay/llm-toolkittheir own version, first seen Oct 11, 2026
Other versions14 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 14
- liangdabiao/amazon-sorftime-research-MCP-skill★ 1.1ksame name
- AlpacaLabsLLC/skills-for-architects★ 420same name
- mlopscommunity/Coding-Agents-Conference-skills★ 38same name
- Hassaan146/claude-skills★ 18same name
- Hussain-Elfalah/Agentic-Skills★ 2same name
- 199-biotechnologies/product-research★ 1same name
- ccgargantua/gars-claude-skills★ 1same name
- mahiunfiltered/claude-code-skills★ 1same name
- newkirkjosh/skills★ 1same name
- rolandtolnay/llm-toolkit★ 1same name
4 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 repository6 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- amazon-analyseSkill
- category-selectionSkill
- keyword-researchSkill
- product-planningSkill
- review-analysisSkill
The file
We split this skill into the rules it gives an agent
9 rules. 0 are common, 7 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 13 edited versions we read keep these.
7
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 20
Before any data call, read references/runtime-credential-preflight.md when it is available.
- Distinctive: line 22
If SellerSprite MCP is not configured, unavailable, or returns an authentication error, ask the user for the SellerSprite MCP API key …
- Distinctive: line 23
If Gemini/GLM validation is part of the requested output and model keys are missing, ask for the missing keys before validation.
- Distinctive: line 24
Do not continue with mock MCP data or fabricated opportunity conclusions.
- Distinctive: line 25
Do not write provided keys into reports, raw files, dashboards, examples, or the open-source repository.
- Very specific: line 29
Read references/sellersprite-mcp-api.md before execution when it is available.
- Distinctive: line 46
If MCP cannot answer a required question, mark the gap and then use a crawl/browser fallback only for that missing evidence.
- Distinctive: line 71
Do not invent supply-chain, patent, compatibility, seasonality, inventory, or certification risks.
- Distinctive: line 81
Do not publish raw product exports or private cost assumptions.
“Common” is measured: kept by at least 6 in 10 of the 13 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Product Research
Command
/product-research "{PRODUCT_KEYWORD}" {SITE}Goal
Evaluate a product opportunity and produce a decision-ready research report.
Credential Preflight
Before any data call, read references/runtime-credential-preflight.md when it is available.
- If SellerSprite MCP is not configured, unavailable, or returns an authentication error, ask the user for the SellerSprite MCP API key before product research.
- If Gemini/GLM validation is part of the requested output and model keys are missing, ask for the missing keys before validation.
- Do not continue with mock MCP data or fabricated opportunity conclusions.
- Do not write provided keys into reports, raw files, dashboards, examples, or the open-source repository.
Required Reference
Read references/sellersprite-mcp-api.md before execution when it is available.
Normalize GB to SellerSprite MCP UK before tool calls.
Data Calls
product_node: map the product direction to relevant Amazon category nodes.product_research: collect candidate products and opportunity-filtered samples.competitor_lookup: compare representative products by keyword, ASIN, brand, seller, node, month, and variation setting.market_researchandmarket_research_statistics: quantify category market size and competition.market_price_distribution,market_rating_distribution,market_product_demand_trend: check pricing, maturity, and demand trend.market_product_concentration,market_brand_concentration,market_seller_concentration: quantify head concentration.keyword_miner,keyword_research,keyword_research_trends: validate keyword demand, CPC/PPC, purchase rate, supply-demand ratio, and trend.traffic_listing,traffic_source,traffic_extend: inspect traffic patterns for representative competitors when available.review: collect VOC from representative ASINs.google_trend: optional external demand validation.trademark_country_list,trademark_list,trademark_stats,trademark_detail: use only for naming/IP/trademark risk checks.
If MCP cannot answer a required question, mark the gap and then use a crawl/browser fallback only for that missing evidence.
Workflow
- Clarify product keyword and site.
- Normalize site code for SellerSprite MCP.
- Collect representative products using
product_researchandcompetitor_lookup. - Collect keyword, category, market distribution, and traffic context from MCP.
- Save raw or compact MCP responses before reasoning.
- Label product attributes: price, rating, reviews, feature, material, scenario.
- Compare opportunity patterns with evidence references.
- Analyze VOC and barriers using review/category/trademark evidence or labeled assumptions.
- Output decision: enter, observe, or reject.
Research Dimensions
| Dimension | Questions |
| Demand | Is there enough search and sales demand? |
| Competition | Are review moats and brands too strong? |
| Differentiation | Can the product be meaningfully improved? |
| Profit | Is price/CPC/return risk acceptable? |
| Supply chain | Is production feasible? |
| Launch path | What keywords and segments should be tested first? |
Do not invent supply-chain, patent, compatibility, seasonality, inventory, or certification risks. Use MCP data first, then existing user files, then explicitly labeled assumptions or crawl evidence.
Output
Save under:
product-research-reports/{PRODUCT_KEYWORD}_{SITE}_{YYYYMMDD}/report.mdDo not publish raw product exports or private cost assumptions.
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.

