review-analysis
Skill2 starsChanged 4 months agoMITView on GitHub
Amazon review and VOC analysis using SellerSprite MCP. Use when the user runs `/review-analysis {ASIN} {SITE}` to analyze positive and negative reviews, identify product pain points, listing mismatch, service risks, and product improvement actions.
6 other projects use a version of this.
Adopted by
Most recently taken up by
- asospy/asospy-agent-skillstheir own version, first seen Nov 15, 2026
- AppKittie/aso-mcp-skillstheir own version, first seen Nov 8, 2026
- fitlab-ai/agent-infratheir own version, first seen Oct 27, 2026
- Nirusan/claude-configtheir own version, first seen Oct 13, 2026
- liangdabiao/amazon-sorftime-research-MCP-skilltheir own version, first seen Oct 13, 2026
- trysonar/skillstheir own version, first seen Oct 1, 2026
Used with
Projects with it also use growth-analysis, revenue-analysis and 4 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.
asospySkillgrowth-analysis
Explain how an app grew or declined over a period, using ASOSpy installs, revenue, ratings and chart-rank history, and find likely causes in reviews and release dates. Use when the user asks why an app's downloads, revenue or rank changed, or wants a growth timeline. Needs the ASOSpy MCP server.
Also in 3 projects that use this
trysonarSkillrevenue-analysis
When the user wants to estimate or benchmark app revenue and downloads — validating an app idea, sizing a niche, comparing monetization across apps, or reading their own App Store Connect sales on the App Store or Google Play. Also use when the user mentions "how much does this app make", "revenue estimate", "app downloads estimate", "market size", "is this niche profitable", or "my sales". For finding the apps to benchmark, see market-discovery. For full competitor teardowns, see competitor-analysis.
Also in 3 projects that use this
aws-solutionsSkillapp-discovery
Navigates a deployed web application, discovers all pages and interactive elements, and produces a structured discovery report. Use when a test plan or spec needs a map of a live web app's pages, controls and form rules, or the user asks to crawl an app before writing E2E tests. Loads dom-inspection to extract form validation rules, error selectors, and conditional visibility. Used as input to k-light-ui-testing and k-e2e-test-generation workflows.
Also in 3 projects that use this
Kungfookenny123Skillapp-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 3 projects that use this
Kungfookenny123Skillmetadata-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 3 projects that use this
LangChainSkillcompetitor-analysis
Analyze competitors in a given market segment. Trigger on: competitive landscape, competitor analysis, market comparison, competitive positioning.
Also in 4 projects that use this
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- liangdabiao/amazon-sorftime-research-MCP-skill★ 1.1ksame name
- fitlab-ai/agent-infra★ 88same name
- AppKittie/aso-mcp-skills★ 8same name
- Nirusan/claude-config★ 7same name
- asospy/asospy-agent-skills★ 1same name
- trysonar/skills★ 0same name
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
- product-researchSkill
The file
We split this skill into the rules it gives an agent
8 rules. 0 are common, 6 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
6
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 reviews or fabricated VOC conclusions.
- Distinctive: line 25
Do not write provided keys into reports, raw files, examples, or the open-source repository.
- Very specific: line 29
Read references/sellersprite-mcp-api.md before execution when it is available.
- Distinctive: line 54
Only mark an issue as a confirmed pain point when it appears in MCP review evidence or an existing user-provided source.
- Distinctive: line 64
Do not publish raw review dumps or customer-identifying data.
“Common” is measured: kept by at least 6 in 10 of the 4 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
Review Analysis
Command
/review-analysis {ASIN} {SITE}Goal
Turn review data into product decisions: what users love, why users complain, and what should be fixed first.
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 review analysis.
- 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 reviews or fabricated VOC conclusions.
- Do not write provided keys into reports, raw files, 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
asin_detail: product context.reviewwithstarList: [4,5]: positive reviews. Use pagination and record sample size.reviewwithstarList: [1,2,3]: negative reviews. Use pagination and record sample size.- Optional
reviewfilters:typeListfor image/video/VP/vine reviews,startTimestamp,endTimestamp,page,size, andreturnFields. asin_sales_trendandtraffic_keyword: optional context for whether VOC issues correlate with sales or keyword expectation gaps.keepa_info: optional price/rank history context when available.
Save raw or compact review responses before summarization. Do not quote large review dumps in public reports; aggregate themes and keep customer-identifying data out.
Analysis Dimensions
| Dimension | What to Identify |
| Product defect | broken parts, durability, failure |
| Design/function gap | usability, missing function, poor fit |
| Material/appearance | smell, scratches, color, texture |
| Description mismatch | expectation gap from title/images/bullets |
| Service/logistics | used item, missing parts, late delivery |
| Return risk | high-friction issues likely to cause returns |
Only mark an issue as a confirmed pain point when it appears in MCP review evidence or an existing user-provided source. Otherwise label it as a hypothesis.
Output
Save under:
review-analysis-reports/{ASIN}_{SITE}_{YYYYMMDD}/report.mdDo not publish raw review dumps or customer-identifying data.
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.

