Agent skill · Code Review & Quality

review-intelligence-digest

Scrape G2, Capterra, and Trustpilot reviews for your product and competitors, then extract recurring themes, objections, proof points, and exact customer language for use in messaging. Chains review-site-scraper with LLM analysis. Produces a weekly or monthly digest that feeds directly into copywriting, positioning, and sales enablement. Use when a marketing team needs to ground messaging in real customer language.

gooseworks-aigithub.com/gooseworks-aiGitHub ↗
claude-codecodexcursorMIT
Install
npx skills add gooseworks-ai/goose-skills --skill review-intelligence-digest --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 7 KB
Bundled scripts: none
Path: skills/research/composites/review-intelligence-digest/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 1,091
Language: Python

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Review Intelligence Digest Scrape reviews for your product and top competitors, then extract what actually matters for marketing: the exact language customers use, recurring pain points, proof points that convert, and objections to pre-empt. **Core principle:** Your best marketing copy is already written — by your customers, in their reviews. This skill surfaces it. ## When to Use - "What are customers saying about us vs competitors?" - "Find proof points and objections from our G2 reviews" - "What language do our customers use to describe the problem we solve?" - "Run a review audit for [client]" - "What are [competitor]'s customers complaining about?" ## Phase 0: Intake 1. Your product name + review page URLs (G2, Capterra, Trustpilot — any/all) 2. Competitor names + their review page URLs (1-3 competitors recommended) 3. What are you trying to learn? (Pick primary focus or do all): - **Messaging mining** — extract ICP language and proof points - **Competitive displacement** — find competitor pain points to exploit - **Objection mapping** — identify what's stopping people from buying/staying - **Feature gaps** — what do customers wish existed? 4. Time range: last 3 months (defa

What's inside
Steps it walks through
  1. When to Use
  2. Phase 0: Intake
  3. Phase 1: Scrape Reviews
  4. Phase 2: Categorize & Cluster
  5. Lens 1: Proof Points (5-star reviews)
  6. Lens 2: Core Pain Language
  7. Lens 3: Objection Mapping (3-4 star reviews, negative cons)
  8. Lens 4: Competitive Displacement Signals (competitor reviews)
  9. Lens 5: Buyer Language Patterns
  10. Phase 3: Output Format
  11. Scheduling
  12. Cost
  13. Tools Required
  14. Trigger Phrases
Ships with 1 file
  • skill.meta.json
Commands it runs
Your product
python3 skills/capabilities/review-site-scraper/scripts/scrape_reviews.py \
Competitor
More from goose-skills
All skills →
About this skill
What does the review-intelligence-digest skill do?

Scrape G2, Capterra, and Trustpilot reviews for your product and competitors, then extract recurring themes, objections, proof points, and exact customer language for use in messaging. Chains review-site-scraper with LLM analysis. Produces a weekly or monthly digest that feeds directly into copywriting, positioning, and sales enablement. Use when a marketing team needs to ground messaging in real customer language.

How do I install it?

Run `npx skills add gooseworks-ai/goose-skills --skill review-intelligence-digest --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 gooseworks-ai/goose-skills, a repository with 1,091 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.

Keep going