MCPInstall

review-audit

Analyzes positive customer reviews to surface deep customer insights for ad copy. Use this whenever a user provides customer reviews and wants to understand their customers better, extract VOC (voice of customer), find ad-ready language, or build messaging strategy from real customer language. Trigger for any request involving "analyze these reviews," "what are customers saying," "find insights in these reviews," "VOC analysis," or any variation of wanting to mine customer reviews for creative strategy inputs. Output is always organized by product (if multiple), and surfaces five buckets of insight: pain points, trigger moments, objections, transformations, and standout language.

Installs
474
Last 24h
—
Trending rank
—
Security
Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/motion-team/creative-strategy-skills --skill review-audit
  1. 01

    Install

    Run the command in your project. The CLI asks which agents to install for.

  2. 02

    Describe the task

    Ask your agent for something this skill covers. It loads review-audit automatically when relevant.

  3. 03

    Review the result

    The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

Review Audit

This system mines positive customer reviews to extract the insights that make ad copy actually work — the real language, real pain, real moments, and real transformations that customers experienced. The output feeds directly into creative strategy and hook writing.

The goal is not to summarize reviews. The goal is to find the raw material for ads.


What You Need Before Starting

Reviews can be provided in any format:

  • Pasted directly into the chat
  • CSV or spreadsheet upload
  • Copy/pasted from a document

If multiple products are present in the review set, identify them before beginning. All output is separated by product.

If the format is unclear or product attribution is ambiguous, ask before proceeding.


Step 1: Group by Product

If the brand sells multiple products, sort all reviews by product first. Every subsequent step runs separately per product.

If all reviews are for a single product, skip grouping and proceed.


Step 2: Score Review Quality (1–5)

Before analysis, score every review for quality. This determines what gets analyzed and what gets discarded.

ScoreWhat it looks like
1Garbage — gibberish, swear words, 2–3 meaningless words, zero signal ("great product", "love it", "👍")
2Low signal — very short, vague, no specific detail or emotion
3Moderate — mentions the product, some specificity, but no vivid detail or emotional depth
4High quality — specific, describes a real experience, references a before/after or a feeling
5Gold — long, emotional, vivid, paragraph-level detail; the customer was so moved they wrote an essay about it

Score 5 reviews are the priority. They contain the most usable language and the deepest insight.


Step 3: Filter

Discard all reviews scored 1. Do not include them in analysis.

Analyze scores 2–5, with emphasis on 4s and 5s. Low-scoring reviews (2–3) can contribute to pattern identification but should not be the source of pulled quotes.


Step 4: Extract Insights by Bucket

Run this analysis separately for each product. Within each bucket, group similar insights together and write a brief summary of the pattern. Then pull the best word-for-word quotes that exemplify it.

Do not editorialize the quotes. Pull them exactly as written.


Bucket 1: Pain Points

What problem were they experiencing before they found this product?

Look for: descriptions of the problem they had, how long they'd had it, what they'd tried before, how it affected their life, the emotional weight of living with it.

For each pain theme identified:

  • Name the theme
  • Write a 2–3 sentence summary of the pattern across reviews
  • Flag the strongest quotes for the swipe file

Bucket 2: Trigger Moments

What finally made them buy?

Look for: the specific moment, event, or realization that pushed them over the edge. This is the thing that turned a maybe into an add-to-cart. It could be a life event (wedding, diagnosis, vacation), a recommendation (friend, doctor, TikTok), hitting a breaking point, or running out of patience with other solutions.

For each trigger theme identified:

  • Name the theme
  • Write a 2–3 sentence summary of the pattern
  • Flag the strongest quotes for the swipe file

Bucket 3: Objections Before Purchasing

What almost stopped them from buying?

Look for: skepticism they mention having had, comparisons to other products they'd tried, price hesitation, disbelief that this would actually work, fear of wasting money again.

