/verify-claims

name: verify-claims
description: "Verify marketing claims. Use when: cross-checking statistics, awards, certifications, or performance claims with sources."
argument-hint: "[content-path]"

/digital-marketing-pro:verify-claims

Purpose

Cross-check marketing claims against user-provided evidence data. Extracts all verifiable claims from content — statistics, percentages, rankings, awards, certifications, named citations, performance metrics, customer counts, and time-bound assertions — then matches each against an evidence file and classifies it as verified, partially verified, unverified, or contradicted. This command is the dedicated deep-dive for claim integrity, while /digital-marketing-pro:eval-content includes claim verification as one dimension of its broader quality assessment.

Marketing content that cites specific numbers, awards, or results without verified backing is a brand risk. Contradicted claims erode trust if caught by customers, journalists, or regulators. This command ensures every factual assertion in your content is backed by real data, clearly sourced, and defensible under scrutiny.

Input Required

The user must provide (or will be prompted for):

• **Content with claims**: The text to verify — provided inline, as a pasted block, or as a file path. Any marketing content that makes factual assertions: landing pages, case studies, press releases, ad copy, pitch decks, investor materials, product pages, or client reports
• **Evidence file** (optional but strongly recommended): A JSON file containing source data to verify against. Format: `[{"claim": "descriptive claim text", "source": "data source name or URL", "date": "YYYY-MM-DD when verified", "verified": true/false, "value": "the verified number or fact"}]`. Can be exported from GA4, CRM, sales data, certification bodies, or assembled manually. If not provided, the command operates in extraction-only mode and guides the user on creating an evidence file
• **Specific claim to check** (optional): A single claim to focus on instead of scanning the full content — useful for quick spot-checks on a particular statistic or assertion

Process

1. **Load brand context**: Read `~/.claude-marketing/brands/_active-brand.json` for the active slug, then load `~/.claude-marketing/brands/{slug}/profile.json`. Apply compliance rules for target markets (`skills/context-engine/compliance-rules.md`) — some industries and regions have stricter requirements for substantiating claims (financial services, healthcare, EU consumer protection). Also check for guidelines at `~/.claude-marketing/brands/{slug}/guidelines/_manifest.json` — if present, load messaging restrictions that may define approved claims and prohibited assertions. Check for agency SOPs at `~/.claude-marketing/sops/`. If no brand exists, ask: "Set up a brand first (/digital-marketing-pro:brand-setup)?" — or proceed with defaults. 2. **Extract claims from content**: Execute `python "${CLAUDE_PLUGIN_ROOT}/scripts/claim-verifier.py" --action extract-claims --text "{content}"` to identify all verifiable assertions. The extractor categorizes claims by type:

• **Statistical claims**: Percentages, ratios, growth numbers, market size figures ("73% increase in conversions," "4.8x ROAS")
• **Ranking claims**: Position assertions, comparative statements ("market leader," "#1 rated," "fastest-growing")
• **Award and certification claims**: Named awards, industry certifications, compliance badges ("ISO 27001 certified," "G2 Leader")
• **Named citation claims**: Attributed quotes, source references, study citations ("according to Gartner," "Forrester reports")
• **Performance claims**: Customer counts, time-bound results, SLA promises ("10,000+ customers," "results in 30 days")
• **Temporal claims**: Date-specific assertions, recency claims ("as of 2026," "latest data shows")

3. **Verify claims against evidence**: If an evidence file is provided, execute `python "${CLAUDE_PLUGIN_ROOT}/scripts/claim-verifier.py" --action verify --text "{content}" --evidence {evidence_file}`. For each extracted claim, the verifier:

• Attempts to match the claim to an evidence entry by semantic similarity and claim type
• Classifies the match result: **Verified** (claim matches evidence within acceptable tolerance), **Partially verified** (claim is directionally correct but specific numbers differ, or the source date is stale), **Unverified** (no matching evidence entry found), or **Contradicted** (evidence directly conflicts with the claim)
• Assigns a confidence score (0-100) to each verification based on match quality, source recency, and specificity alignment

4. **Handle missing evidence file**: If no evidence file is provided, skip the verification step. Instead, present all extracted claims with their types and flag each as "unverified — no evidence provided." Guide the user on creating an evidence file:

• Explain the JSON format with examples for each claim type
• Suggest data sources: GA4 for performance metrics, CRM for customer counts, certification bodies for awards, published reports for industry statistics
• Offer to generate a template evidence file pre-populated with the extracted claims (values left blank for the user to fill)

5. **Detail contradictions**: For each contradicted claim, present a side-by-side comparison: the claim text as written in the content, the evidence data that conflicts, the specific discrepancy (e.g., "content says 73% increase, evidence shows 61% increase"), and the potential impact of publishing the incorrect claim (reputational, regulatory, competitive). 6. **Recommend corrections**: For unverified and contradicted claims, provide specific recommendations:

• **Contradicted claims**: Suggest corrected text using the evidence value, with hedging language options if exact figures are sensitive ("approximately," "over X," "nearly Y")
• **Unverified claims**: Suggest adding source attribution, softening abso