critical-thinking-logical-reasoning
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.
Security Assessment
About critical-thinking-logical-reasoning
A guided method for critically analysing the reasoning in written content — articles, blogs, transcripts, and reports, rather than code — to be used specifically when explicitly asked to critique or analyse an argument. It frames the task through a lens of critical thinking and logical reasoning and walks through a disciplined sequence: first understand the argument well enough to restate it in a way its author would accept, then identify the core claims (separating conclusions from supporting points), examine whether the evidence is sufficient, relevant, and credibly sourced, and spot logical issues such as fallacies, unsupported leaps, and circular reasoning. It distinguishes the standards different claims require — empirical claims need evidence, normative claims need justified principles, and definitional claims need consistency — and prompts surfacing hidden assumptions, considering what is missing (alternative explanations, contradictory evidence, unstated limitations), assessing internal consistency, and weighing the burden of proof against the significance of the claim. Output follows a fixed structure: a one-sentence Summary of the core claim and overall assessment; a Key Issues section bulleting the most significant problems with why each matters and, where relevant, how a weak argument could be strengthened; a Questions to Probe section of two to five questions a decision-maker should ask; and a Verdict giving the actionable takeaway. The guidelines emphasize charity paired with rigor — assume good intentions, critique the argument rather than the person, prioritize issues that genuinely affect the conclusion over minor technical flaws, apply a 'so what' test, distinguish 'flawed' from 'wrong', acknowledge uncertainty in one's own analysis, avoid fact-checking empirical claims unless obviously implausible, and refrain from manufacturing criticism when an argument is sound. Concise output and Australian English spelling are required throughout.
FAQ
When should this skill be used?
Only when explicitly asked to critically analyse or critique an argument in written content such as articles, blogs, transcripts, or reports — it is for reasoning, not for code.
What is the first step of the analysis?
Understand the argument well enough to state it in a way the author would agree with; if you can't, you're not ready to critique it.
How is the response structured?
Into four parts — a one-sentence Summary, a Key Issues bullet list with why each matters, two to five Questions to Probe, and a Verdict with the actionable takeaway.
Does it fact-check claims?
No — it critiques reasoning and logic, and does not fact-check empirical claims unless they are obviously implausible or internally contradictory.
What tone and conventions does it follow?
Direct and concise with no fluff, charitable but rigorous, critiquing the argument rather than the person, and using Australian English spelling.
Install critical-thinking-logical-reasoning
Quick Setup:
- Copy the skill folder to
.claude/skills/ - Claude will automatically detect and use the skill
Repository
sammcj/agentic-coding