Agent skill · writing content · github
shopify-review-triage
Use this skill when someone wants public Shopify App Store reviews, low-star reviews, or merchant feedback triaged, prioritized, clustered, or turned into a product or support brief. Trigger for prompts like "triage these app store reviews", "what should we fix first from this feedback", "cluster our 1-star reviews", or "write a weekly low-star review brief", for a single Shopify app or a portfolio plus watched competitors. Produces a P0-P3 brief covering incident risk, repeated friction, pricing confusion, feature requests, and an explicit needs-human-read bucket, where every item keeps its public source link and stays labeled first pass or human-checked. Do not trigger for support tickets, order data, or any other private merchant data, and never use it to reply to or contact a reviewer.
Why this skill is useful
Provides a structured method for triaging public Shopify App Store reviews, which the AI wouldn't reliably generate on its own.
What it needs
About 11k tokens when loaded. Last updated 2026-08-07. 37,534 stars on the source repository.
What this skill does
Shopify review triage - public low-star reviews to a P0-P3 brief What this does 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 reproduces a publicly published rule set verbatim, so a manual pass and this skill sort the same row the same way. See Provenance for the source. Hard rules These are not style preferences. Breaking one makes the output worse than nothing. 1. Public review text only. Never accept, request, or copy support tickets, merchant emails, order data, personal contact details, internal telemetry, or anything else not already public on a listing page. If such data appears in the input, stop, say which rows are affected, and ask for them to be removed before continuing. 2. Never invent evidence. Do not write a review, a rating, a date, an app name, or a source URL that was not supplied. A row with no link gets source: not captured - never a guessed one. 3. Keyword output is a sort, not a verdict. Everything produced by the rubric alone is labeled first pass - not human-checked. Only a person who read the review and checked it against their own systems may relabel an item human-checked. 4. Reviews are customer reports, not verified defects. Write "the reviewer reports the editor showed a blank screen", never "the editor is broken". The distinction survives into the brief. 5. No coverage claims. The brief covers exactly the rows supplied and says so. Make no claim of exhaustive coverage of a listing, a period, or an app. 6. No promises. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills github/shopify-review-triage