skills.rest
JuanTaco4You
JuanTaco4YouCOMMUNITY
Explore all skills by this author →
GitHub

research-verify-before-claim

Verify facts about libraries, tools, commands, or APIs before making recommendations.

Updated Jan 16, 2026
Search Tags:#documentation#libraries#evidence#verify#tools#versions#fact-check
One-click install
npx skills add https://github.com/JuanTaco4You/codex-agent-skills --skill research-verify-before-claim
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: research-verify-before-claim
Source: https://github.com/JuanTaco4You/codex-agent-skills/tree/main/research-verify-before-claim
Command: npx skills add https://github.com/JuanTaco4You/codex-agent-skills --skill research-verify-before-claim

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps ensure recommendations are backed by verified facts from primary sources and local evidence, reducing confident but incorrect guidance.

Core Features & Use Cases

  • Verification workflow: Read official docs and release notes, check local tool outputs, and compare versions.
  • Evidence-based guidance: Provide verifiable evidence and clearly state any remaining uncertainty.
  • Fallback planning: Suggest safe alternatives and cautious defaults when verification is inconclusive.

Quick Start

To start using this skill, begin by validating a claim about a library you plan to recommend, for example verifying the behavior of a CLI tool by checking its --version and reading its official docs.

Frequently Asked Questions about research-verify-before-claim

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

FAQPage Schema
How do I verify a library version before making a technology recommendation?▼

To verify a library version, check local tool outputs like the --version command and cross-reference the results against official documentation and release notes to ensure accurate technology recommendations.

What is the best way to fact-check API capabilities for technical proposals?▼

The best way to fact-check API capabilities is to read official documentation, examine local tool outputs, and gather verifiable evidence from primary sources before drafting technical proposals.

How do I state uncertainty when I cannot fully verify a tool's documentation?▼

When tool documentation is inconclusive, you should clearly state the remaining uncertainty and provide fallback planning by suggesting safe alternatives and cautious defaults for the user.

Can I use evidence-based guidance for IT operations and data science evaluations?▼

Yes, you can apply evidence-based guidance across software development, data science, and IT operations to ensure technical evaluations and recommendations are backed by verified facts.

Why do I need to check official docs before recommending a CLI tool?▼

You need to check official docs because relying on verified facts from primary sources reduces the risk of providing confident but incorrect guidance about CLI tool behaviors and capabilities.

Related Skills

Explore More Education & Research Skills→
ShopifyShopify
491

shopify-onboarding-dev

Guide Shopify CLI and AI toolkit installation with environment detection and version checks.

Official
Intermediate
StudyDriftStudyDrift
58

verify-this

Restate claims and compare baseline and treatment artifacts to return a verdict.

Official
Advanced
Svenja-devSvenja-dev
38

changelog-generator

Analyze Git history and convert commit messages into categorized release notes.

Community
Basic
skylarsaboskylarsabo

research-verify

Verify research claims against primary sources and the codebase.

Community
Advanced