Note: In positive reviews, objections are almost always mentioned in past tense — "I was skeptical but..." or "I almost didn't try it because..." These are gold for objection-handling ad copy.

For each objection theme identified:

  • Name the theme
  • Write a 2–3 sentence summary of the pattern
  • Flag the strongest quotes for the swipe file

Bucket 4: Transformations

What changed for them after using the product?

Look for: the specific result they experienced, how their life is different now, the emotional shift (confidence, relief, freedom, pride), and — most importantly — how they describe the transformation in their own words. The more specific and visceral, the better.

For each transformation theme identified:

  • Name the theme
  • Write a 2–3 sentence summary of the pattern
  • Flag the strongest quotes for the swipe file

Bucket 5: Standout Language & Ad-Ready Phrases

Exact language worth stealing for ads.

This bucket is different from the others. It is not organized by theme — it is a curated collection of the most vivid, emotionally charged, specific, and scroll-stopping phrases pulled from across all buckets. These are the lines that made you stop while reading. The ones that don't need to be rewritten. The ones a copywriter would highlight and build an ad around.

Pull these verbatim. Note which product they're from.

What to look for:

  • Unusually specific descriptions of pain or transformation
  • Phrases that capture an emotion in a way you couldn't have written yourself
  • Before/after language that is visceral and concrete
  • Lines that could work as a hook with zero editing
  • Anything that made you feel something while reading it

Output Format

Produce a separate full output for each product. Structure:

─────────────────────────────────────
PRODUCT: [Product Name]
Reviews analyzed: [X] | Discarded (score 1): [X]
─────────────────────────────────────

BUCKET 1: PAIN POINTS

[Theme Name]
Summary: [2–3 sentences on the pattern]

[Theme Name]
Summary: [2–3 sentences on the pattern]

---

BUCKET 2: TRIGGER MOMENTS

[Theme Name]
Summary: [2–3 sentences on the pattern]

---

BUCKET 3: OBJECTIONS BEFORE PURCHASING

[Theme Name]
Summary: [2–3 sentences on the pattern]

---

BUCKET 4: TRANSFORMATIONS

[Theme Name]
Summary: [2–3 sentences on the pattern]

---

BUCKET 5: STANDOUT LANGUAGE & AD-READY PHRASES

"[Exact quote]"
"[Exact quote]"
"[Exact quote]"
[etc.]

─────────────────────────────────────

All word-for-word quotes are collected in Bucket 5. Do not scatter quotes throughout buckets 1–4 — keep the summaries clean and let the swipe file be the dedicated place for raw language.


How This Feeds the Rest of the Stack

The output of this analysis plugs directly into creative strategy and execution:

  • Pain Points → Creative Strategy Engine — pain buckets map directly to the pain/desire anchor layer
  • Trigger Moments → Hook Writing — trigger moments are often the most powerful hook material; they capture the exact moment of emotional readiness
  • Objections → Hook Writing / Creative Mechanics — objections inform Borrowed Enemy, Reframe, and Risk Reversal mechanics and hook tactics
  • Transformations → Hook Writing — transformation language feeds aspirational and social proof hooks
  • Standout Language → Hook Voice Patterns — the best phrases can be added directly to the swipe file as native voice patterns pulled from real customers

Notes on Quality

  • Score 5 reviews should be read in full and treated as primary sources
  • Score 2–3 reviews are useful for pattern confirmation but not quote sourcing
  • If the review set is small (under 20 reviews), note this — patterns may not be statistically meaningful but language is still usable
  • If a product has too few quality reviews to surface meaningful patterns, flag it rather than manufacturing themes that aren't there

FAQ

What does the review-audit skill do?

Analyzes positive customer reviews to surface deep customer insights for ad copy. Use this whenever a user provides customer reviews and wants to understand their customers better, extract VOC (voice of customer), find ad-ready language, or build messaging strategy from real customer language. Trigger for any request involving "analyze these reviews," "what are customers saying," "find insights in these reviews," "VOC analysis," or any variation of wanting to mine customer reviews for creative strategy inputs. Output is always organized by product (if multiple), and surfaces five buckets of insight: pain points, trigger moments, objections, transformations, and standout language.

