docs-validating-factual-accuracylisted

# Factual Validation Methodology Skill ## Purpose This Skill provides a universal methodology for verifying factual correctness in technical documentation, educational content, and code examples using WebSearch and WebFetch tools. **When to use this Skill:** - Verifying command syntax and flags - Checking version numbers and compatibility - Validating code examples compile/run correctly - Confirming API methods and signatures - Verifying external claims and references - Classifying confidence levels for documentation - Maintaining factual accuracy in tutorials ## Core Concepts ### What is Factual Validation? **Factual validation** is the systematic process of verifying objective, verifiable claims in documentation against authoritative sources using web search and retrieval tools. **Validates**: - Command syntax (bash, npm, git commands) - Software version numbers - API method names and signatures - Code example correctness - Configuration file formats - Library/package availability - External factual claims **Does NOT validate**: - Subjective quality assessments - Narrative flow or writing style - Architectural decisions or opinions - Future predictions or speculation ### The Four Confidence Classifications All validation findings use one of four confidence labels: **[Verified]** - Objectively correct according to authoritative sources - Command syntax matches official documentation - Version number confirmed via package registry - Code example compiles/runs a