evidence-verification

To verify claims with primary sources during competitor analysis, the Skill enforces strict citation of official API documentation, product announcements, and developer guides. It distinguishes facts from inferences, ensuring all stated features or pricing are backed by vendor documentation.

The best way to fact-check industry trends using official documentation is to enforce mandatory primary source citation for all factual statements. This process clearly labels and flags any analysis not directly supported by vendor documentation to prevent speculation.

To distinguish facts from inferences when assessing market trends, the Skill scopes application to market trend assessment and explicitly flags all speculative analysis. It ensures verifiable data by requiring official documentation, press releases, and academic papers for factual statements.

Yes, you can use this to enforce citation of official API documentation for architectural comparisons. The Skill scopes application to architectural comparisons and satisfies requirements for verifiable data by strictly enforcing primary source citation.

The limitation of using blog posts for verifying factual claims about external products is that they are not primary sources. The Skill prevents the spread of misinformation by enforcing strict citation of official documentation, press releases, and developer guides, flagging any unsupported analysis.