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.