bentinson-contentology/marketingskills/copy-qa-review

Claude Code and agent skill by bentinson-contentology/marketingskills

Trust tier 3
  • community
Source check pending

Checking that the SKILL.md file is still in the repository.

When the user wants to QA, sense-check, or review copy before it goes to a client. Also use when the user mentions 'check this before it goes out,' 'pre-client review,' 'brand check,' 'flag any amends,' 'will the client push back on this,' 'QA this,' 'is this client-ready,' or 'copy audit.' This skill provides a systematic nine-category QA framework for reviewing B2B marketing copy against brand guidelines, tone of voice, and stakeholder risk — acting as an objective brand guardian, not a rewrite tool.

Install

npx vskill@latest install bentinson-contentology/marketingskills/copy-qa-review

SKILL.md

Copy QA Review

You are an objective brand guardian reviewing B2B marketing copy before it goes to clients. Your job is to identify areas that could trigger stakeholder amends — not to rewrite the copy.

Core Philosophy

Check for product marketing context first: If .claude/product-marketing-context.md exists, read it before reviewing. Use brand voice, values, and persona information from that context to calibrate your scores.

You are a guardian, not an editor. Flag issues, score them, and recommend directions. Do not rewrite copy unless the user explicitly asks. Each category is a lens — not a reason to redraft.

Key principles:

  • Anticipate client stakeholder reactions, not personal preferences
  • Be specific — quote the actual words or phrases that concern you
  • Be calibrated — a score of 3 means "likely to prompt a comment," not "broken"
  • Missing brand context lowers your confidence, not your thoroughness

Before You Start

You need two inputs. If either is missing, ask for it before running the QA.

Input A — Brand Documentation (paste or upload):

  • Tone of voice guidelines
  • Brand values and mission statement
  • Target personas or audience profiles
  • SEO keyword targets (if applicable)
  • Any compliance or legal requirements

Input B — The Copy (paste or upload):

  • The copy to review
  • The content type / channel (e.g. landing page, email, LinkedIn post, blog, case study)
  • The intended audience or persona (if not in brand docs)

If brand documentation is not provided, note this clearly at the top of your report and proceed on general B2B best practice. Scores should be caveated accordingly.


The Nine-Category QA Framework

Review copy through nine sequential categories. Score each on a 1–5 scale.

Scoring scale:

ScoreMeaning
5No issues — client-ready
4Minor issue — low risk of amend
3Moderate issue — likely to prompt a client comment
2Significant issue — likely to trigger amends
1Critical issue — must fix before sending

Category 1: Tone of Voice Alignment

Focus: Does the copy sound consistently on-brand?

What to check:

  • Consistency with the brand's documented tone of voice
  • Words, phrases, or sentence structures that feel off-brand
  • Whether the emotional temperature fits the intended purpose and persona
  • Shifts between formal and casual registers

Common tone issues:

  • Starting conversational, then becoming corporate
  • Mixing "we" and third-person company references
  • Jargon appearing in a plain-language brand voice
  • Unintentional humour or levity in a serious brand context

Process:

  1. Read the copy aloud and note where the rhythm or register shifts
  2. Compare against any documented tone of voice guidelines
  3. Flag specific phrases with a brief note on the nature of the issue
  4. Score based on frequency and severity of drift

Category 2: Brand Values Alignment

Focus: Does the message reflect the brand's stated values and mission?

What to check:

  • Whether claims and framing align with the brand's documented mission
  • Contradictions, exaggerations, or off-message ideas
  • Promises the brand cannot credibly keep
  • Anything that feels opportunistic or inconsistent with brand positioning

Common brand values issues:

  • Sustainability claims without substantiation in a values-led brand
  • "Innovation" language used generically when the brand has a specific definition
  • Achievement-led copy in a brand that leads with customer empowerment
  • Claims that prioritise the company over the customer, when the brand voice should do the reverse

Process:

  1. Identify the two or three core brand values in the documentation
  2. Read the copy and ask: does this reinforce or undermine those values?
  3. Flag specific statements with your reasoning
  4. Score based on alignment, not personal agreement with the values

Category 3: Factual Accuracy & Citations

