Critical Thinking Logical Reasoning

sammcj/agentic-coding/Skills/critical-thinking-logical-reasoning

by sammcj527cf639ae86No license162 starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated today

Critically analyse the reasoning in written content (articles, blogs, transcripts, reports), not code. Use only when explicitly asked to critically analyse or critique an argument.

Instructions onlyResearch & Analysis
AI-generated overview

Critically analyses reasoning in written content, producing a structured critique of claims, evidence and logic.

What it does
Examines written arguments such as articles, blogs, transcripts and reports, identifying core claims, evidence quality, logical fallacies, hidden assumptions and gaps. It returns a structured critique with a summary, key issues, probing questions and an actionable verdict. It critiques reasoning rather than fact-checking empirical claims, and notes how weak arguments could be strengthened.
When to use it
Use when explicitly asked to critically analyse or critique the argument in a piece of written content. It is intended for evaluating reasoning quality before acting on a conclusion, not for reviewing code or verifying facts.
Requirements
No scripts or special tools; it is an instructions-only skill that runs within the agent.

Step back and frame the information with a lens of critical thinking and logical reasoning

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

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. 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.

Verdict

The actionable takeaway - what to do given this analysis.

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.

Source and attribution

Source:sammcj/agentic-codinginSkills/critical-thinking-logical-reasoningat commit527cf63

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal