Verify copy claims by script against evidence you give; without it, lists what needs proof.

MITAuto-check passedResearch & Science

Install Verify Claims

skills CLI
$ npx skills add indranilbanerjee/digital-marketing-pro --skill verify-claims -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install indranilbanerjee/digital-marketing-pro verify-claims --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/indranilbanerjee/digital-marketing-pro.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/verify-claims .claude/skills/verify-claims && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
verify-claims
GitHub stars
862
Used in
1 other repo
Token cost
~2.3k tokens
SKILL.md length
1,157 words
Files
1
Skills in repo
162
Repo updated
First seen
Licence
MIT

At a glance

Verify copy claims by script against evidence you give; without it, lists what needs proof.

  • Works in 7 steps: Load brand context: Read… → Extract claims from content: Execute… → Verify claims against evidence: If an… → …
  • Tasks that involve Fact-checking and source verification
  • SKILL.md covers Purpose, Input Required, Process and Output, plus 1 more section
  • Calls python

What it does

Verify Claims is an agent skill from indranilbanerjee/digital-marketing-pro. Verify copy claims by script against evidence you give; without it, lists what needs proof. "can we back up these numbers"

Its SKILL.md is about 2.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Research & Science, covering Fact-checking and source verification. The repository describes itself as: An open-source AI marketing operating system for strategy, SEO, AEO/GEO, paid media, content, CRM, and analytics - grounded in brand context, human approval, and verifiable… The licence is MIT.

When your agent uses it

  • Tasks that involve Fact-checking and source verification

Example prompts

  • “can we back up these numbers”
  • “/verify-claims”

Requirements

  • Python 3

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

  1. Load brand context: Read ~/.claude-marketing/brands/_active-brand.json for the active slug, then load…
  2. Extract claims from content: Execute python "${CLAUDE_PLUGIN_ROOT}/scripts/claim-verifier.py" --action extract-claims --text "{content}"…
  3. Verify claims against evidence: If an evidence file is provided, execute python "${CLAUDE_PLUGIN_ROOT}/scripts/claim-verifier.py" --action…
  4. Handle missing evidence file: If no evidence file is provided, skip the verification step. Instead, present all extracted claims with…
  5. Detail contradictions: For each contradicted claim, present a side-by-side comparison: the claim text as written in the content, the…
  6. Recommend corrections: For unverified and contradicted claims, provide specific recommendations
  7. Generate verification summary: Produce an overall verification score (percentage of claims verified or partially verified), a risk…

What it can do on your machine

Read from SKILL.md and the folder at commit 9e949f3. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • python

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Verify Claims loads about 2.3k tokens when it runs. Until then it costs about 34 tokens; SKILL.md has 1,157 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~34
When it runs · the whole SKILL.md, loaded when a task matches
~2.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from indranilbanerjee/digital-marketing-pro at commit 9e949f3, republished under its MIT licence (© indranilbanerjee). 1,157 words, ~2,332 tokens.

