doubt

Validate disputed claims across Ground, Source, and Adversary axes with cited verdicts.

1|Updated May 28, 2026
One-click install
npx skills add https://github.com/SilvrDuck/skills --skill doubt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doubt
Source: https://github.com/SilvrDuck/skills/tree/main/skills/doubt
Command: npx skills add https://github.com/SilvrDuck/skills --skill doubt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you respond when you sense a wrong or shaky answer and need the AI to pause, investigate the claim, and produce an honest verdict backed by authoritative sources.

Core Features & Use Cases

  • Fresh skepticism mode: re-examines the disputed claim instead of defending or capitulating.
  • Explicit claim investigation: treats the user’s paste or hunch as the exact target to verify.
  • Structured three-part analysis: grounds findings in observable reality, cites authoritative sources, and actively tries to falsify the claim.
  • Three honest outcomes: returns one of Correct way, Pushback, or Tradeoffs with actionable resolution.

Quick Start

Invoke the skill as /doubt with your hunch or by pasting the specific line you think is wrong.

Frequently Asked Questions about doubt

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

FAQPage Schema
How do I verify if a disputed code snippet or API behavior claim is correct?

To verify a disputed code snippet or API behavior claim, you can trigger an evidence-backed re-examination that classifies the doubt type, validates it across observable reality and authoritative sources, and actively attempts to falsify the claim before producing a final verdict.

What is the best way to perform an evidence-based code review when I suspect an error?

Evidence-based code review for suspected errors requires a structured three-part analysis that grounds findings in observable reality, cites authoritative sources, and applies adversary testing to falsify the disputed snippet, returning a final actionable resolution.

Can I use skeptical debugging to evaluate pasted project facts and domain knowledge?

Skeptical debugging evaluates pasted project facts and domain knowledge by treating the user's hunch as the exact target to verify, ensuring a fresh skepticism mode that re-examines the disputed claim instead of defending or capitulating to the original assumption.

How does claim verification work for reasoning errors in software engineering?

Claim verification for reasoning errors works by classifying the specific doubt type, validating the claim across Ground, Source, and Adversary axes, and concluding with exactly one of three honest outcomes: Correct way, Pushback, or Tradeoffs supported by citations.

What outcomes should I expect from a tradeoff analysis of a disputed API behavior?

Tradeoff analysis of a disputed API behavior yields exactly one of three honest outcomes: a Correct way resolution, a Pushback against the original claim, or a Tradeoffs conclusion, all of which are supported by citations from authoritative sources.