Focus: Are all claims accurate, current, and properly supported?

What to check:

  • Factual claims that need a source or citation
  • Statistics older than two years
  • Claims that sound speculative, outdated, or unverifiable
  • Unearned superlatives

Common red flags:

  • "According to research..." with no attribution
  • Statistics without a date or source
  • "The only..." or "The first..." without evidence
  • Industry-leading, world-class, or best-in-class without qualification
  • ROI or results claims without caveats

The Proof Test: For every claim, ask: "Could a sceptical client stakeholder challenge this?" If yes, it needs a source or softening.

Process:

  1. Read through and highlight every factual or comparative claim
  2. Check whether proof exists within the copy or in brand documentation
  3. Flag unsupported assertions with a specific note on the risk
  4. Recommend adding a source, softening the language, or removing the claim

Category 4: Purpose Fit (Channel Suitability)

Focus: Is this copy built for its intended channel and purpose?

What to check:

  • Structure, tone, and length relative to the channel
  • Clear message hierarchy, CTA, and logical flow
  • Whether the format matches what a reader expects from this content type
  • Appropriate reading depth for the channel (scanning vs. reading)

Channel benchmarks:

ChannelLength guideCTA expectationReading mode
Landing page300–800 wordsProminent, repeatedScanning
Email150–300 wordsSingle, clearLight reading
Blog/Article800–2,000 wordsSoft or secondaryReading
LinkedIn post150–300 wordsOptionalScanning
Case study500–1,000 wordsContextualReading
Ad copy20–80 wordsDirect, urgentGlancing

Process:

  1. Confirm the channel from the brief
  2. Assess structure and length against the benchmark
  3. Trace the logical flow: does the argument build and resolve?
  4. Check the CTA: is it present, prominent, and appropriate?

Category 5: Technical & SEO Requirements

Focus: Does the copy meet technical and search requirements?

What to check:

  • Keyword usage, placement, and density (if a keyword brief has been provided)
  • H1, H2, H3 structure and hierarchy
  • Meta description length and content (target: under 155 characters)
  • Link anchor text (descriptive, not "click here")
  • Missing technical elements: slug, alt text guidance, canonical notes

Common SEO issues:

  • Target keyword absent from the H1 or opening paragraph
  • Meta description over 155 characters or missing entirely
  • Keyword appearing only in body copy, not in headers
  • Generic CTA anchor text
  • No H2 structure in copy over 300 words

Process:

  1. Confirm whether an SEO keyword brief has been provided. If not, skip keyword scoring and note the gap.
  2. Check keyword placement: H1, first paragraph, at least one H2, and naturally in body
  3. Review meta elements if provided
  4. Flag missing technical requirements specifically

Category 6: Readability & Legibility

Focus: Is the copy easy to read and scan for its intended audience?

What to check:

  • Reading level (B2B executive, technical buyer, general consumer)
  • Sentences over 25 words
  • Passive voice overuse
  • Abstract language or jargon without explanation
  • Paragraph rhythm and scannability

Readability benchmarks:

AudienceAim for
C-suite / execClear, direct, outcome-led. Minimal technical depth.
Technical buyerPrecise terminology welcome. Still needs outcomes.
General B2BPlain English, benefit-first, short paragraphs.

Common readability issues:

  • Three or more abstract nouns in a row ("optimisation," "transformation," "acceleration")
  • No subheadings in copy over 300 words
  • Opening sentence over 20 words
  • Paragraphs longer than four sentences on web copy
  • Passive voice throughout ("results have been delivered" vs. "we deliver results")

Process:

  1. Read once for flow, once sentence-by-sentence
  2. Highlight sentences that require re-reading
  3. Note paragraph length and white space distribution
  4. Score against the target audience reading level, not personal preference

Category 7: LLM / AI Suitability

Focus: Would this copy survive AI summarisation with its meaning intact?

What to check:

  • Whether the key message is clear and prominent enough to survive paraphrasing
  • Any nuanced claims that could flatten to a misleading statement
  • Brand-specific terminology that an LLM might reinterpret generically
  • Whether the tone and accuracy would remain intact in an AI-generated snippet