Download SKILL.mdSave it as .claude/skills/verify-claims/SKILL.md (or your agent's skills folder).
name
verify-claims
description
Verify copy claims by script against evidence you give; without it, lists what needs proof. "can we back up these numbers"
argument-hint
[content-path]

/digital-marketing-pro:verify-claims

Script location. If your host does not set ${CLAUDE_PLUGIN_ROOT}, the scripts are in this plugin's scripts/ folder, next to skills/.

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 absolute statements to qualified ones, or removing the claim until evidence is available
    • Stale evidence: Flag claims where the evidence date is more than 12 months old and recommend refreshing the data
  7. Generate verification summary: Produce an overall verification score (percentage of claims verified or partially verified), a risk assessment based on the number and severity of contradicted and unverified claims, and a compliance note if the brand operates in a regulated industry where unsubstantiated claims carry legal risk.
Show full SKILL.md (335 more words)Show less

Output

A structured verification report containing:

  • Verification score: Percentage of claims that are verified or partially verified — the headline metric for content claim integrity
  • Claims inventory: Total claims extracted, broken down by type (statistical, ranking, award, citation, performance, temporal) — showing the scope of factual assertions in the content
  • Per-claim verification results: For each claim:
    • The claim text as it appears in the content, with location
    • Claim type classification
    • Verification status: Verified, Partially verified, Unverified, or Contradicted
    • Evidence match: The specific evidence entry it was checked against (if any), with source and date
    • Confidence score (0-100) for the verification
    • Issue details: For partially verified or contradicted claims, the specific discrepancy
    • Recommended action: Keep as-is, update with correct value, add source attribution, soften language, or remove
  • Contradiction details: Side-by-side comparison for each contradicted claim — content text vs. evidence data, with the specific discrepancy highlighted and corrected text suggestion
  • Unverified claims list: All claims with no matching evidence, grouped by risk level (high-risk: specific numbers and absolute statements; moderate-risk: comparative claims and rankings; low-risk: general qualitative assertions)
  • Stale evidence warnings: Claims where the supporting evidence is older than 12 months, with a recommendation to refresh the data
  • Corrected text suggestions: For each claim needing correction, the original text and one or more replacement options — an exact-value version using the evidence data and a hedged version with qualifier language
  • Evidence file template: If no evidence file was provided, a pre-populated JSON template with all extracted claims ready for the user to fill in verified values and sources
  • Compliance notes: If the brand operates in a regulated industry (financial services, healthcare, legal, insurance), specific regulatory requirements for claim substantiation with references to relevant rules (FTC Act, EU Consumer Rights Directive, ASA CAP Code, industry-specific regulations)

Agents Used

  • quality-assurance — Claim extraction from content using pattern matching and NLP heuristics, claim-to-evidence matching with semantic similarity and type alignment, verification status classification with confidence scoring, contradiction detection with discrepancy quantification, correction text generation with hedging options, and compliance-aware risk assessment for regulated industries

© indranilbanerjee, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/verify-claims of indranilbanerjee/digital-marketing-pro.

Open the folder on GitHubat commit 9e949f3

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in indranilbanerjee/digital-marketing-pro, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Verify Claims next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Verify Claims compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Verify Claims this skillindranilbanerjee/digital-marketing-pro8621 repos~2.3kAutomated safety check: PassMIT
Perplexity Web Searchdavila7/claude-code-templates33k11 repos~3.5kAutomated safety check: NotesMIT
Citation Verification GuideGalaxy-Dawn/claude-scholar5.7k2 repos~1.9kAutomated safety check: PassMIT
Article Fact Checkerdigoal/blog8.6k—~939Automated safety check: PassGPL-2.0
Deep Research Agent TeamImbad0202/academic-research-skills51k—~13kAutomated safety check: PassCustom licence
Docs Grounding Verifiermicrosoft/apm4k—~1.9kAutomated safety check: PassMIT

Similar skills

  • Perplexity Web Search

    davila7/claude-code-templates

    Runs web-grounded searches through Perplexity's Sonar models over OpenRouter for current events, recent literature and cited facts beyond the model's training cutoff.

    33k GitHub starsUsed in 11 repos~3.5k tokens
    Research & ScienceAuto-check: notes
  • Citation Verification Guide

    Galaxy-Dawn/claude-scholar

    Reference guidance for checking every citation in academic writing against canonical sources such as DOI, arXiv, CrossRef and Semantic Scholar, to catch fake or wrong references.

    5.7k GitHub starsUsed in 2 repos~1.9k tokens
    Research & ScienceAuto-check passed
  • 三层审查模型,逐段逐句验证文章真伪、证据链与逻辑结构。Use when the user asks to fact-check, verify, audit, or evaluate the credibility of an article, essay, report, opinion piece, social-media post, or any written claim —…

    8.6k GitHub stars~939 tokensUpdated 2 days ago
    Research & ScienceAuto-check passed
  • Deep Research Agent Team

    Imbad0202/academic-research-skills

    Runs a 13-agent pipeline for rigorous academic research, from forming the question through systematic search, synthesis, bias checks and an APA 7.0 report.

    51k GitHub stars~13k tokensUpdated yesterday
    Research & ScienceAuto-check passed
  • Official

    A skill your agent uses to verify CLAIM-LEVEL grounding of a documentation page (or set of pages) against the source code.

    4k GitHub stars~1.9k tokensUpdated yesterday
    Research & ScienceAuto-check passed
  • Fact Checking

    bradygaster/squad

    Review and validate claims using counter-hypothesis testing.

    3.3k GitHub stars~503 tokensUpdated yesterday
    Research & ScienceAuto-check passed

More from indranilbanerjee/digital-marketing-pro

All 162 skills in this repo
  • Import Template

    indranilbanerjee/digital-marketing-pro

    Import a deliverable template as a reusable placeholder template per brand.

    862 GitHub starsUsed in 1 repo~1.6k tokens
    Auto-check passed
  • Ab Test Plan

    indranilbanerjee/digital-marketing-pro

    Plan an A/B test by script: sample size per variant, days to run, stopping rules.

    862 GitHub starsUsed in 1 repo~1.9k tokens
    Auto-check passed
  • Aeo Audit

    indranilbanerjee/digital-marketing-pro

    Run a one-time AEO audit of six AI answer engines, scored per surface.

    862 GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed
  • Agent Readiness Audit

    indranilbanerjee/digital-marketing-pro

    Audit agent readiness by script: AI-crawler rules, product schema, no-JS HTML, feeds.

    862 GitHub starsUsed in 1 repo~3.7k tokens
    Auto-check passed
  • Backlink Gap

    indranilbanerjee/digital-marketing-pro

    Find backlink gap domains linking to competitors, not you, scored by script.

    862 GitHub starsUsed in 1 repo~2.6k tokens
    Auto-check passed
  • C2pa Metadata

    indranilbanerjee/digital-marketing-pro

    Embed C2PA provenance in AI-generated images, video or PDF by script.

    862 GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed

Questions about Verify Claims

What does Verify Claims do?

Verify copy claims by script against evidence you give; without it, lists what needs proof. Verify Claims is an agent skill from indranilbanerjee/digital-marketing-pro. Verify copy claims by script against evidence you give; without it, lists what needs proof.

When should I use Verify Claims?

Verify Claims fits situations like: tasks that involve Fact-checking and source verification.

How do I install Verify Claims in Claude Code?

Run `npx skills add indranilbanerjee/digital-marketing-pro --skill verify-claims -a claude-code`. Or copy the skill folder (skills/verify-claims in indranilbanerjee/digital-marketing-pro) into .claude/skills/verify-claims in your project. Claude Code loads it when a task matches its description.

How do I install Verify Claims in Codex?

Run `npx skills add indranilbanerjee/digital-marketing-pro --skill verify-claims -a codex`. Or copy the skill folder (skills/verify-claims in indranilbanerjee/digital-marketing-pro) into .agents/skills/verify-claims in your project. Codex loads it when a task matches its description.

Can I use Verify Claims in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add indranilbanerjee/digital-marketing-pro --skill verify-claims -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/verify-claims, .gemini/skills/verify-claims, .github/skills/verify-claims and .opencode/skills/verify-claims in your project.

What does Verify Claims need to run?

Going by SKILL.md and its folder, Verify Claims needs the command-line tools its instructions call (python). Our summary lists: Python 3.

Does Verify Claims access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Verify Claims safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Verify Claims use?

Verify Claims is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Verify Claims use?

About 2.3k tokens (SKILL.md is roughly 9.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Verify Claims?

Skills that share tags, products or a category with Verify Claims: Perplexity Web Search (davila7/claude-code-templates, 33k stars), Citation Verification Guide (Galaxy-Dawn/claude-scholar, 5.7k stars), Article Fact Checker (digoal/blog, 8.6k stars) and Deep Research Agent Team (Imbad0202/academic-research-skills, 51k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Verify Claims?

indranilbanerjee (a GitHub user) maintains it in indranilbanerjee/digital-marketing-pro, which has 862 GitHub stars. The repository holds 162 skills in this directory. The repository was last updated on October 9, 2026.

Source: indranilbanerjee/digital-marketing-pro on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.