app-store-analyzer
Skill1 starsChanged 7 months agoMITView on GitHub
Analyze app store reviews, ratings, and feedback for product insights. Use when processing app reviews, tracking sentiment, or mining user feedback from app stores.
In this repository26 other files it gives its agents.
- AGENTS.mdAGENTS.md
- brainstormingSkill
- competitor-trackerSkill
- continual-learningSkill
- decision-loggerSkill
- exec-communicatorSkill
- experiment-designerSkill
- experiment-writeupSkill
- growth-loop-mapperSkill
- jtbd-extractorSkill
- knowledge-updaterSkill
- launch-postSkill
- launch-readinessSkill
- meeting-to-actionsSkill
- metric-storytellerSkill
- one-pagerSkill
- pptx-creatorSkill
- prd-writerSkill
- prioritization-scorerSkill
- retro-runnerSkill
- stakeholder-updateSkill
- strategy-connectorSkill
- user-interview-synthSkill
- what-ifSkill
- working-backwardsSkill
- writing-clearlySkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 16
After a release to gauge reception
- Distinctive: line 17
Before planning to understand user pain
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
App Store Analyzer
Mine app store reviews and ratings for actionable product insights. A consumer/mobile-specific skill that turns the firehose of user reviews into structured themes, feature requests, and bug reports.
When to Use
- "Analyze our app reviews"
- "What are users saying in the app store?"
- "Process these reviews"
- "What are the top complaints?"
- After a release to gauge reception
- Before planning to understand user pain
- To monitor competitor app reviews
Process
1. Ingest Reviews
Accept reviews in any format:
- Pasted text from app store
- Exported CSV or text file
- A description ("look at our last 50 one-star reviews")
Capture for each review:
- Rating (1-5 stars)
- Date
- Review text
- Platform (iOS / Android)
- Version (if available)
2. Classify Each Review
Tag each review with:
Sentiment: positive / neutral / negative / mixed
Category:
- Bug report — something is broken
- Feature request — user wants something new
- UX complaint — flow or design friction
- Performance — speed, battery, crashes
- Praise — something they love
- Churn signal — user says they're leaving or switching
- Onboarding — new user confusion
Severity (for negative reviews):
- Blocker — user can't complete core task
- Frustration — user can do it but hates the experience
- Annoyance — minor irritation
3. Theme Extraction
Group reviews into themes:
- Frequency — how many reviews mention this theme
- Trend — is this theme growing, stable, or declining?
- Rating correlation — do 1-star reviews cluster around specific themes?
- Platform split — is this iOS-only, Android-only, or both?
4. Prioritize Findings
Rank themes by:
- Volume × severity — many users × blocker = top priority
- Trend direction — growing complaints are more urgent than stable ones
- Rating impact — themes that disproportionately drive 1-star reviews
- Churn signal strength — themes where users explicitly mention leaving
5. Connect to Product
Map findings to:
- Existing backlog items (
knowledge/products/*/roadmap.md) - Known bugs or issues
- Recent releases that may have caused changes
- Competitor advantages mentioned in reviews
6. Store Insights
Write to memory/feedback/YYYY-MM-DD_app-store-[topic].md
Output
## App Store Analysis: [Product]
**Date:** YYYY-MM-DD
**Reviews analyzed:** [count]
**Period:** [date range]
**Average rating:** [X.X] (trend: ↑/↓/→)
### Rating Distribution
| Stars | Count | % | Trend |
|-------|-------|---|-------|
| 5 ⭐ | [n] | [%] | ↑/↓/→ |
| 4 ⭐ | [n] | [%] | ↑/↓/→ |
| 3 ⭐ | [n] | [%] | ↑/↓/→ |
| 2 ⭐ | [n] | [%] | ↑/↓/→ |
| 1 ⭐ | [n] | [%] | ↑/↓/→ |
### Top Themes
| Rank | Theme | Mentions | Avg Rating | Trend | Category |
|------|-------|----------|------------|-------|----------|
| 1 | [theme] | [n] | [X.X] | ↑/↓/→ | [category] |
### Critical Issues (Blocker + High Volume)
- **[Issue]**: [count] mentions, avg [X.X] stars — [summary]
### Feature Requests (Most Requested)
- **[Feature]**: [count] mentions — [what users want and why]
### What Users Love (Protect These)
- **[Strength]**: [count] mentions — [why they love it]
### Churn Signals
- [count] reviews mention switching or leaving
- Top reasons: [reasons]
### Recommended Actions
| Priority | Action | Theme | Expected Impact |
|----------|--------|-------|-----------------|
| P0 | [action] | [theme] | [impact on rating/retention] |Principles
- 1-star reviews are product roadmaps — they tell you what's broken
- 5-star reviews are moats — they tell you what to protect
- Trends > snapshots — a growing problem is more urgent than a big stable one
- Cross-reference with data — reviews are qualitative; pair with analytics for the full picture
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.

