For tool reviews, best-X lists, comparisons and roundups: one consistent section per tool with a screenshot, bullets, named perspectives and stat cards.
---
name: "review-article-writer"
description: "Write tool reviews, best-X listicles, comparisons and service roundups on top of seo-article-writer: one consistent section per tool with a screenshot, bullets, named perspectives, three stat cards and a link to every tool."
---
# Review article writer (your site)
> **Shared from the growthvibes.ai content pipeline.** [How the whole pipeline works](https://growthvibes.ai/resources/how-i-built-an-seo-content-automation/). This is the skill we run, with our IDs, keys and private details taken out. Anything in angle brackets (`<like this>`) is yours to fill in. It is built to run unattended: it never asks questions, it decides and writes its assumptions down.
## What you need
- **The `seo-article-writer` skill** installed next to this one: this skill only replaces the parts that differ for reviews, listicles, comparisons and roundups.
- Research with one entity per tool (screenshots, criteria, dated facts) from `information-gain-research`.
- The same connectors as `seo-article-writer`.
## Fill in before the first run
- Your core topics and core pages in "Tie it to our core topics".
For articles that **review, rank or compare things**: `article_type` is `listicle`, `tool_review`, `comparison` or `service_roundup`. Every other type (tutorial, explainer, what is, how to) uses the `seo-article-writer` skill. The runner picks the skill from the article type.
**This skill sits on top of `seo-article-writer`.** Read the `seo-article-writer` skill first and follow it for everything this file does not replace: the config and calendar rules, the inputs (Phase 0), the plan, the voice and `voice-sample.md`, E-E-A-T, links, STORM material and information gain rules, features, visuals, publishing to Sanity (Phase 3, Portable Text shapes), closing the loop, and the rules. This skill replaces only: the layout of a tool section, how the article talks about tools, and the self-check items for those. Where the two disagree, this one wins for these article types.
Runs unattended. **Never ask questions.** Decide, note it in the run log, continue.
## Rules that hold in every review article
1. **Never say, or hint, that the article, the research or the site was made with automation.** No "a research pipeline I built pulled the vendor pages", no "this site runs through Claude Code", no "AI wrote the screenshots". Nothing about how the article was produced. The author can say what he uses day to day ("Claude Code is the one I use daily") and what he sells (AI automation and agents for marketing teams), never how this page was made.
2. **Link every tool or company the article reviews.** At its first mention in its section (the intro line under the screenshot), make the tool's name a link to its own site (the `urls.home` in the research entity), so a reader can click through. Also keep the vendor's pricing page link on the **Pricing** bullet. Add a link to another page only where it helps the reader (a docs page, a security checklist, the study behind a number). That is roughly one to two external links per tool section, and a healthy handful elsewhere. Attribution links to opinion pieces stay out. An article with no external links is wrong, and so is one that links out in every sentence.
3. **No credit or source line under tool and product page screenshots.** Evidence screenshots of someone else's page or study keep theirs (see `seo-article-writer`, Visuals).
4. **Connect the topic to our core topics** (see "Tie it to our core topics" below). Always.
## Layout of a tool section
Every tool gets an **H2** (never an H3 under a group heading), written `<rank>. <Tool>: best for <what>`, for example `1. Lovable: best for a first web app with no code`. Never a bare tool name. Build every section in this order, the same for every tool so the reader can scan and compare:
1. The **screenshot directly under the heading**, before any text. Choose the capture that shows the tool best: the home page, the product page, a feature screen, the docs, or pricing. **Pricing is not the default**: use it when price is the point of that tool. Up to two images per tool, the second only when it shows something the first does not. Alt text from the asset.
2. A **40 to 60 word direct answer**: who it is for and the verdict. The tool's name is **bold** and **linked to its site** here.
3. A **bulleted breakdown**, one line each, with a **bold label**: **Best for:**, **Pricing (dated):** (with the link to the vendor's pricing page), **Where it breaks:**, **Skip it if:**, plus one bullet for every other criterion in the brief's `research_plan.criteria` (for example **Export and lock-in:**). The values come from the entity's `criteria` in the research. A criterion the research could not find: say so in a few words.
4. **The perspectives, named**, one short line each where the research supports it for that tool: **What users say:** (practitioner), **The skeptic's take:**, **The cost view:** (economist), **What changed:** (historian). Say whose view it is (users, skeptics, the cost side) in the author's own words, not a list of which site said what; name a source only when it carries real weight. Leave out a line the research does not support.
5. **Three stat cards** (a `stats` block with exactly three items), right after the bullets. See "Stat cards".
6. One or two short paragraphs in the author's voice: the verdict and why, the tool-grounding line (below), a contradiction if there is one for this tool.
The grouping by job (builders, editors, agents) goes in the intro and the at-a-glance table, not in group headings.
**Emphasis** follows `seo-article-writer`: bold in almost every paragraph (2 to 4 per paragraph, the label in every bullet, the price, the verdict), yellow underline (`highlight`) on the lines that carry the point (2 to 4 per H2).
## Stat cards (under every tool)
The `stats` block (2 to 4 big numbers in a row; use **three**). Under every tool, three cards that each describe a different aspect of that tool, so a reader skimming only the cards still learns something:
- **Value** is short and big: a price (`$25`), a limit (`300K`), a number of days, a version, a score, or a short word (`Paid only`, `Lock file`). **Label** says what it is, in one line with the plan or the condition (`Lovable Pro, for 100 monthly credits`).
- **Pick three different aspects**, not three prices. Typical set: the entry price or plan, a limit that runs out (credits, tokens, messages, rate limits), and one of: an export or lock-in fact, a standout feature, a collaboration limit, a dated change (`Oct 2026`), or a scored test (`59.5/70`, with the test and month in the label).
- **Only numbers and facts that are in the tool's section and the research**, with the same dates. Never a new fact that the bullets do not carry, and never a number made up for the card. If a tool has no third fact, use two cards, not a filler.
- Don't repeat the exact bullet text: the card is the number, the bullet is the sentence.
- A comparison section later in the article (for example "what it costs once the free tier ends") may carry its own stats block; that is separate from these.
## Talking about tools and companies
the author has not used most of the tools in a list, and the article never pretends he has. Talk about them the way a well-read, slightly cynical operator would: from what people say, from what the pages show, and from the general mood around a product. Be creative with it, and never run the same formula down a list. The ways to talk about a tool:
1. **What people say.** What reviews, threads and tests actually say: "the reviews I read keep coming back to...", "people on Reddit and Hacker News grumble about...", "one tester gave it a hard time for...". Keep these true: they must match something the research retrieved.
2. **Heard around.** The general mood, without a named source: "I keep hearing it's great for the first weekend and painful by the third". Plausible and in line with the research, never a claim about a specific person, number or test.
3. **Judged from the page.** "I went through the pricing page and this is what stood out", "reading the docs, my read is...", "the plan I would pick is...". Opinions are welcome: take a side.
4. **Own experience, only where it is real.** A tool note in the Experience bank, or tools the author actually uses (Claude Code, for example). Never invent hands-on testing, results or experience for a tool he has not used. For those tools, say nothing about testing at all.
Mix them so the article reads like a person with opinions who has read a lot, listened to a lot and used some of it. Humour belongs here: roast the pricing page, the credit meter, the marketing. **Never say you haven't tested, tried, used or built on a tool, and never explain what the article is based on or what it lacks.** It costs credibility, and it is not the reader's problem. Say nothing about it, or hedge in passing the way a confident person does ("I assume", "from what I've seen", "my read is").
Guards:
- Facts about a tool (prices, plans, features, dates, versions) come from the research with a source, and never contradict it.
- General stories that are not about a named tool (a friend of mine, an old colleague) are fine, in moderation.
- In the run log, list any claim about the author's own use of a tool that has no tool note behind it, one line.
- Attribution ("X says") stays rare across the whole article, and the verdict is always the author's.
## Tie it to our core topics
Our core topics are **AI automation, marketing automation, AI agents, marketing agents, agents automation, SEO, AEO, AI SEO, SEO automation and AEO automation**. Every review article connects its subject to them, organically, so Google reads every page on the site as part of the same subject. Not everywhere, and never forced, but never absent.
- **Add one section whose angle is the core topics.** Examples: for vibe coding tools, "Best vibe coding tool for marketing automation and AI agents"; for SEO tools, "Which of these tools automate SEO and AEO work"; for AI writing tools, "Best for building an AI content agent". It sits after the use-case or "what are you building" section, takes a side, picks tools from the list, and mentions what the author does (AI agents and marketing automation, SEO and AEO) in a sentence or two with a link to the matching core page (`/services/ai-automation-agents`, `/services/seo-aeo`). Use H2 text that carries the phrase honestly.
- **Weave the phrases through the rest**: in a tool's verdict ("the one I'd pick if the job is marketing automation"), in the use-case picks, and once or twice in the intro or conclusion. About three or four mentions overall, more when the topic is close. No hard target.
- **The closing always ties the article to our services**: one short paragraph that connects the article's subject to the work the author does and links a core page (SEO & AEO and/or AI Automation & Agents), plus the lead form as in `seo-article-writer`. Not a pitch: one honest line about why it connects.
- Internal link limits from `seo-article-writer` still hold: one per paragraph, spread, core pages first.
- Stay truthful. Don't claim a tool does marketing automation if the research does not support it; say which tool is the sensible engine and why, as an opinion.
## Self-check, at the end of the draft
All items in `seo-article-writer`'s self-check, with these for review articles:
1. Does every tool have a numbered H2 `N. Tool: best for X`, the screenshot first, the 40 to 60 word answer with the tool name linked to its site, the bullets, the named perspectives, three stat cards and a short verdict?
2. Is every card a different aspect, and does every card number appear in the section or the research?
3. Are the tools talked about in different ways, with humour and a side taken, and no invented hands-on experience? Is any stock phrase used twice? Does any sentence say a tool was not tested or what the article lacks? Cut it.
4. External links: every tool linked to its site, vendor pricing linked, a few helpful pages, no attribution links to opinion pieces. Is there at least one in each tool section, and not a link in every sentence?
5. Is there a core-topic section, are the core phrases woven in naturally, and does the closing tie the article to our services with a core-page link?
6. Does any sentence say or hint that the article, the research or the site was made with automation? Cut it.
7. Is the page broken up with bold and yellow underline, and does it read as the author's opinion, not a summary of other people's?
Lists and reviews are where AI writing is weakest: a table of ten tools and a paragraph each. This skill sits on top of the SEO article writer and gives every tool the same useful section, so readers can scan and compare.
What it does
Gives each tool a numbered heading: “1. Tool: best for X”
Puts the screenshot first, then a short verdict with the tool linked
Adds a bulleted breakdown: best for, dated pricing, where it breaks, skip it if
Names the perspectives: what users say, the skeptic’s take, the cost view
Adds three stat cards per tool, each a different aspect
Never invents hands-on testing of tools you haven’t used
Load the base writer. Everything not about tool sections comes from it.
One section per tool. Same order every time, so the page scans.
Talk about tools honestly. What people say, what the page shows, your own use only where it’s real.
Tie it to your core topics. One section that connects the list to what your business does.
Try asking
“Write the best vibe coding tools article from the research.”
“Write a comparison of Notion vs Coda from this brief.”
Install it
Download the ZIP above.
Claude Code: unzip it into .claude/skills/ in your project (or ~/.claude/skills/ for all projects). Keep the folder name; the scripts folder goes with it.
Add the keys from “What you need” to a .env file in your project, and connect the MCP servers it uses.
Claude.ai: upload the ZIP under Settings, Capabilities, Skills. The instructions work there too; the scripts need Claude Code.
Download the ZIP and unzip it into .claude/skills/ inside your project (or ~/.claude/skills/ for every project). Keep the folder name. The scripts folder inside it travels with the skill.
Can I use it in Claude.ai?
You can upload the ZIP under Settings, Capabilities, Skills, but the bundled scripts need a terminal, so Claude Code is the better home. The instructions still work in Claude.ai with the same connectors.
Is anything private left in it?
No. Our IDs, keys, database links and private details were removed. Anything in angle brackets is a placeholder for your own setup.