How do I install the Docs Validating Factual Accuracy skill?

Run npx skillmds add wahidyankf/docs-validating-factual-accuracy in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Docs Validating Factual Accuracy safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Docs Validating Factual Accuracy?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Docs Validating Factual Accuracy free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Docs Validating Factual Accuracy?

wahidyankf (@wahidyankf) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Docs Validating Factual Accuracy by wahidyankf

Name: Docs Validating Factual Accuracy
Rating: 4.2 (5 reviews)
Author: wahidyankf

Docs Validating Factual Accuracy

Universal methodology for verifying factual correctness in documentation using WebSearch and WebFetch tools. Covers command syntax verification, version checking, code example validation, API correctness, confidence classification system ([Verified], [Error], [Outdated], [Unverified]), source prioritization, and update frequency rules. Essential for maintaining factual accuracy in technical documentation and educational content

wahidyankf 9d45719 10 files · 19.3 KB Updated Sep 10, 2026

File contents

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

See The Four Confidence Classifications for the full [Verified] / [Error] / [Outdated] / [Unverified] definitions with examples of each.

Validation Workflow

See Step-by-Step Validation Workflow for the six-step process from identifying claims through documenting a finding, with a worked npm-flag example.

Source Prioritization

See Source Prioritization for the four-tier source hierarchy — official documentation, package registries, official release notes, and well-maintained community sources — with examples and when to use each.

Common Validation Patterns

See Common Validation Patterns for four worked patterns: command syntax, version number, code example, and API method validation.

Update Frequency Rules and Metadata

See Update Frequency Rules and Metadata Storage for the mandatory and optional re-validation triggers and the external-links-status.yaml metadata format.

Integration with Checker Agents

See Integration with Checker Agents for the dual-label pattern (verification + criticality), confidence assessment levels, the three agents that implement this methodology, and when to delegate research to web-researcher.

Common Mistakes and Best Practices

See Common Mistakes and Best Practices for the five most common validation mistakes, the pre-publish validation checklist, the batch validation workflow, and the WebSearch/WebFetch tool usage pattern.

Reference Documentation

Primary Convention: Factual Validation Convention

Related Conventions: Content Quality Principles, Criticality Levels, Timestamp Format

Related Skills: repo-assessing-criticality-confidence - dual-label system and priority matrix

Related Agents: docs-checker, docs-tutorial-checker, apps-ayokoding-www-facts-checker

This Skill packages critical factual validation methodology for maintaining accuracy in technical documentation. For comprehensive details, consult the primary convention document.

---name: docs-validating-factual-accuracydescription: Universal methodology for verifying factual correctness in documentation using WebSearch and WebFetch tools. Covers command syntax verification, version checking, code example validation, API correctness, confidence classification system ([Verified], [Error], [Outdated], [Unverified]), source prioritization, and update frequency rules. Essential for maintaining factual accuracy in technical documentation and educational content---# Factual Validation Methodology Skill## PurposeThis 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 ClassificationsSee [The Four Confidence Classifications](./reference/confidence-classifications.md) for the full`[Verified]` / `[Error]` / `[Outdated]` / `[Unverified]` definitions with examples of each.## Validation WorkflowSee [Step-by-Step Validation Workflow](./reference/validation-workflow.md) for the six-stepprocess from identifying claims through documenting a finding, with a worked npm-flag example.## Source PrioritizationSee [Source Prioritization](./reference/source-prioritization.md) for the four-tier sourcehierarchy — official documentation, package registries, official release notes, andwell-maintained community sources — with examples and when to use each.## Common Validation PatternsSee [Common Validation Patterns](./reference/common-validation-patterns.md) for four workedpatterns: command syntax, version number, code example, and API method validation.## Update Frequency Rules and MetadataSee [Update Frequency Rules and Metadata Storage](./reference/update-frequency-and-metadata.md)for the mandatory and optional re-validation triggers and the `external-links-status.yaml`metadata format.## Integration with Checker AgentsSee [Integration with Checker Agents](./reference/checker-integration.md) for the dual-labelpattern (verification + criticality), confidence assessment levels, the three agents thatimplement this methodology, and when to delegate research to `web-researcher`.## Common Mistakes and Best PracticesSee [Common Mistakes and Best Practices](./reference/mistakes-and-best-practices.md) for the fivemost common validation mistakes, the pre-publish validation checklist, the batch validationworkflow, and the WebSearch/WebFetch tool usage pattern.## Reference Documentation**Primary Convention**: [Factual Validation Convention](../../../repo-governance/conventions/writing/factual-validation.md)**Related Conventions**: [Content Quality Principles](../../../repo-governance/conventions/writing/quality.md), [Criticality Levels](../../../repo-governance/development/quality/criticality-levels.md), [Timestamp Format](../../../repo-governance/conventions/formatting/timestamp.md)**Related Skills**: `repo-assessing-criticality-confidence` - dual-label system and priority matrix**Related Agents**: `docs-checker`, `docs-tutorial-checker`, `apps-ayokoding-www-facts-checker`---This Skill packages critical factual validation methodology for maintaining accuracy in technical documentation. For comprehensive details, consult the primary convention document.

Frequently asked questions