claims-and-proof-check
Claims & Proof Check
Find every claim in a piece of copy that a buyer, a competitor or a regulator could ask you to back up, and say what to keep on file before it goes live. The principle: a claim you cannot support is a liability, not a selling point.
When to use
Before publishing a landing page, ad, launch email, sales deck, case study or social post that makes claims about results, rankings, competitors, security, compliance, health or AI. Also when a reviewer asks "can we say this?".
Before you start
- Read the brand/product context first. If
.agents/product-marketing.md(or.agents/aaj-brand.md) exists, read it for the product, the audience and the proof points already recorded. If none exists, ask the user what the product is and who it is sold to. - Gather inputs: the exact copy (not a summary of it), the audience - "general", "b2b-saas", "ai", "edtech" or "medtech" - and any evidence or permissions already on file (studies, reports, signed releases, review exports).
- Confirm the objective: a list of claims to support, reword or cut before publishing. This skill flags; it never decides what is legal.
Method
Read the copy one sentence at a time and treat every checkable statement as a claim. Sort each claim by what it needs: proof (numbers, results, rankings, comparisons, security, compliance, health and AI claims), consent (testimonials, named customers, logos, creators) or a wording review (absolutes, guarantees, "free" and deadline offers). For each, name the evidence that would hold up and point to the regulator's own guidance - not a summary of it. I would rather a founder cut a strong-sounding line than publish one they cannot show.