How do I install review-audit?

Run npx skills add https://github.com/motion-team/creative-strategy-skills --skill review-audit in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/review-audit/ (personal) or .claude/skills/review-audit/ (project).

Which AI agents can use review-audit?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is review-audit safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains review-audit?

It is published by motion-team in motion-team/creative-strategy-skills. It has 474 recorded installs.

More from motion-team/creative-strategy-skills

View all →

hook-writing

motion-team/creative-strategy-skills

Writes high-converting, psychologically-driven hooks for paid ads, TikTok, Instagram Reels, and organic content. Use this whenever a user wants to write hooks, opening lines, scroll-stoppers, or attention-grabbing openers for ads or social content. Trigger for any request involving "write me hooks," "give me hooks for," "I need hooks for my ad," "TikTok hooks," "hook ideas," or any variation of wanting compelling opening lines for advertising or social content. Also use when a user provides a product, persona, messaging angle, or awareness stage and wants tactical hook execution — especially when used downstream from the Creative Strategy Engine.

Docs & Writing622 installs

creative-strategy-engine

motion-team/creative-strategy-skills

Strategic framework for mapping pain/persona intersections and messaging angles. Defines the structure for organizing creative strategy, not the tactics for execution. Use this when planning an organizational or systematic approach to creative strategy, or when a user provides a product and wants to define messaging angles, write strategic hooks, or execute ads in visual formats defined by awareness and decision stages.

Media & Creative531 installs

creative-mechanics

motion-team/creative-strategy-skills

A library of creative mechanics — the structural patterns that define how an ad constructs meaning between its hook, visuals, and narrative. Use this whenever designing ad concepts, briefing creative, or trying to explain why a specific ad works beyond just its hook or format. Trigger when a user describes an ad they saw and wants to understand or replicate what made it work, when building a creative concept from a messaging angle, or when execution needs more than a hook and a format — it needs a structural idea. Creative mechanics sit between hooks and visual formats in the Creative Strategy Engine: hooks say what, formats show how, mechanics define the cognitive or emotional mechanism that makes the concept land. Always pair with Hook Writing for opening line execution and Hook Tactics for tactic classification.

Media & Creative529 installs

visual-formats

motion-team/creative-strategy-skills

A reference library of 45+ visual ad formats for Meta and paid social, each with a definition, funnel stage guidance, and medium (video/static/both). Use this whenever choosing how an ad should look and feel, building out a creative concept, writing a creative brief, or deciding which format best serves a messaging angle and awareness stage. Trigger when the user asks "what format should this be," "how should we execute this," "give me concept ideas," or any time a creative concept needs a production structure. Always pair with creative-mechanics to fully flesh out the concept — format defines the vessel, mechanic defines the cognitive move inside it. Either can come first; they work in both directions.

Media & Creative489 installs

hook-tactics

motion-team/creative-strategy-skills

Reference library of 35+ hook and headline tactic types. Use this when a user asks for hooks organized by tactic, wants to know which tactic to use for a given situation, or requests hooks "by tactic type." This defines what each tactic is and when to deploy it. Always pair with hook-writing for execution — tactics define the frame, psychological triggers are the mechanism inside the frame.

DevOps & Cloud488 installs

brand-intake

motion-team/creative-strategy-skills

Open the skill to read its SKILL.md instructions.

Marketing & SEO468 installs

Popular code quality & workflow skills

View category →

grill-me

mattpocock/skills

A relentless interview to sharpen a plan or design.

Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.

handoff

mattpocock/skills

Compact the current conversation into a handoff document for another agent to pick up.

domain-modeling

mattpocock/skills

Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.

codebase-design

mattpocock/skills

Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.

diagnosing-bugs

mattpocock/skills

Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.