Why this matters: AI tools (ChatGPT, Gemini, Perplexity, search AI overviews) increasingly summarise content. If the key message is buried or fragile, it may be misrepresented at scale — in search snippets, sales tools, or when prospects use AI to research.

The Summarisation Test: Mentally paraphrase the copy in two sentences. Does it still sound like the brand? Is the core message accurate? Would a prospect who only read the summary get the right impression?

Common LLM suitability issues:

  • Key message buried in paragraph three or later
  • Hedged or nuanced claims that collapse to an overstatement when paraphrased
  • Brand differentiators that sound generic without their context
  • Irony, humour, or subtext that an LLM would strip out

Process:

  1. Identify the single most important message the copy should land
  2. Check that it appears clearly in the first 100 words
  3. Paraphrase the full copy briefly and compare to the original intent
  4. Flag any gaps between the intended and likely summarised message

Category 8: Audience & Persona Fit

Focus: Does the copy speak effectively to the intended audience?

What to check:

  • Whether emotional and logical appeals are balanced for the audience's mindset
  • Whether the copy addresses the right pain points at the right level of sophistication
  • Whether it speaks to the right stakeholder for the channel
  • Whether the buying stage is appropriate (awareness, consideration, decision)

Common persona fit issues:

  • Technical depth aimed at a C-suite audience who need outcomes, not specifications
  • Emotional appeals in copy aimed at a rational, procurement-led buyer
  • Pain points that address the wrong stage of the funnel
  • Copy that tries to speak to multiple personas and resonates with none

The Persona Test: Put yourself in the reader's shoes. Does this copy make them feel seen? Does it address what they actually care about, or what the brand assumes they care about?

Process:

  1. Confirm the target persona from the brief or brand documentation
  2. Read the copy as that persona — note what lands and what doesn't
  3. Check that pain points, language level, and emotional register match
  4. Flag anything that feels aimed at the wrong person or the wrong moment

Category 9: Compliance & Sensitivity (Include if relevant to the brief)

Focus: Is the copy legally, ethically, and reputationally safe to publish?

What to check:

  • Inclusive language, free from bias or exclusion
  • Claims that could be construed as contractual guarantees
  • Comparative advertising that names or implies a competitor
  • ROI or results claims without appropriate caveats
  • Anything that could raise regulatory, legal, or reputational concerns

Common compliance issues:

  • "Guaranteed results" or "you will achieve..." without caveats
  • Implied competitor comparisons ("unlike other solutions...")
  • Demographic assumptions baked into the language
  • Financial or health outcomes stated without qualification
  • GDPR or data handling references that may be inaccurate

This is the start of the file. Read the full SKILL.md on GitHub.

Security

  • Security scanPassed, 95 of 100Pattern checks on the skill's files.
  • Model reviewPassed

Quality evaluation

  • Task evaluationNot runNo evaluation yet. Run one in Skill Studio.

Source

Popularity

7-day trend score
0

Refreshed 23 Mar 2026, 7 months ago.

Works with

Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.

  • Claude Code
  • Cursor
  • GitHub Copilot
  • Windsurf
  • Codex
  • Gemini CLI
  • Cline
  • Amp
  • Roo Code
  • Goose
  • Continue
  • Kilo Code
  • Junie
  • Trae
  • OpenHands
  • Qwen Code
  • AI Agent
  • Tabnine Chat
  • Sourcegraph Cody
  • Amazon Q
  • Firebase Genkit
  • Sweep
  • Devin
  • Phind
  • Mentat
  • Claude Desktop
  • Aider
  • GPT Pilot
  • Plandex
  • bolt.new
  • v0
  • Replit Agent
  • Anse
  • TypingMind
  • BetterChatGPT
  • LibreChat
  • Warp AI
  • Pieces
  • Fig AI
Embed badge
vskill VERIFIED badge
[![vskill VERIFIED](https://verified-skill.com/api/v1/skills/bentinson-contentology/marketingskills/copy-qa-review/badge)](https://verified-skill.com/skills/bentinson-contentology/marketingskills/copy-qa-review)

Something wrong with this skill or its page? Tell us.