app-review-analyzer — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited app-review-analyzer (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Ask the user which mode they need:
opportunities
surface feature requests, and draft professional responses
If the user provides a competitor's app, use Competitive Analysis mode. If they mention "my app" or "our app," use Own App Management mode.
Open the app's store page in Chrome:
Confirm the correct app with the user before proceeding.
Read reviews in two passes:
capture current sentiment.
least 20-30 critical reviews to surface pain points.
For each review, note:
Assign each review to one or more theme categories:
| Category | Signals |
|---|---|
| Bug Reports | Crashes, errors, data loss, freezing, sync failures |
| Missing Features | "I wish it had...", "Why can't I...", "Needs..." |
| UX Complaints | "Too complicated", "Can't find...", "Confusing", "Slow" |
| Pricing Objections | "Too expensive", "Not worth it", "Used to be free" |
| Praise | Specific features users love, "best app for...", loyalty signals |
| Support Complaints | "No response", "Unhelpful", "Can't reach anyone" |
Generate a structured report using the template in references/analysis-report-template.md. The report must include:
frequency
Open your app's store page in Chrome. Confirm the correct app.
Follow the same collection process as Competitive Analysis (Steps 2-3 above).
Score each theme by Frequency x Severity:
| Severity | Definition |
|---|---|
| Critical (3) | Data loss, crashes, security issues, payment failures |
| High (2) | Core functionality broken, major UX blockers |
| Medium (1) | Nice-to-have features, minor annoyances, cosmetic issues |
Calculate priority score: count of reviews in theme x severity weight
Sort themes by priority score descending. This is the fix-first order.
For each negative review (1-3 stars), draft a response following the templates in references/response-templates.md.
Key response principles:
Platform-specific notes:
receive a notification and can update their rating.
policy-violating reviews (spam, off-topic, profanity) via the Play Console.
Generate a report using references/analysis-report-template.md with an additional action plan section:
Use this decision tree when categorizing ambiguous reviews:
Review mentions a crash/error/data loss?
→ Bug Report
Review says "I wish" or "please add" or "why can't I"?
→ Missing Feature
Review says "confusing" or "hard to use" or "can't find"?
→ UX Complaint
Review mentions price, subscription, cost, or payment?
→ Pricing Objection
Review says "no response" or "support" or "help"?
→ Support Complaint
Review is purely positive with no complaints?
→ Praise
Review has multiple themes?
→ Assign all applicable categoriescategory with multiple variants each. Load when drafting review responses.
report output. Load when producing the final report.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.