claims-validator

Detects inflated or unsupported claims in text and generates a structured report.

175|26|Updated Aug 14, 2025
One-click install
npx skills add https://github.com/jmagly/ai-writing-guide --skill claims-validator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: claims-validator
Source: https://github.com/jmagly/ai-writing-guide/tree/main/.factory/skills/claims-validator
Command: npx skills add https://github.com/jmagly/ai-writing-guide --skill claims-validator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill eliminates misleading claims by automatically scanning documentation for unsupported metrics, made-up statistics, and unverifiable statements.

Core Features & Use Cases

  • Claims Validation: Automatically identifies percentage claims without data, time estimates without basis, and feature descriptions for unimplemented capabilities.

Quick Start

When you say "check for unsupported claims", this Skill analyzes your documentation for:

  • Performance metrics without benchmarks
  • Time/cost estimates without methodology
  • Marketing superlatives presented as facts
  • Features described as implemented that don't exist in the codebase.

Example Output

"Claims Validation: README.md

Found 8 unsupported claims:

Metrics (4):

  • Line 204: '20-98% reduction' - no data
  • Line 362: '56-63% time saved' - no data
  • Line 366: '2 Minutes' in heading - varies by project

Recommendation: Remove these claims. Describe what features do, not how much time/money they save."

Frequently Asked Questions about claims-validator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I identify unsupported claims in documentation?

Documentation claims validation automatically scans for unsupported metrics, unverified statistics, and unsubstantiated statements. It flags performance percentages without benchmarks, time estimates without methodology, and feature descriptions for unimplemented capabilities, then returns a structured report with remediation recommendations.

What types of claims does documentation validation catch?

Claims validation detects performance metrics lacking data, time or cost estimates without basis, marketing superlatives presented as facts, comparative claims without evidence, and features described as implemented that don't exist in the codebase. It traces each flagged claim to its source line.

Can I validate claims across multiple documentation files and codebases?

Yes, claims validation scans documentation for unsupported metrics and unverifiable statements across sources and codebases. It identifies citation validity issues and cross-references feature assertions against actual implementation, returning traceable evidence sources for each claim.

Why should I automate claims validation instead of manual review?

Automated claims validation eliminates manual review overhead by systematically identifying misleading metrics, made-up statistics, and unverifiable statements at scale. It reduces human error and catches inconsistencies between documented claims and actual codebase capabilities.

What output does a claims validation report provide?

The validation report details each unsupported claim by type—metrics, time estimates, feature assertions—with line numbers, evidence of why claims lack support, and recommended remediations. Results are structured for actionable documentation fixes and compliance tracking.