facts-check

Verify facts, API compatibility, and dependency versions with source reporting.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/towry/dots --skill facts-check
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: facts-check
Source: https://github.com/towry/dots/tree/main/conf/claude-local-marketplace/skills/facts-check
Command: npx skills add https://github.com/towry/dots --skill facts-check

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill facilitates fact-checking, API compatibility verification, and dependency/version validation to prevent incorrect assumptions and outdated knowledge in your designs and implementations.

Core Features & Use Cases

  • External Verification: Check library versions, API methods, and documentation for accuracy.
  • Codebase Verification: Validate presence and signatures of internal modules and data structures.
  • Best Practices: Cross-check current best practices and deprecations before you code.

Quick Start

Use a combination of web searches and code-context checks:

  • Verify a library version exists and is current.
  • Validate an API method usage with example.
  • Cross-check a configuration against official docs.

Frequently Asked Questions about facts-check

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

FAQPage Schema
How do I verify that a library version is current and compatible with my project?

Dependency version verification checks whether a library exists, identifies its current release, and validates compatibility with your codebase. This prevents integration failures from outdated or mismatched versions before implementation.

Can I validate API methods and their signatures before writing code?

API compatibility checks confirm method names, parameters, and return types against live documentation and code context. This catches breaking changes and deprecated APIs before you integrate them.

What's the best way to cross-check facts and best practices against official documentation?

External verification combines web searches with codebase validation to confirm library capabilities, data schemas, and current best practices. Structured reporting with sources delivers a validated assessment of accuracy.

Why should I verify dependencies and APIs before starting implementation?

Pre-implementation checks prevent incorrect assumptions about external APIs and library versions that lead to failed integrations and rework. Dual verification through code context and documentation ensures confidence in your design decisions.

Can I validate internal modules and data structures alongside external dependencies?

Codebase verification uses AST-based analysis and code-context checks to validate presence and signatures of both internal modules and external APIs within your project, delivering comprehensive fact-checking.