Critical Thinking & Self-Skepticism

Critique architecture and code by questioning assumptions and validating evidence.

1|Updated Oct 20, 2025
One-click install
npx skills add https://github.com/colek42/claude-plugins --skill critical-thinking-self-skepticism
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Critical Thinking & Self-Skepticism
Source: https://github.com/colek42/claude-plugins/tree/main/nk-dev-practices/skills/critical-thinking
Command: npx skills add https://github.com/colek42/claude-plugins --skill critical-thinking-self-skepticism

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solves? This Skill cultivates a rigorous, objective, and self-skeptical mindset essential for high-quality technical work. It encourages direct, fact-based communication and proactive problem identification, reducing assumptions and improving decision-making.

Core Features & Use Cases

  • Linus Torvalds Mindset: Promotes direct, technical communication focused on facts and problem-solving, prioritizing accuracy over validation.
  • Extraordinary Skepticism: Encourages constant questioning of assumptions, self-correction, and a healthy fear of being wrong to drive deeper investigation.
  • Red Team Everything: Guides users to critically analyze completeness and expose unsupported thoughts before declaring work "done," broadening scope beyond stated assumptions.
  • Use Case: During a design review, this skill prompts the user to challenge assumptions, identify potential flaws, and ask probing questions, ensuring a more robust and well-thought-out architectural decision rather than simply agreeing with initial proposals.

Quick Start

When evaluating a solution or design, ask yourself:

- What assumptions am I making, and are they validated?

- What could go wrong here, and how can I prove it won't?

- Is there concrete evidence to support every claim?

- Have I considered all edge cases and alternative solutions?

- What information is missing or unclear?

Frequently Asked Questions about Critical Thinking & Self-Skepticism

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

FAQPage Schema
How do I improve code review quality by challenging assumptions?

Code review quality improves by questioning every assumption, demanding concrete evidence for claims, and identifying edge cases before approving. This approach exposes hidden flaws and prevents decisions based on incomplete analysis.

What's the best way to evaluate if a design decision is truly complete?

Evaluate completeness by red-teaming the proposal: identify what could fail, test unsupported assumptions, document missing information, and disclose limitations. Declare work done only after systematically challenging every aspect.

How do I shift from accepting proposals to critically analyzing them?

Adopt a skeptical mindset by asking what assumptions underpin each claim, what evidence validates them, and what alternative solutions exist. Replace validation-seeking with fact-based investigation and self-correction.

When should I use direct technical critique instead of consensus-building feedback?

Use direct critique during design reviews, architecture decisions, and debugging when accuracy matters more than agreement. This approach reduces ambiguity and surfaces problems faster than consensus-focused communication.

Can I apply skepticism without creating conflict in technical discussions?

Yes. Ground critique in evidence, question assumptions rather than people, and focus on problem-solving. Direct, fact-based questioning reduces defensiveness and improves outcomes compared to indirect or validating feedback.

What edge cases am I missing when evaluating a solution?

Identify missing edge cases by systematically red-teaming the solution: test boundary conditions, challenge stated scope, examine failure modes, and document assumptions. This reveals gaps before implementation.