critical-thinking-logical-reasoning
sammcj/agentic-coding
Analyse written arguments and claims using structured critical thinking and logical reasoning.
What is critical-thinking-logical-reasoning?
This skill helps you examine articles, blogs, transcripts, and reports by identifying logical fallacies, unsupported claims, hidden assumptions, and gaps in reasoning. Use it when asked to critically analyse non-code written content and provide actionable critique.
- Identify core claims and separate conclusions from supporting points
- Examine evidence for sufficiency, relevance, and credibility
- Spot logical fallacies, circular reasoning, false dichotomies, and appeals to authority or emotion
- Surface hidden assumptions required for arguments to hold
- Detect missing alternative explanations, contradictory evidence, and unstated limitations
- Assess internal consistency and burden of proof proportionality
How to install critical-thinking-logical-reasoning
npx skills add https://github.com/sammcj/agentic-coding --skill critical-thinking-logical-reasoningHow to use critical-thinking-logical-reasoning
- 1.Provide the written content you want analysed (article, transcript, report, etc.)
- 2.Ask the skill to critically analyse it using the structured approach
- 3.The skill will examine the core claim, evidence, logical issues, and hidden assumptions
- 4.Review the structured critique including key issues, probing questions, and bottom-line takeaway
- 5.Use the findings to inform your decision or understanding
Use cases
- Evaluate the reasoning in a research article or white paper before acting on its recommendations
- Critique the logic of a business proposal or strategic argument in a meeting transcript
- Analyse a blog post or opinion piece to identify unsupported claims and weak reasoning
- Review a report's conclusions to check whether evidence actually supports them
- Assess the soundness of an argument in a debate or discussion transcript
- Decision-makers evaluating proposals or recommendations
- Researchers and analysts reviewing published work
- Team members critiquing strategic or policy arguments
- Anyone needing to assess the quality of reasoning in written content
critical-thinking-logical-reasoning FAQ
No. It critiques reasoning and logic rather than verifying empirical facts, unless claims are obviously implausible or internally contradictory. The focus is on argument structure, not factual accuracy.
The skill will say so. It does not manufacture criticism—if reasoning is solid, that will be stated clearly.
This skill specifically examines logical validity, identifies fallacies, surfaces assumptions, and flags gaps in reasoning. It goes beyond summary to evaluate the strength and soundness of arguments.
No. This skill is designed for written content like articles, blogs, transcripts, and reports—not code. For code critique, use other code-specific skills.
Structured output with a one-sentence summary of the core claim, bullet-pointed key issues with explanations, 2–5 probing questions, and a concise bottom-line takeaway.
Full instructions (SKILL.md)
Source of truth, from sammcj/agentic-coding.
name: critical-thinking-logical-reasoning description: Critical thinking and logical reasoning analysis skills for when you are explicitly asked to critically analyse written content such as articles, blogs, transcripts and reports (not code).
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:
- Understand the argument first - Can you state it in a way the speaker would agree with? If not, you are not ready to critique.
- Identify the core claim(s) - What is actually being asserted? Separate conclusions from supporting points.
- Examine the evidence - Is it sufficient? Relevant? From credible sources?
- 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.
- Surface hidden assumptions - What must be true for this argument to hold?
- Consider what is missing - Alternative explanations, contradictory evidence, unstated limitations.
- Assess internal consistency - Does the argument contradict itself?
- 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.
Related skills
More from sammcj/agentic-coding and the wider catalog.

muapi-ad-creative
Generate a high-converting ad creative set — hero image, ad copy variations, and platform-optimized crops for Meta, Google Display, and LinkedIn.

muapi-ai-clipping
Turn a long video into N viral-ready short clips with a single managed API call. Wraps muapi.ai's `/ai-clipping` endpoint, which handles transcription, highlight ranking through a virality framework (hook / emotional peak / opinion bomb / revelation / conflict / quotable / story peak / practical value), overlap dedupe, and vertical face-tracking auto-crop server-side. No local Whisper, no local LLM, no GPU.

muapi-cinema-director
Direct high-fidelity cinematic video with AI — translates creative intent into technical cinematographic directives for Veo3, Kling, and Luma video models via muapi.ai

muapi-instagram-post
Create a polished, on-brand Instagram post — square or portrait hero image with matching caption and hashtags.

muapi-logo-creator
Engineer professional-grade brand logos using geometric primitives and negative space — generates minimalist, scalable vector-style marks via muapi.ai

muapi-media-editing
Edit and enhance images and videos with AI via muapi.ai — prompt-based editing, upscaling, background removal, face swap, lipsync, video effects, and more