skills.rest
haolange
haolangeCOMMUNITY
Explore all skills by this author →
GitHub

skeptic

Challenge weak claims and require evidence before accepting debugging conclusions.

15|5|Updated Mar 5, 2026
Search Tags:#debugging#verification#evidence#claims-evaluation#skeptic#rdc-debugger
One-click install
npx skills add https://github.com/haolange/RDC-Agent-Frameworks --skill skeptic-haolange
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: skeptic
Source: https://github.com/haolange/RDC-Agent-Frameworks/tree/main/debugger/platforms/claude-code/.claude/skills/skeptic
Command: npx skills add https://github.com/haolange/RDC-Agent-Frameworks --skill skeptic-haolange

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The skeptic skill provides a disciplined reviewer role that challenges weak claims during debugging sessions and prevents premature sign-offs until evidence is verified.

Core Features & Use Cases

  • Rigorous claim evaluation: requires evidence and cross-checks before accepting conclusions.
  • Guarded escalation: routes uncertain claims to the skeptic role when multiple agents or artifacts create doubt.
  • Evidence-backed sign-off: only endorses results after verification across relevant artifacts.

Quick Start

When prompted by rdc-debugger, summon the skeptic to validate the current claim using available artifacts and supporting evidence.

Frequently Asked Questions about skeptic

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

FAQPage Schema
How do I challenge weak claims during debugging sessions?▼

Challenge weak claims during debugging by applying a reviewer role that requires evidence and cross-checks before accepting conclusions, preventing premature sign-offs until verification is complete.

What is evidence-backed sign-off in debugging workflows?▼

Evidence-backed sign-off is a verification process that only endorses debugging results after confirming evidence across relevant artifacts, ensuring conclusions are proven before final acceptance.

How do I prevent premature conclusions with multiple debugging agents?▼

Prevent premature conclusions by routing uncertain claims to a skeptic role when multiple agents or artifacts create doubt, enforcing guardrails that require cross-checks before final sign-off.

When do I need to escalate claims for rigorous evaluation?▼

Escalate claims for rigorous evaluation when uncertainty arises across multiple agents or artifacts, triggering a guarded escalation that demands evidence verification before proceeding.

How do I validate debugging conclusions using rdc-debugger?▼

Validate debugging conclusions by summoning a skeptic role during rdc-debugger sessions to verify current claims using available artifacts and supporting evidence before final sign-off.

What are the limitations of relying on claims without verification?▼

Relying on claims without verification risks accepting weak conclusions, which guarded escalation prevents by requiring evidence and cross-checks across relevant artifacts before final sign-off.

Related Skills

Explore More Software Engineering Skills→
haolangehaolange
15

reference-contract

Validate reference contract fields against acceptance rules and produce pass/fail diagnostics.

Community
Basic
cuipengfeicuipengfei
8

multi-source-inquiry

Cross-verify claims across multiple source categories with evidence labels.

Community
Advanced
haolangehaolange
15

report-knowledge-curator

Generate BugFull and BugCard outputs and curate reusable knowledge for Claude Code workflows.

Community
Advanced
Miss-PinkElfMiss-PinkElf

superpowers-verification-before-completion

Enforce fresh verification evidence before SPARK-workflow completion claims.

Community
Intermediate