How does the Claims Validator identify non-existent features?

The skill scans the documentation for command-line flags, functions, or features mentioned in the prose and cross-references them with the actual codebase to verify their existence.

Can I use this for marketing copy?

Yes, it is specifically designed to catch marketing superlatives and subjective claims, helping you produce more professional and factual technical content.

What kind of metrics does this skill flag?

It flags percentage improvements, time-saving estimates, and cost projections that lack cited benchmarks, methodology, or reproducible data.

Does it automatically fix the documentation?

It does not automatically rewrite your files; instead, it generates a detailed report highlighting specific lines, categorizing the issues, and providing actionable recommendations.

Claims Validator

Name: Claims Validator
Author: jmagly

byjmagly

•

Content Management

Identifies and flags unsupported claims, unverified metrics, and marketing superlatives in documentation to ensure factual accuracy.

About

The Claims Validator skill helps developers and technical writers maintain high-integrity documentation by scanning for unverifiable statements, 'made-up' metrics, and non-existent feature claims. It cross-references described features against the actual codebase, flags percentage-based improvements lacking benchmarks, and identifies marketing 'BS' like subjective superlatives. By generating a detailed validation report with specific remediation steps, this skill ensures your READMEs, guides, and technical copy remain factual, credible, and free from misleading promises.

Key Features

Scans documentation for unsupported percentage and performance metrics
67 GitHub stars
Flags marketing superlatives and subjective comparative claims
Generates detailed validation reports with specific fix recommendations
Detects unverifiable cost and time estimates
Identifies non-existent feature claims by cross-referencing codebase

Use Cases

Reviewing technical documentation for marketing fluff or unrealistic benchmarks
Auditing README files before a public repository launch
Ensuring consistency between documented CLI commands and implemented features

About

Key Features

Scans documentation for unsupported percentage and performance metrics
67 GitHub stars
Flags marketing superlatives and subjective comparative claims
Generates detailed validation reports with specific fix recommendations
Detects unverifiable cost and time estimates
Identifies non-existent feature claims by cross-referencing codebase

Use Cases

Reviewing technical documentation for marketing fluff or unrealistic benchmarks
Auditing README files before a public repository launch
Ensuring consistency between documented CLI commands and implemented features