fact-checking

To automate fact-checking for technical claims, this skill generates counter-hypotheses and tests them against available data, outputting structured reviews with claims, statuses, and evidence. It triggers automatically during architecture decisions or when claims contain superlatives.

Counter-hypothesis testing for accuracy verification is a mechanism that generates alternative hypotheses to validate technical claims. It tests these hypotheses against available data to ensure the accuracy of technical content, references, and API endpoints.

To verify URLs and API endpoints during a technical review, the skill performs evidence verification against available data. It structures the output by formatting reviews with the original claims, validation statuses, and verified evidence.

Yes, this fact-checking skill requires access to external references and APIs to verify package names, URLs, and API endpoints. It relies on these external data sources to test counter-hypotheses and validate technical claims.

You should use counter-hypothesis testing for quality assurance when reviewing deliverables, verifying technical claims, or performing quality assurance on outputs. It is particularly useful for validating architecture decisions and claims containing thresholds.