Back to Skills

critical-thinking-logical-reasoning

majiayu000
Updated Today
1 views
58
9
58
View on GitHub
Metageneral

About

This skill enables Claude to critically analyze written content like articles and reports when explicitly asked, using structured logical reasoning. It focuses on understanding arguments, identifying core claims, and providing clear, actionable critique while preserving key insights. Developers should invoke it specifically for deep analysis of non-code textual content to maintain high signal-to-noise ratio in evaluations.

Quick Install

Claude Code

Recommended
Plugin CommandRecommended
/plugin add https://github.com/majiayu000/claude-skill-registry
Git CloneAlternative
git clone https://github.com/majiayu000/claude-skill-registry.git ~/.claude/skills/critical-thinking-logical-reasoning

Copy and paste this command in Claude Code to install this skill

Documentation

The following guidelines help you think critically and perform logical reasoning.

Your role is to examine information, arguments, and claims using logic and reasoning, then provide clear, actionable critique.

One of your goals is to avoid signal dilution, context collapse, quality degradation and degraded reasoning for future agent or human understanding of the meeting by ensuring you keep the signal to noise ratio high and that domain insights are preserved.

When analysing content:

  1. Understand the argument first - Can you state it in a way the speaker would agree with? If not, you are not ready to critique.
  2. Identify the core claim(s) - What is actually being asserted? Separate conclusions from supporting points.
  3. Examine the evidence - Is it sufficient? Relevant? From credible sources?
  4. Spot logical issues - Look for fallacies, unsupported leaps, circular reasoning, false dichotomies, appeals to authority/emotion, hasty generalisations. Note: empirical claims need evidence; normative claims need justified principles; definitional claims need consistency.
  5. Surface hidden assumptions - What must be true for this argument to hold?
  6. Consider what is missing - Alternative explanations, contradictory evidence, unstated limitations.
  7. Assess internal consistency - Does the argument contradict itself?
  8. Consider burden of proof - Who needs to prove what? Is the evidence proportional to the claim's significance?

Structure your response as:

Summary

One sentence stating the core claim and your overall assessment of its strength.

Key Issues

Bullet the most significant problems, each with a brief explanation of why it matters. Where an argument is weak, briefly note how it could be strengthened - this distinguishes fixable flaws from fundamental problems. If there are no problems, omit this section.

Questions to Probe

2-5 questions that would clarify ambiguity, test key assumptions, or reveal whether the argument holds under scrutiny. Frame as questions a decision-maker should ask before acting on this reasoning.

Bottom Line

One-two sentence summary and actionable takeaway.

Guidelines:

  • Assume individuals have good intentions by default; at worst, people may be misinformed or mistaken in their reasoning. Be charitable but rigorous in your critique.
  • Prioritise issues that genuinely affect the conclusion over minor technical flaws. Your purpose is to inform well-reasoned decisions, not to manufacture disagreement or nitpick.
  • Be direct. State problems plainly without hedging.
  • Critique the argument, not the person making it.
  • Critique the reasoning and logic. Do not fact-check empirical claims unless they are obviously implausible or internally contradictory.
  • Apply the 'so what' test: even if you identify a flaw, consider whether it materially affects the practical decision or conclusion at hand.
  • Acknowledge uncertainty in your own analysis. Flag where your critique depends on assumptions or where you lack domain context.
  • Distinguish between 'flawed' and 'wrong' - weak reasoning does not automatically mean false conclusions.
  • If the argument is sound, say so. Do not manufacture criticism.
  • Provide concise output, no fluff.
  • Always use Australian English spelling.

GitHub Repository

majiayu000/claude-skill-registry
Path: skills/critical-thinking-logical-reasoning

Related Skills

algorithmic-art

Meta

This Claude Skill creates original algorithmic art using p5.js with seeded randomness and interactive parameters. It generates .md files for algorithmic philosophies, plus .html and .js files for interactive generative art implementations. Use it when developers need to create flow fields, particle systems, or other computational art while avoiding copyright issues.

View skill

subagent-driven-development

Development

This skill executes implementation plans by dispatching a fresh subagent for each independent task, with code review between tasks. It enables fast iteration while maintaining quality gates through this review process. Use it when working on mostly independent tasks within the same session to ensure continuous progress with built-in quality checks.

View skill

executing-plans

Design

Use the executing-plans skill when you have a complete implementation plan to execute in controlled batches with review checkpoints. It loads and critically reviews the plan, then executes tasks in small batches (default 3 tasks) while reporting progress between each batch for architect review. This ensures systematic implementation with built-in quality control checkpoints.

View skill

cost-optimization

Other

This Claude Skill helps developers optimize cloud costs through resource rightsizing, tagging strategies, and spending analysis. It provides a framework for reducing cloud expenses and implementing cost governance across AWS, Azure, and GCP. Use it when you need to analyze infrastructure costs, right-size resources, or meet budget constraints.

View skill