shopify-review-triage
Turn public 1-3-star Shopify App Store review rows into a P0-P3 triage brief: incident risk, repeated friction, pricing confusion, feature requests, and an explicit needs-human-read bucket.
Profile →npx skills add sickn33/agentic-awesome-skills --skill shopify-review-triage --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
What it does
Turn public 1-3-star Shopify App Store review rows into a P0-P3 triage brief: incident risk, repeated friction, pricing confusion, feature requests, and an explicit needs-human-read bucket.
How it works
The skill analyzes public Shopify App Store reviews to classify each row into one primary category (P0, P1, P2, P3) based on keyword matching, with secondary keywords recorded if present. It requires owners list first, then accepts one review per line in a specific format, preserving the original source URL when present. It does not fetch data or introduce new data. It enforces hard rules about not fabricating evidence, not making promises, and not contacting reviewers. It guides a human pass to verify and reproduce issues before finalizing.
When to use it
Use when you need triaged, prioritized, or clustered low-star reviews for Shopify apps to determine incident risk, repeated friction, pricing confusion, or feature requests, without claiming exhaustiveness or making promises.
What it can touch
Not provided in this summary.
Caveats
Public review text only; no invented evidence; keyword outputs are for first pass and require human validation; no coverage claims; no promises about outcomes. Reviewers are referred to as people, not individuals; ensure ownership rules (owned vs competitors) are applied during triage.
# Shopify Review Triage — public low-star reviews to a P0–P3 brief ## Overview Takes rows of **public** Shopify App Store review text and produces one prioritized brief a product or support owner can act on: what kind of problem each review describes, how badly it can hurt, what to do first, and where the original wording came from. It is built for independent Shopify app teams and the agencies that run their support — the case where low-star reviews arrive scattered across several listings plus a few watched competitors, and the failure mode is treating them all as equally urgent. The rubric below is not invented here. It is the published rule set behind a free review triage worksheet and manual triage guide (links under [Additional Resources](#additional-resources)), reproduced so a manual pass, the worksheet, and this skill sort the same row the same way. This skill needs no network access, no scripts, and no system packages. The person you are helping supplies the review text. ## When to Use This Skill - Use when someone wants app store reviews, low-star reviews, or merchant feedback triaged, prioritized, or clustered — even when they never say "triage", "severity", or "P0". -
- Overview
- When to Use This Skill
- Hard Rules
- How It Works
- Step 1: Collect the rows
- Step 2: First pass — apply the rubric
- Step 3: Human pass — verify before you promote anything
- Step 4: Write the brief
- Step 5: Self-check before you hand it over
- Examples
- Example 1: Worked example — eight rows in, first pass out
- Example 2: A row that carries its source link
- Best Practices
- Limitations
What does the shopify-review-triage skill do?
Turn public 1-3-star Shopify App Store review rows into a P0-P3 triage brief: incident risk, repeated friction, pricing confusion, feature requests, and an explicit needs-human-read bucket.
How do I install it?
Run `npx skills add sickn33/agentic-awesome-skills --skill shopify-review-triage --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From sickn33/agentic-awesome-skills, a repository with 44,414 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.