docs-validating-factual-accuracy

What problem does it solve?

This Skill eliminates factual errors in technical documentation—including incorrect command syntax, outdated version references, and broken code examples—that cause user frustration, failed workflows, and loss of trust in content.

Core Features & Use Cases

• Four-Tier Confidence Classification: Tag all validation findings with [Verified], [Error], [Outdated], or [Unverified] labels to clearly communicate factual status and urgency.
• Authoritative Source Prioritization: Rely on official documentation, package registries, and official release notes as the highest-authority sources, avoiding unreliable unofficial content.
• Use Case: A team maintaining API documentation can use this Skill to validate all endpoint method signatures against the latest official API reference, catching outdated or incorrect parameters before they reach end users.

Quick Start

Use the docs-validating-factual-accuracy skill to validate the installation command syntax in your project's Getting Started guide and flag any errors with appropriate confidence labels.