fact-check-note

Audit technical documents line-by-line and produce categorized fact-check reports.

Updated Mar 1, 2026
One-click install
npx skills add https://github.com/CloudyWing/ai-dotfiles --skill fact-check-note
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fact-check-note
Source: https://github.com/CloudyWing/ai-dotfiles/tree/main/skills/fact-check-note
Command: npx skills add https://github.com/CloudyWing/ai-dotfiles --skill fact-check-note

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a structured, honest review of technical documents by identifying incorrect concepts, inconsistent terminology, deprecated API usage, and potentially misleading commands so authors and reviewers can prioritize corrections without assuming uncertainty.

Core Features & Use Cases

  • Concept validation: Checks whether definitions and explanations (e.g., sync vs async) are correctly stated and logically consistent.
  • Terminology consistency: Detects multiple names used for the same concept and flags domain-specific naming issues.
  • API and version checks: Flags method/property names, deprecated APIs, and claims tied to specific versions, marking items that require authoritative verification.
  • Use case: Audit release notes, how-to guides, API reference drafts, or internal technical notes to produce a categorized fact-check report for engineers and technical writers.

Quick Start

Ask the skill to audit the provided technical note and return a categorized report listing confirmed errors, items requiring verification, and suggested corrections.

Frequently Asked Questions about fact-check-note

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

FAQPage Schema
How do I fact-check API documentation for deprecated methods and version-specific claims?

To fact-check API documentation, the skill audits technical documents line-by-line to identify deprecated methods, version-specific claims, and inconsistent terminology, producing a categorized report of confirmed errors and suggested corrections.

What is the best way to verify technical accuracy and flag uncertainties in release notes?

Verifying technical accuracy in release notes involves checking definitions and explanations for logical consistency, flagging unclear commands, and categorizing items requiring external authoritative verification while preserving the original text.

Can I audit internal technical notes for inconsistent terminology automatically?

Yes, you can audit internal technical notes to detect multiple names used for the same concept, flag domain-specific naming issues, and validate whether definitions are correctly stated, generating a structured editorial report.

How do I generate a categorized report of confirmed errors and suggested corrections for code comments?

Generating a categorized report for code comments requires applying a line-by-line audit to identify inaccurate concepts and unclear commands, then outputting a report marking confirmed errors, verification needs, and suggested corrections.

Does fact-checking technical writing preserve the original document text?

Yes, fact-checking technical writing preserves the original text while providing a structured, honest review that identifies incorrect concepts, misleading commands, and items requiring external verification so authors can prioritize corrections.